On Wed Jun 18, 2025 at 1:05 PM CEST, Ralph Corderoy wrote: > Hi Radek, > >> I discovered that the issue has nothing to do with xdg-desktop-portal. >> Other D-Bus activated services also does not start. > > Does this help? > > — https://wiki.archlinux.org/title/Sway#Configuration
No, it's not that. I already have 50-systemd-user.conf included in my Sway config. I dug into the topic a little more. I switched from dbus-broker-units to dbus-daemon-units, and services can now be activated via dbus (both dunst.service and xdg-desktop-portal.service with its backends work). Unfortunately, this creates other problems mainly with responsiveness. For example, Chromium needs around 20 seconds to start and even 20 more to resolve the first domain. After that, it is quite fast. seahorse (GNOME UI for accessing gnome-keyring) timeouts (even though gnome-keyring-daemon.service is enabled and started; as far as I understand the config files, it is not supposed to be D-Bus activated). I tried for the second time, and it worked, but not in a way that I could read a password. There were other similar problems, so I switched back to dbus-broker-units. The described problems are gone, but dunst.service and xdg-desktop-portal (and probably others) are again not activatable via D-Bus. Any idea what might be the problem with dbus-broker that it does not activate services? Best, Radek
