Jamie Getty <[email protected]> writes: > I'm not sure what you mean by *wrap it in dbus-run-session*. > I use SDDM as my display manager and I start Sway from there. > My sway config also contains this line, as previously mentioned: > > *# Enable screen sharingexec --no-startup-id > dbus-update-activation-environment --all* > > However, I noticed that if I try running this line by itself in a terminal, > I get this output: > > > *jamie@localhost ~ $ exec --no-startup-id > dbus-update-activation-environment --allbash: exec: --: invalid optionexec: > usage: exec [-cl] [-a name] [command [argument ...]] [redirection ...]*
Sway configs aren't shells scripts. In shell, you'd run 'dbus-update-activation-environment --all' alone. Does qdbus --session output any errors or just a bunch of names and numbers? SDDM should set up a D-Bus session bus, I believe. I'm quite sure that your D-Bus session bus is not working properly because of the error you initially posted. > On Sun, Nov 26, 2023 at 11:37 PM Arsen Arsenović <[email protected]> wrote: > >> Hi Jamie, >> >> Jamie Getty <[email protected]> writes: >> >> > How do I ensure I have a dbus user session running? Those links just lead >> > to forum posts with varying issues and I'm not sure which to follow. >> > Here are the dbus-related process I have running: >> >> Make sure to wrap it in dbus-run-session. See >> https://wiki.gentoo.org/wiki/Sway#Starting_Sway >> >> Then add the >> >> exec --no-startup-id dbus-update-activation-environment --all >> >> ... line from the screen sharing troubleshooting entry. >> -- >> Arsen Arsenović >> -- Arsen Arsenović
signature.asc
Description: PGP signature
