Arch Linux

Are you using a slideshow in your lock screen?

Nope, just plain lock screen.

The screen saver is just a picture, and that part works fine.

Only kscreenlocker crashed.

Please post a full backtrace

Strangely, coredumpctl failed to catch that crash.
Thus no backtrace available.

Just interested no one else hit such crash.

BTW, my desktop and laptop all have the same problem, thus it shouldn't be that rare, especially my laptop has far less customization compared to my desktop.

Extra info:
Further looking into the journal, it looks like kscreenlocker_greeter is trying to add a lot of inotify.
I have a kernel source code which has a loop soft link, and limited inotify max.
So it kscreenlocker_greeter will easily hit ENOSPC when adding inotify.

Not sure why this happens.

17:07:37 adam-pc ksmserver[2259]: UnmapNotify: 140509215
17:07:37 adam-pc ksmserver[2259]: UnmapNotify: 140509219
17:07:37 adam-pc ksmserver[2259]: CreateNotify: 140509188
17:07:37 adam-pc ksmserver[2259]: CreateNotify: 140509192
17:07:37 adam-pc ksmserver[2259]: CreateNotify: 140509201
17:07:37 adam-pc kscreenlocker_greet[12230]: inotify_add_watch(/home/adam/.config/plasmarc) failed: (No space left on device)
17:07:37 adam-pc ksmserver[2259]: CreateNotify: 140509202
17:07:37 adam-pc ksmserver[2259]: CreateNotify: 140509204
17:07:37 adam-pc ksmserver[2259]: MapNotify: 140509202
17:07:37 adam-pc ksmserver[2259]: CreateNotify: 140509205
17:07:37 adam-pc ksmserver[2259]: MapNotify: 140509205
17:07:37 adam-pc kscreenlocker_greet[12230]: inotify_add_watch(/usr/share/plasma/desktoptheme/Arc-Dark/metadata.desktop) failed: (No space left on device)
17:07:37 adam-pc kscreenlocker_greet[12230]: inotify_add_watch(/usr/share/icons/Papirus-Dark/index.theme) failed: (No space left on device)
17:07:37 adam-pc kscreenlocker_greet[12230]: inotify_add_watch(/etc/fstab) failed: (No space left on device)
17:07:37 adam-pc ksmserver[2259]: CreateNotify: 140509214
17:07:38 adam-pc ksmserver[2259]: CreateNotify: 140509229
17:07:38 adam-pc org_kde_powerdevil[2313]: powerdevil: Scheduling inhibition from ":1.16" "My SDL application" with cookie 273 and reason "Playing a game"
17:07:38 adam-pc org_kde_powerdevil[2313]: powerdevil: Releasing inhibition with cookie 273
17:07:38 adam-pc org_kde_powerdevil[2313]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it
17:07:39 adam-pc kernel: kscreenlocker_g[12230]: segfault at 7ffbff7fdfe0 ip 00007efbfe417558 sp 00007ffbff7fdfb0 error 6 in libQt5Gui.so.5.13.1[7efbfe0a6000+414000]
17:07:39 adam-pc kernel: Code: e5 40 e9 6b ff ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 41 57 41 56 41 55 41 54 55 53 48 89 fb 48 81 ec c8 38 00 00 48 8b 6f 10 <48> 89 74 24 30 64 48 8b 04 25 28 00 00 00 48 >gg

can you post your kscreenlockerrc

[$Version]
update_info=kscreenlocker.upd:0.1-autolock

[Greeter]
Theme=com.github.varlesh.arc-dark

[Greeter][Wallpaper][org.kde.image][General]
Image=file:///home/adam/wallpapers/wallpaler.jpg

Just want to chime in, I'm seeing this exact issue. It appears to happen randomly? Was doing it nonstop last night, across reboots, this morning it doesn't want to. When it does happen the screen flashes black about 3 times, 5-10 seconds into the screen lock.

- This is a fresh install
- kscreenlockerrc is the same as adam's (wallpaper is a static image, only difference is I'm using breezedark theme)
- Tried playing with lock password time settings, same result regardless of that.

Dmesg spams what looks like the same thing when it happens:
kscreenlocker_g[21533]: segfault at 7ffd779e2fc0 ip 00007fd3c1c8e558 sp 00007ffd779e2f90 error 6 in libQt5Gui.so.5.13.1[7fd3c191d000+414000]
[11358.319064] Code: e5 40 e9 6b ff ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 41 57 41 56 41 55 41 54 55 53 48 89 fb 48 81 ec c8 38 00 00 48 8b 6f 10 <48> 89 74 24 30 64 48 8b 04 25 28 00 00 00 48 89 84 24 b8 38 00 00

Due to weekday work I won't be able to respond to anything new very often.

status with 5.17.1?

Wow, that was fast. I'm not seeing it happen so far, though I've only had a bit to test it. The locker seems a lot more responsive in general. Will update if I see it starting again.

Haven't see the bug any more since upgraded to .1

Upstream also said .1 would solve it. So I'll close the case.