[master] Some apps need 20-30 seconds to start

[nwg-piotr]

I'm not sure if it's a bug, or something wrong in my configuration, but I don't know where even to start. It only happens on one of my two laptops (Ryzen + 2 x amdgpu, Arch, ly DM). The other one (intel + integrated graphics, ArchLabs, sddm) behaves well.

• If I reboot and log into wayfire, some apps (waybar, Caja, Thunar, nwggrid) need 20-30 seconds to start. It seems sometimes they don't start at all. Other apps (e.g. Chromium, mousepad, lxappearance, Alacritty, Azote) start normally.

• If I reboot, start sway, log out and start wayfire, everything works well.

[ammen99]

Try adding 0_environment = dbus-update-activation-environment --systemd WAYLAND_DISPLAY DISPLAY XAUTHORITY.
The 0_environment is just so that it is first in the alphabetical order and is run first.

[nwg-piotr]

You mean the startwayfire script?

[soreau]

You should put that in the autostart plugin config.

[nwg-piotr]

Ah, all right. It helps. Many thanks!

[damianatorrpm]

If someone comes across this you maybe also want 2_systemctl = systemctl --user import-environment
which needs to be run after 0_environment

[kode54]

Hi, that step is redundant, unless you are saying there are environment variables missing from the above command.

[damianatorrpm]

@kode54 They are not redundant.
Without the latter systemd.services that run GUI applicaitons don't see those.

[kode54]

Yes, and that dbus command with the --systemd argument does precisely the same thing.

[damianatorrpm]

If that's supposed to do so good, but it doesn't here.

[valpackett]

(note: the --systemd flag in dbus-update-activation-environment doesn't require systemd, so it's okay to always have it in autostart configs etc.)

Another completely unrelated reason something similar could happen (that probably very few other people will experience, but documenting for completeness):
if gvfs integration with gnome-online-accounts is broken (as it is right now on FreeBSD) some GTK apps would stall for about 30 seconds waiting for g-o-a to reply, and killall goa-daemon can cancel the wait.

If that's supposed to do so good, but it doesn't here.

Hmm. The manpage suggests also adding DBUS_SESSION_BUS_ADDRESS to the list of variables, because systemd might not be aware of the d-bus session bus in your setup.

[affffc]

If someone comes across this you maybe also want 2_systemctl = systemctl --user import-environment which needs to be run after 0_environment

After doing this flatpak gnome apps started respecting user theme settings. Thanks!

[LinArcX]

What about void linux users?

Void uses runit instead of systemd.

[ammen99]

0_environment = dbus-update-activation-environment --systemd WAYLAND_DISPLAY DISPLAY XAUTHORITY

@LinArcX
Use this. The --systemd means 'also pass these env vars pass to systemd if it is present'