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
Wrongly configured org.freedesktop.systemd1 service on user's dbus session with i3 #87502
Labels
Comments
In the session running lightdm+i3, I can see:
In the session running Gnome, I can see:
|
Here is some info about the user's dbus.socket unit:
|
I don't know if it's helpful, but I also get this on SDDM+Plasma5. This on the other hand works:
|
10 tasks
adisbladis
added a commit
to adisbladis/nixpkgs
that referenced
this issue
May 18, 2020
This ensures a correct DBUS_SESSION_BUS_ADDRESS environment variable is set and imported into the systemd user environment. Previously this would refer to a non-existing path preventing commands interacting with the systemd manager from working. Closes NixOS#87502
NickHu
pushed a commit
to NickHu/nixpkgs
that referenced
this issue
May 20, 2020
This ensures a correct DBUS_SESSION_BUS_ADDRESS environment variable is set and imported into the systemd user environment. Previously this would refer to a non-existing path preventing commands interacting with the systemd manager from working. Closes NixOS#87502
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The dbus service
org.freedesktop.systemd1
doesn't seem properly started when lightdm+i3 is used.To Reproduce
Expected behavior
Doing the same within an lightdm+i3 session results in:
Notify maintainers
/cc @ocharles @worldofpeace @modulistic @fpletz @globin
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result."x86_64-linux"
Linux 5.4.35, NixOS, 20.09.git.855483fe5af (Nightingale)
yes
yes
nix-env (Nix) 2.3.4
""
/home/cassou/Documents/projects/nixos/system
Maintainer information:
The text was updated successfully, but these errors were encountered: