You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
lightdm can't start a GNOME wayland session #56342
Mostly opening for investigation, someone in IRC mentioned that they couldn't
get a wayland session to start when using lightdm, as they noticed this when $XDG_SESSION_TYPE == x11.
I was then able to reproduce this within a VM.
Steps to reproduce
Enable GNOME3 and use lightdm as a display-manager
Try to start the GNOME session
Realize that you're running the gnome-xorg session
This isn't specific to LightDM: GDM does the same thing for me. I don't know how all of the XSession stuff works, but I looked at the .desktop files in /nix/store/...gnome-session... (xsessions/gnome.desktop, xsessions/gnome-xorg.desktop, and wayland-sessions/gnome.desktop) and found them identical except for the "Name" field. Am I missing something, or should the "Exec" fields (and possibly others) be different for the XOrg and Wayland sessions?
EDIT: The corresponding files are the same in Fedora (which runs the Wayland session), so I guess that isn't the problem (GDM still runs the X session for both in NixOS, however)
Yeah, there's some behind the scenes stuff being done depending on where the desktop files reside (ie. wayland-sesisons/ vs. xsessions/)
GDM still runs the X session for both in NixOS
Works here. nixos-18.09 doesn't have gnome wayland support, that might be what you're seeing. Otherwise I would double check that services.xserver.displayManager.gdm.wayland is true (should be by default). There might be some hardware thing too (eg. nvidia card with the proprietary drivers, don't think we support that yet).
I'm guessing lightdm finds the xsession first (since there's a gnome.desktop in both). Should probably work to just add the wayland session dir before the xsession one. Checking now.
Oh, I forgot to mention how when I tested, I worked around the duplicate session name bug (which plasma5 actually compensates for in sddm, gnome could do similar).
I removed the xsessions from gnome-session in testing to be sure.
Ahh, right, using the wayland dir first worked, in the sense that it tries to launch a wayland session. But something is indeed broken as it won't start the session.
Hello, I'm a bot and I thank you in the name of the community for opening this issue.
To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.
The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.
If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.
Activity
hedning commentedon Feb 25, 2019
Yeah, I didn't turn it on in the gnome wayland pr as lightdm didn't handle the duplicate
gnome.desktopsesssion names:nixpkgs/nixos/modules/services/x11/display-managers/lightdm.nix
Line 48 in f3a676a
#53843 turns it on (note this pr needs to be updated for pantheon).
worldofpeace commentedon Feb 25, 2019
Thanks for the heads up
I'll push some fixup commits to that branch so it can work for pantheon
hedning commentedon Feb 25, 2019
Cheers :)
According to upstream it's up to the specific greeter to handle duplicates: ubuntu/lightdm#16
lePerdu commentedon Apr 10, 2019
This isn't specific to LightDM: GDM does the same thing for me. I don't know how all of the XSession stuff works, but I looked at the .desktop files in
/nix/store/...gnome-session...(xsessions/gnome.desktop,xsessions/gnome-xorg.desktop, andwayland-sessions/gnome.desktop) and found them identical except for the "Name" field. Am I missing something, or should the "Exec" fields (and possibly others) be different for the XOrg and Wayland sessions?EDIT: The corresponding files are the same in Fedora (which runs the Wayland session), so I guess that isn't the problem (GDM still runs the X session for both in NixOS, however)
hedning commentedon Apr 10, 2019
Yeah, there's some behind the scenes stuff being done depending on where the desktop files reside (ie.
wayland-sesisons/vs.xsessions/)Works here.
nixos-18.09doesn't have gnome wayland support, that might be what you're seeing. Otherwise I would double check thatservices.xserver.displayManager.gdm.waylandistrue(should be by default). There might be some hardware thing too (eg. nvidia card with the proprietary drivers, don't think we support that yet).lePerdu commentedon Apr 10, 2019
I'm on the
nixos-unstablechannel and can start the GNOME wayland session manually withworldofpeace commentedon Jan 30, 2020
LightDM can now start wayland sessions, it needed a patch upstream that I provided
However it is broken with GNOME still. Haven't had time to debug it.
hedning commentedon Jan 30, 2020
I'm guessing lightdm finds the xsession first (since there's a gnome.desktop in both). Should probably work to just add the wayland session dir before the xsession one. Checking now.
worldofpeace commentedon Jan 30, 2020
Oh, I forgot to mention how when I tested, I worked around the duplicate session name bug (which plasma5 actually compensates for in sddm, gnome could do similar).
I removed the xsessions from gnome-session in testing to be sure.
hedning commentedon Jan 30, 2020
Ahh, right, using the wayland dir first worked, in the sense that it tries to launch a wayland session. But something is indeed broken as it won't start the session.
stale commentedon Aug 28, 2020
Hello, I'm a bot and I thank you in the name of the community for opening this issue.
To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.
The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.
If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.
Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel.
6 remaining items
stale commentedon Aug 28, 2021
I marked this as stale due to inactivity. → More info
MohamedLEGH commentedon Sep 23, 2022
still not working.
qweered commentedon May 25, 2026
Gnome is wayland only now, if anyone still have this issue please comment