-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
lightdm can't start a GNOME wayland session #56342
Comments
Yeah, I didn't turn it on in the gnome wayland pr as lightdm didn't handle the duplicate
#53843 turns it on (note this pr needs to be updated for pantheon). |
Thanks for the heads up
I'll push some fixup commits to that branch so it can work for pantheon |
Cheers :) According to upstream it's up to the specific greeter to handle duplicates: canonical/lightdm#16 |
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 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.
Works here. |
I'm on the
|
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. |
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). |
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. Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel. |
still an issue |
Still not working. |
I marked this as stale due to inactivity. → More info |
still not working. |
Issue description
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
GNOME
sessiongnome-xorg
sessioncc @hedning @jtojnar
The text was updated successfully, but these errors were encountered: