-
Notifications
You must be signed in to change notification settings - Fork 7
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
Trying to use this theme makes nody-greeter unusable (Pop OS 20.04 LTS) #13
Comments
I just created a VM with Pop OS 22.04 LTS (20.04 LTS no longer available) to test the theme and was able to get it working. Change
Restart and try to login again, that should be the right session for Pop OS. Also make sure you don't have any other configurations with conflicting values under the Let me know if that solves your issue. |
I changed the title of the issue and I forgot to specify that I usually use xfce as my default session, but I already tried to change it to pop and it gives me the same error. Also, the /etc/lightdm/lightdm.conf.d/ folder seems to be empty. |
No need to try updating the version. I don't think the version made any big difference but wanted to point out that the test I did was not exactly the same.
Ooh ok, that makes sense, then I would assume Just to make sure, I changed my The reason why you see this problem on only this theme and the simple theme is because these themes select the session different than most. Most themes will ask the greeter for a list of all available sessions, let the user choose from that list in the interface, then on login will pass the name of the session selected by the user. The simple theme and WelcomeXP instead just asks the greeter what the default session is set to and will always ask for that session on login, whether it actually exists or not. For some reason the greeter is telling these themes that the default session is |
When you get a chance, run Interesting thing I also noticed is that if you don't specify a
|
I actually decided to update to 22.04 LTS and it now works fine without changing the lightdm.conf or any configuration file... So I guess it actually makes a difference. Also, while I was using the old version I also tried like you did to change the user-session value to something without sense like "test" and it just kept ignoring it. |
Glad it works now but that is strange, sometime I'll have to find a copy of 20.04 LTS and see if there is issues on a clean installation. If there is I might have to put a note in the README. |
I'm continuing the issue here, I'm using Arch Linux opposed from using a distribution that pre-includes LightDM I did the installation and setup manually. So this could be a setup/configuration issue. I'm unfamiliar with the purpose of .session files but in Arch Linux they aren't there because I presume it relies on the .desktop files for entries for LightDM. When trying to login via WelcomeXP it complains that the My user session has been set to xfce and I've also left it commented out but both produced the same result. My best guess myself is I could be missing session files. But it's unclear what's put inside of them. As for Nody-Greeter not working at all with the other theme. I might need to investigate that as well but if you can provide help as to why it might be struggling to get into the XFCE desktop with the default nody-greeter theme let me know too! I appreciate you taking the time to read this |
If I use the default theme (gruvbox) all the sessions start correctly; However, if I try to use this theme or the simple theme, the error
"LightDM couldn't start session
The provided session: "ubuntu" couldn't be started
Session returned error code 1"
shows up.
Then, if I try to load the default theme using the button provided in the error, it becomes unable to start up any session.
This is how my /etc/lightdm/lightdm.conf looks like:
[SeatDefaults]
user-session=xfce
greeter-session=nody-greeter
But the error message doesn't change even if I try to change the user-session value to the .desktop file name of the other ones I have installed. What should I do?
The text was updated successfully, but these errors were encountered: