-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slow launch for (some) GTK apps #5732
Comments
Can you run |
Heard on IRC that adding |
Thanks for that. This issue came out of nowhere. So far Fedora has been the only distro I've tested that has this problem. |
This might be related to the switch from Edit: try |
@wmww Sure looks that way:
Neither adding the environment variable, nor Here's a strace log from launching https://gist.github.com/tokyovigilante/872e9e24c061886ab19a14f9ae19ad3c |
If you've established that As for how to fix it, I'm not sure. You can try running |
Was going to edit the above post, but thanks for the speedy reply. Mysteriously fixed after a reboot with both fixes above applied. Are these true fixes and I can close this, or is there an underlying sway bug? |
Ah yes, you'd need to reboot (or maybe just restart the session?) for the |
FWIW the very end in my sway file runs |
Note that because some distributions ship by default a similar script for X11, that explains why we're the only ones seeing this. Some systemd distributions like Arch Linux ship something similar by default: Obviously it's not included by default in user config files. I don't think there's much to be done here. I added a wiki entry to document the issue: /~https://github.com/swaywm/sway/wiki#gtk-applications-take-20-seconds-to-start |
Adding |
I just experienced this on Ubuntu 20.04 too just now, but I did so after adding a custom PPA for updated mesa-drivers, which may also be a contributing factor. Honestly not sure. Solution was the same though, so I'm happy. |
Is there a method for nosystemd? For example OpenRC. |
This was still an issue for my system, and will probably be for others. Mostly default Ubuntu 22.04.1 LTS with Sway installed, fixed with |
For me adding |
But what if it uses no-systemd? |
@beucismis does xdg-desktop-portal work without systemd at all? Maybe you better set |
I'm on Hyprland, was having the same issues and fixed them by following their wiki, however, some GTK apps were still having the 25s timeout (Firefox and Virt-Manager, for me), even with |
Same for me and adding |
I had the same issue. I tried everything in the wiki and the recommendations from this issue. Unfortunately, nothing helped besides removing Later on, I figured out that I had some other portal backends installed like
I'm uncertain if the file is available on every distribution, so check that first, i.e., using |
Not using sway, but ran into similar issue, as opposed to Michael, I didn't have to get rid of all |
|
Hate to post on a dead thread, but I recently installed sway on an Ubuntu 24.04 machine and ran into the same problem - GUI programs would take 20+ seconds to start the first time, and then on subsequent attempts they'd open just fine. I uninstalled I fixed that by installing Dumps of a few relevant commands:
|
Sway Version:
sway version 1.5-d6ac3075 (Oct 13 2020, branch 'master')
Debug Log:
https://gist.github.com/tokyovigilante/198fe1b11f378bc02b9c41b14396cf18
Configuration File:
Minimal - https://gist.github.com/tokyovigilante/1222534c8743c1827933fe4d3cbd6d38
Description:
Launching some GTK/GLib apps seems to hang for ~10-15 sec before launching and running normally. Occurs at least with waybar, sublime-merge and Pantheon files app. Doesn't happen with Vivaldi, ST3 or terminal (alacritty). Nothing obvious in the log, all affected apps should be Wayland-native. 100% reproducible with affected apps.
Log shows launch to minimal desktop, followed by waybar appearing at ~15 sec as a result of being called from
bar_command
.Lenovo X1Y4 with FC33, Kernel 5.9 and mesa-git, although also occuring on an Intel desktop with AMD GPU (also using mesa-git).
The text was updated successfully, but these errors were encountered: