Bugzilla – Bug 965517
Switching off monitor causes sddm-greeter to exit
Last modified: 2016-02-08 11:45:57 UTC
Steps to reproduce: 1) log in to KDE5 2) lock the screen (hit CTRL + ALT + L) 3) switch the monitor off 4) wait a couple of seconds 5) switch the monitor on. Results: sddm-greeter exited, and, if plasmashell didn't crash, which is another issue, the screen is unlocked and fully accessible. No need to enter the password. I guess that setQuitOnLastWindowClosed(false) in sddm-greeter would be enough to prevent that, but I don't know if it could cause other issues.
You are mixing two different things here: Plasma's lockscreen is totally independent of sddm and its greeter, except that there's a breeze theme for both. So is this about the lock screen only? That's already reported as Bug#964548 and currently under investigation. Or do you have a problem with sddm (i.e. the *login* screen) too?
Right. My mistake in thinking KDE could uses sddm-greeter as screenlocker. On the bright side, I have patched sddm-greeter to add setQuitOnLastWindowClosed(false), and now the *login* screen doesn't die if the monitor is switched off at boot (which would leave you unable to log in to KDE/Gnome once the monitor is switched on again). Sorry again for the confusion.
Ok, so sddm's greeter quits too when you turn off the monitor? Let's adjust the summary then. For the record, I cannot reproduce this here on my 13.2 radeon system (but then I cannot reproduce the screenlocker issue either by just switching off the only monitor or even disconnect it). So, what graphics driver are you using? What I can reproduce is that sddm's greeter doesn't show up at all if no monitor is connected during boot (if it is only turned off, it does work fine here though). I filed an upstream bug report about this: https://github.com/sddm/sddm/issues/598
PS: Actually your report here is a duplicate of Bug#964353 then, no?
(In reply to Wolfgang Bauer from comment #4) > PS: Actually your report here is a duplicate of Bug#964353 then, no? in the end it is, you're right. Sorry again for the confusion. *** This bug has been marked as a duplicate of bug 964353 ***