https://bugs.kde.org/show_bug.cgi?id=413442
Bug ID: 413442
Summary: kscreenlocker crashes after several hours of idle time
Product: kscreenlocker
Version: unspecified
Platform: Slackware Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: greeter
Assignee: plasma-b...@kde.org
Reporter: ste...@gmail.com
CC: bhus...@gmail.com
Target Milestone: ---
Created attachment 123479
--> https://bugs.kde.org/attachment.cgi?id=123479&action=edit
Console output from manually starting kscreenlocker_greet with --testing option
SUMMARY
kscreenlocker crashes after several hours of idle time
STEPS TO REPRODUCE
1. Screen Locking configured to start automatically after 20 minutes
2. Unlocking without password setting: 300 seconds
3. After waking from sleep: not set
4. Appearance settings follows in steps 5-10 below
5. Media controls: set Show
6. Wallpaper type: Slideshow
7. Positioning: Scaled and Cropped
8. Order: Random
9. Change every: 0 hours 2 minutes 0 seconds
10. All 22 stock wallpapers are selected
OBSERVED RESULT
After several hours of idle (~ 6 to 8 hours) the screen locker crashes with
below message.
“The screen locker is broken and unlocking is not possible anymore. In order to
unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2), log in as root and
execute the command:
# ck-unlock-session <session-name>”
EXPECTED RESULT
No crash. Continued operation.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Slackware/14.2 -current
(available in About System)
KDE Plasma Version: 5.17.0
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1
ADDITIONAL INFORMATION
package: kscreenlocker-5.17.0-x86_64-1alien
(behavior not observed in previous package kscreenlocker-5.16.5-x86_64-1alien
and can be remedied by installing it)
This behavior appears related to bugs 405219 and 371175.
When disabling the automatic start and manually starting kscreenlocker with:
"/usr/lib64/kscreenlocker_greet --testing" a segmentation fault will occur. The
console output which precedes the seg fault is added as an attachment.
Some relevant system log output in /var/log/messages:
Oct 24 06:40:50 kiai dbus-daemon[1777]: [session uid=1000 pid=1775]
Successfully activated service 'org.kde.runners.baloo'
Oct 24 07:00:01 kiai -- MARK --
Oct 24 07:20:01 kiai -- MARK --
Oct 24 07:40:01 kiai -- MARK --
Oct 24 08:00:01 kiai -- MARK --
Oct 24 08:20:01 kiai -- MARK --
Oct 24 08:40:01 kiai -- MARK --
Oct 24 09:00:01 kiai -- MARK --
Oct 24 09:20:01 kiai -- MARK --
Oct 24 09:40:01 kiai -- MARK --
Oct 24 10:00:01 kiai -- MARK --
Oct 24 10:20:01 kiai -- MARK --
Oct 24 10:40:01 kiai -- MARK --
Oct 24 11:00:01 kiai -- MARK --
Oct 24 11:20:01 kiai -- MARK --
Oct 24 11:40:01 kiai -- MARK --
Oct 24 12:00:01 kiai -- MARK --
Oct 24 12:20:01 kiai -- MARK --
Oct 24 12:40:01 kiai -- MARK --
Oct 24 13:00:01 kiai -- MARK --
Oct 24 13:09:02 kiai kernel: [191359.983592] kscreenlocker_g[25671]: segfault
at 7f7e20008eb8 ip 00007f7b52abce00 sp 00007fffa506cfb0 error 4 in
libQt5Core.so.5.13.1[7f7b528ed000+2d3000]
--
You are receiving this mail because:
You are watching all bug changes.
