Hi Alex,
Alexander Asteroth <[email protected]> writes: > Dear all, > > I considered all of the hints that were given in this 1 year old > thread. > My configuration currently is similar to the one presented by > Arnaud: > > ``` > (service > home-pipewire-service-type) > (service > home-dbus-service-type) > ``` > > in my `home-config.scm` plus > > ``` > exec > $HOME/.guix-home/profile/bin/dbus-update-activation-environment > --systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP=sway >/dev/null 2>&1 > & > exec $HOME/.guix-home/profile/libexec/xdg-desktop-portal -r >>/dev/null 2>&1 & > exec $HOME/.guix-home/profile/libexec/xdg-desktop-portal-wlr -r >>/dev/null 2>&1 & > ``` Those are d-bus services. They should typically be started by dbus. To do that you would install them to your home. And you're good to go. Using -r can be good for debugging what implementations are used. Moreover even when starting manually, starting -wlr as well is also unnecessary as the main desktop portal does start all the implementations it chooses. Feel free to try with -v verbose log to see what implementations are actually being chosen. > > in my `$HOME/.config/sway/config` > > And sway is started using `dbus-run-session -- sway` from a login > tty. This is wrong. By this you've made a nested dbus session that cannot communicate with the session that runs pipewire. And that is probably the cause of the issue you're seeing. The home-dbus-service-type already starts a dbus session upon login and you should have DBUS_SESSION_BUS_ADDRESS set by it. If you're already inside of a running d-bus session, just start `sway`, not with `dbus-run-session`. Rutherther
