J. Roeleveld wrote: > On Wednesday, 4 March 2020 14:41:31 CET Dale wrote: >> Howdy, >> >> I did my usual Sunday upgrades the other day. There was a lot of >> upgrades to plasma and elogind it seems. Let's add LOo in there as well >> just for giggles. Anyway, I have a few oddities going on here. I'm not >> quite sure what to make of it but wondering if anyone else has ran into >> this. >> >> First weirdness. When I lock my screen, CTRL + shift + L. It locks the >> screen just fine. The weird part happens when I poke the mouse or hit a >> key to wake the screen back up. Instead of a screen asking for my >> password with the goofy looking user avatar, I get a black screen with >> the mouse pointer visible. The background and the little box for my >> password, nowhere to be found. After a bit, I type in the password, >> blindly, and it sits there for a while and then my desktop comes back. >> It takes a while and could be related to other problems coming up. > I investigated this a bit more and found it has to do with " kde-plasma/ > kscreenlocker ". > This process was using up 100% CPU (gladly only 1 core) and killing (-9) this > cleared the black screen. > > Can this also be related to still using consolekit? Do I really need to > migrate to "elogind" to be able to unlock my laptop after hibernate? > > Many thanks, > > Joost >
I migrated to elogind a few months ago, there's a thread about it too. It went well. No problems. Still, when something goes wrong with elogind, I'm trying to figure out how to recognize it. The biggest thing I don't like, it being in the boot runlevel. It requires me to remember to restart it after a upgrade. If I forget, I run into the issues in this thread. From my understanding tho, consolekit is leaving the building. At some point, switching will have to be done. When I was restarting elogind yesterday, I had a process that was taking up one core as well. I went back to the boot runlevel, stopped elogind, killed any straggling processes and then restarted elogind and back to default runlevel. So far, everything is working fine. It could be a fluke, it could repeat and be a bug of some sort. I'll know next time, if I remember to check. lol Dale :-) :-)
