Skip to content
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

ly doesn't set DBUS_SESSION_BUS_ADDRESS for sessions #380

Closed
UtkarshVerma opened this issue May 24, 2022 · 9 comments
Closed

ly doesn't set DBUS_SESSION_BUS_ADDRESS for sessions #380

UtkarshVerma opened this issue May 24, 2022 · 9 comments
Labels
bug This issue or pull request discusses a bug

Comments

@UtkarshVerma
Copy link
Contributor

I use Arch Linux which has a systemd service for starting up dbus. If I log into a shell(without ly), I can access the session env var set by the service:

$ echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/bus

However, if I log into a session using ly, the variable is not accessible, because of which applications dependent on dbus fails (playerctl etc).

@AnErrupTion AnErrupTion added the bug This issue or pull request discusses a bug label Jun 3, 2022
@michaelBelsanti
Copy link

This is causing issues for me too. I need to add dbus-launch to i3.desktop for flatpaks to work. This is reset when i3 updates.

@sagarreddypatil
Copy link

#384 related

@xi-pinmping
Copy link

I believe this is causing gnome not to work for me at all. I have been unable to log into xorg or wayland sessions with it.

@TheRealMothebad
Copy link

I'm having this issue on Arch as well. Switching to LightDM fixed it, but I would like to use ly when it is fixed.

@shvedes
Copy link

shvedes commented May 4, 2024

I'm having this issue on Arch as well. Switching to LightDM fixed it, but I would like to use ly when it is fixed.

here is the solution

@AnErrupTion
Copy link
Collaborator

@UtkarshVerma @michaelBelsanti @xi-pinmping @TheRealMothebad Can you guys check if this issue is fixed with the latest code on master? For me DBUS_SESSION_BUS_ADDRESS is set after logging in now.

@UtkarshVerma
Copy link
Contributor Author

I stopped using ly, hence, I won't be able to test it.

@TheRealMothebad
Copy link

TheRealMothebad commented Sep 28, 2024

@AnErrupTion
> @TheRealMothebad Can you guys check if this issue is fixed with the latest code on master? For me DBUS_SESSION_BUS_ADDRESS is set after logging in now.

I'm not smart enough to build from source (I know, I'm a bad linux user), but after running 1.0.2-1 from the AUR (which seems like it should have the change based on the build date?) the problem does not seem to be fixed. Here is what pipewire has to say about it when using ly (it runs no problem under lightdm):
[E][00381.493243] mod.rt | [ module-rt.c: 281 pw_rtkit_bus_get()] Failed to connect to session bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead [E][00381.495652] mod.protocol-native | [module-protocol-: 740 init_socket_name()] server 0x5947ad44a070: name pipewire-0 is not an absolute path and no runtime dir found. Set one of PIPEWIRE_RUNTIME_DIR, XDG_RUNTIME_DIR or USERPROFILE in the environment

Also, echo $DBUS_SESSION_BUS_ADDRESS is blank

It was my fault, I'm actually using 1.0.2-1 now, and it works great! Thank you, and sorry for the needless ping.

@shvedes
Copy link

shvedes commented Sep 28, 2024

Mind to close the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue or pull request discusses a bug
Projects
None yet
Development

No branches or pull requests

7 participants