KDE LiveCD - Login problem

Using the KDE LiveCD snapshot 20150518, (at the moment I’m unable to test using current snapshot).

If one logs out from KDE it is not possible to log back in via the SDDM gui; as I rather embarrassingly found out whilst showing openSUSE to a friend.

Eventually I found this is due, it seems, to the user ‘linux’ having a UID of 999. To further compound this problem, the minimum UID is not being saved in /etc/sddm.conf if it is changed from the settings gui. If one manually edits the minimum to 999 in sddm.conf, then login for the default ‘linux’ user works.

Also missing from sddm.conf are the ‘haltCommand’ and ‘rebootCommand’ (/sbin/shutdown *), and indeed it is not possible to shutdown or reboot from the liveCD, the system appears to halt but neither shuts down nor reboots. Both of these can be entered from the settings gui and are saved, after which all works as expected.

I guess you should report this at http://bugzilla.opensuse.org/.

To further compound this problem, the minimum UID is not being saved in /etc/sddm.conf if it is changed from the settings gui.

Yes. I noticed this a week ago and reported it here:
https://bugs.kde.org/show_bug.cgi?id=347942

Also missing from sddm.conf are the ‘haltCommand’ and ‘rebootCommand’ (/sbin/shutdown *), and indeed it is not possible to shutdown or reboot from the liveCD, the system appears to halt but neither shuts down nor reboots. Both of these can be entered from the settings gui and are saved, after which all works as expected.

Hm. Shutdown and reboot works fine here (on 13.2) with this in sddm.conf: (I suppose that’s what’s on the LiveCD as well, right?)

[General]
HaltCommand=
RebootCommand=

According to “man sddm.conf” the default values are “/usr/bin/systemctl poweroff” and “/usr/bin/systemctl reboot”.
So if it doesn’t work on the LiveCD there might be a problem with systemd or the polkit setup.

https://bugzilla.opensuse.org/show_bug.cgi?id=932328

Hm. Shutdown and reboot works fine here (on 13.2) with this in sddm.conf: (I suppose that’s what’s on the LiveCD as well, right?)

[General]
HaltCommand=
RebootCommand=

According to “man sddm.conf” the default values are “/usr/bin/systemctl poweroff” and “/usr/bin/systemctl reboot”.
So if it doesn’t work on the LiveCD there might be a problem with systemd or the polkit setup.

Yes, that’s as on the LiveCD, with those (blank, and therefore default) settings the KDE session ends, after a few seconds I have a blank screen, then nothing else happens.

If I change them to “/sbin/shutdown -h -P now” and “/sbin/shutdown -r now” they both work as expected. Not really too worried about that one…

Thanks…

Thanks for starting this thread, for reporting the bug, and for posting the bug number.

I haven’t recently tried a live KDE, so I had not run into the problem. But it is good to be aware of it.

Ok, but that shouldn’t be necessary, SDDM uses systemctl by default.
If that doesn’t work there’s some other problem.

As mentioned, it does work fine on my 13.2 installation, and AFAIK it works fine on an installed Tumbleweed system too.

PS, forgot to mention:
Yes, SDDM only displays users with an id>=1000 by default (and the breeze theme doesn’t allow to enter a username either). I think gdm and lightdm do the same though, so probably this problem also exists (for a longer time already) on the GNOME LiveCD?

As I said, I not too worried about it… Just to check, I’ve reverted the changes in sddm.conf and reboot/shutdown now don’t complete. KDE exits, screen blanks, quite a few seconds of activity on the USB stick (I guess it’s writing to ‘hybrid’), then … nothing. I reboot using Alt+SysRq B - So I’ll go along with your “there’s some other problem”.

The PC I normally use (previously running 13.2 which I changed to Tumbleweed) works as expected on shutdown/reboot.

PS, forgot to mention:
Yes, SDDM only displays users with an id>=1000 by default (and the breeze theme doesn’t allow to enter a username either).

So for the LiveCD the minimum UID should really have a default of 999 then - I’m sure people playing with it must log out? albeit perhaps not intentionally…

I think gdm and lightdm do the same though, so probably this problem also exists (for a longer time already) on the GNOME LiveCD?

Don’t know about GNOME… last time I used that it was on V2.something

I have not seen that problem with “lightdm” (the live rescue CD), though it has been a month or two since I last tried.

When I last tried a live Gnome, I was unable to logout and then login to Icewm. Perhaps that’s the same problem, or perhaps Icewm is not on the live CD.

Maybe the user does not have the UID 999 on the Live Rescue CD as it is not installable anyway.

There’s a way of testing that. So I did.

I downloaded openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20150524-Media.iso and then wrote to a USB and booted on my laptop.

The live user is 999. But I can logout and then login again.

The users.conf file does say that 1000 is the min uid. But it seems to be using it differently. It apparently remembers that “live” has logged in recently, so it takes that user as the default even though the uid is 999.

AFAIK this users.conf file is ignored if AccountsService is active (there should even be a comment in this file regarding this), which it is in openSUSE.

So the LiveCD probably contains am AccountsService config for user “linux” in /var/lib/AccountsService/users/ that states that it should be shown, i.e. that it is no system account. Should work with gdm then as well, but sddm does not support AccountsService (yet, it is on their TODO list).

Quick update: I’ve now had the opportunity to try the Tumbleweed-KDE-Live-x86_64-Snapshot20150525 and Halt/Reboot work as expected (with the default settings).

The login problem ( https://bugzilla.opensuse.org/show_bug.cgi?id=932328 ) is “IN_PROGRESS”, looks like a nice simple solution :slight_smile: