# Kscreenlocker segfaults when left alone

**URL:** <https://discuss.kde.org/t/kscreenlocker-segfaults-when-left-alone/12833>\
**Category:** Help\
**Tags:** plasma\
**Created:** [March 22, 2024, 1:46pm UTC](https://discuss.kde.org/t/kscreenlocker-segfaults-when-left-alone/12833 "2024-03-22T13:46:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![omortis](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/o/da6949/32.png) [@omortis](https://discuss.kde.org/u/omortis)\
**Post date:** [March 22, 2024, 1:46pm UTC](https://discuss.kde.org/t/kscreenlocker-segfaults-when-left-alone/12833/1 "2024-03-22T13:46:58Z")

</div>

Hello! With recent updates I have seen the system close my session forcefully and log me out. No reboot, just X11 closing me out while the screen is locked. Possibly when it’s coming back out of sleep. Looking in `dmesg` I see:

`[22580.921980] kscreenlocker_g[24508]: segfault at 5b28f44a1700 ip 00007fd83cb3603b sp 00007fff268872c0 error 4 in libQt5Gui.so.5.15.3[7fd83cae2000+4df000] likely on CPU 6 (core 0, socket 0)`

Seems to happen randomly. Any suggestions on how to get around it? Note that I lock with meta+l all day over and over again without issues.

Operating System: Ubuntu 22.04  
KDE Plasma Version: 5.24.7  
KDE Frameworks Version: 5.92.0  
Qt Version: 5.15.3  
Kernel Version: 6.5.0-26-generic (64-bit)  
Graphics Platform: X11  
Processors: 12 × 11th Gen Intel® Core™ i5-11600K @ 3.90GHz  
Memory: 31.2 GiB of RAM  
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2

I have exactly the same os config installed on my laptop and do not see the issue, there. My XPS uses the Intel GPU mostly.

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![ngraham](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/ngraham/32/64_2.png) [@ngraham](https://discuss.kde.org/u/ngraham)\
**Post date:** [March 24, 2024, 1:05am UTC](https://discuss.kde.org/t/kscreenlocker-segfaults-when-left-alone/12833/2 "2024-03-24T01:05:43Z")

</div>

Can you get a backtrace of the crash? See [Guidelines and HOWTOs/Debugging/How to create useful crash reports - KDE Community Wiki](https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl)

---

<div class="post-metadata">

**Author:** ![omortis](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/o/da6949/32.png) [@omortis](https://discuss.kde.org/u/omortis)\
**Post date:** [April 1, 2024, 12:10am UTC](https://discuss.kde.org/t/kscreenlocker-segfaults-when-left-alone/12833/3 "2024-04-01T00:10:34Z")

</div>

Sweet, thanks for that. Next time it happens I will do so. Unfortunately that workstation mainboard seems to have _died_ on me 2 days ago, so it may be a bit (waiting on an RMA).

Notably I am running the same exact OS and KDE level on this laptop and have never seen that error before…

Thanks again!
