Arch Linux

yochaigal

Member

From: Boston

Registered: 2011-02-06

Posts: 202

KDE: "screen locker is broken" [RESOLVED]

Hey all. After a recent kernel/Xorg update I seem to have lost the ability to lock my screen in KDE. Each time I resume from suspend/unlock, it says:
"The screen locker is broken and unlocking is not possible anymore" and tells me to unlock via tty (which works).
I don't see anything relevant in the systemd journal or in Xorg log.

About system:
Thinkpad X1 Carbon 4th Gen
Arch 64bit
Linux 4.16.5-1-ARCH
KDE Plasma 5.12.4
Intel HD Graphics 520 (Skylake GT2)

Any pointers where I should dig in next?
Thanks!

RESOLVED, see

Last edited by yochaigal (2018-05-23 13:35:17)

nesk

Member

Registered: 2011-03-31

Posts: 181

Re: KDE: "screen locker is broken" [RESOLVED]

Nice job KDE In case you can't fix it - install a simple generic X11 screensaver called "xscreensaver". The manual pages have a "USING KDE" section.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,740

Re: KDE: "screen locker is broken" [RESOLVED]

Look at your journal, it's likely your graphics card/xorg takes a dive. If you are currently using xf86-video-intel try without it. Modern intels tend to work better (and there are quite a few known issues with it and the way KDE uses the graphics card, that the modesetting driver is almost always a good  bet on intel and KDE)

Edit: If you don't see anything relevant, you might want to post these logs, maybe more eyes will find more.

Last edited by V1del (2018-04-29 18:56:51)

yochaigal

Member

From: Boston

Registered: 2011-02-06

Posts: 202

Re: KDE: "screen locker is broken" [RESOLVED]

Here some logs, if that helps:

journalctl

Xorg

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,740

Re: KDE: "screen locker is broken" [RESOLVED]

A full journal would be nice, including the kernel messages, use

journalctl -b > journal.log

or similar to write out a log. But two things, anyway from what we see so far, as mentioned try removing xf86-video-intel and any config file in  /etc/xorg.conf.d making a reference to intel and more importantly set up your microcode updates

yochaigal

Member

From: Boston

Registered: 2011-02-06

Posts: 202

Re: KDE: "screen locker is broken" [RESOLVED]

I did do that, I just cut out all the bits I didn't want to post (plasmashell records *every* notification I get).
When I get a chance I'll reboot and test lock again, to create a clean log file.

I'm up to date on microcode. Wait, what is the alternative to xf86-video-intel?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,740

Re: KDE: "screen locker is broken" [RESOLVED]

Not using any xf86-video driver is the alternative. Xorg will then use a built  in modesetting driver, that can be used by any GPU with working modesetting support, which is all of the open source ones. xf86-video-intel doesn't have many active developers anymore and especially on newer intel graphics tends to have problems. It usually performs better in an uncomposited environment since it has specifically written 2D code, since you are on KDE and likely using Kwin's compositing that is largely irrelevant for you.

yochaigal

Member

From: Boston

Registered: 2011-02-06

Posts: 202

Re: KDE: "screen locker is broken" [RESOLVED]

Uninstalling xf86-video-intel had no effect.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,740

Re: KDE: "screen locker is broken" [RESOLVED]

Post the log, are you sure you are doing the microcode update? Your kernel commandline should have mention of intel-ucode.img which it doesn't. You might also want to try and use linux-lts

Last edited by V1del (2018-05-01 20:26:13)

yochaigal

Member

From: Boston

Registered: 2011-02-06

Posts: 202

Re: KDE: "screen locker is broken" [RESOLVED]

Relevant grub.cfg config:

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-24cca9de-6f8a-4d39-a4d1
-cc312ba9c27c' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='hd0,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,msdos1' --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  5934f3e6-196e-4fff-94c5-7747ef253765
        else
          search --no-floppy --fs-uuid --set=root 5934f3e6-196e-4fff-94c5-7747ef253765
        fi
        echo    'Loading Linux linux ...'
        linux   /vmlinuz-linux root=/dev/mapper/vg0-root rw  quiet
        echo    'Loading initial ramdisk ...'
        initrd  /intel-ucode.img /initramfs-linux.img

yochaigal

Member

From: Boston

Registered: 2011-02-06

Posts: 202

Re: KDE: "screen locker is broken" [RESOLVED]

Switching over to linux-lts did not resolve the problem either, unfortunately.

nesk

Member

Registered: 2011-03-31

Posts: 181

Re: KDE: "screen locker is broken" [RESOLVED]

Post you X config(s).

Seriously, try temporarily switching to xscreensaver https://wiki.archlinux.org/index.php/XScreenSaver
It will help to identify the source of the problem - if xscreensaver works then it's a KDE screenlocker problem, if not - probably X.org problem.
You mentioned kernel and X.org updates - are you sure no KDE components were updated?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,740

Re: KDE: "screen locker is broken" [RESOLVED]

A more complete journal log would still be nice as well, from the small excerpt we have it looks like polkit loses connection to the session. How do you login and start KDE? What's the output of

loginctl show-session $XDG_SESSION_ID #Before locking the screen, Take note of the Id, and afterwards from the tty using that session id and check how the output differs

Last edited by V1del (2018-05-05 10:22:00)

yochaigal

Member

From: Boston

Registered: 2011-02-06

Posts: 202

Re: KDE: "screen locker is broken" [RESOLVED]

OK, here is a complete log from boot, I initiate the lockscreen at the very end.

journalctl

I use SDDM, which logs in automatically to my user (I have LUKS encryption on boot via plymouth). The loginctl id is always c1, which is what I have to unlock every time via tty2. What do you mean, check how the output differs? If I list the sessions in tty nothing prints out.

Last edited by yochaigal (2018-05-05 10:48:59)

yochaigal

Member

From: Boston

Registered: 2011-02-06

Posts: 202

Re: KDE: "screen locker is broken" [RESOLVED]

FYI, xscreensaver works fine, so this is definitely a KDE issue. I forgot to mention that. Nesk asked, I hadn't gotten around to doing it.

I've had a ton of KDE updates since this thread started; problem persists however.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,740

Re: KDE: "screen locker is broken" [RESOLVED]

FWIW I have never had an issue with the lock screen. If this had an actual bug, many more reports would be visible, for some reason you are losing your connection to polkit I'm not entirely sure why.

Definitely a KDE issue isn't really that clearly defined just because xscreensaver works. xscreensaver does implement many things differently, I doubt that it has systemd session integration.

stefanqn

Member

Registered: 2018-05-23

Posts: 1

Re: KDE: "screen locker is broken" [RESOLVED]

don't use "World Map" as wallpaper type in KDEs locking screen configuration. fixed it for me

yochaigal

Member

From: Boston

Registered: 2011-02-06

Posts: 202

Re: KDE: "screen locker is broken" [RESOLVED]

Thanks - that fixed it for me.