ly doesn't set DBUS_SESSION_BUS_ADDRESS for sessions #380

UtkarshVerma commented 2022年05月24日 06:17:34 +02:00 (Migrated from github.com)

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).

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).

michaelBelsanti commented 2022年06月13日 04:04:30 +02:00 (Migrated from github.com)

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.

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 commented 2023年01月25日 08:58:18 +01:00 (Migrated from github.com)

#384 related

#384 related

xi-pinmping commented 2023年01月30日 20:10:26 +01:00 (Migrated from github.com)

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.

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 commented 2024年05月02日 19:17:47 +02:00 (Migrated from github.com)

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.

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 commented 2024年05月04日 15:22:25 +02:00 (Migrated from github.com)

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

> 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](https://github.com/fairyglade/ly/issues/384#issuecomment-1213103624)

AnErrupTion commented 2024年07月27日 21:35:50 +02:00 (Migrated from github.com)

@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 @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 commented 2024年07月28日 05:05:49 +02:00 (Migrated from github.com)

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

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

TheRealMothebad commented 2024年09月28日 08:53:36 +02:00 (Migrated from github.com)

(削除) @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.

~~@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 commented 2024年09月28日 21:12:36 +02:00 (Migrated from github.com)

Mind to close the issue?

Mind to close the issue?

Cogumelo commented 2026年01月29日 15:58:21 +01:00

I'm still having this issue on Artix with Dinit

I'm still having this issue on Artix with Dinit

AnErrupTion commented 2026年01月29日 21:17:55 +01:00

@Cogumelo Could you open a new issue please? Thanks!

@Cogumelo Could you open a new issue please? Thanks!