Bug 466223

Summary: [kded5] Crashes Intermittently, Affecting X11 Session in Odd Ways
Product: [I don't know] kde Reporter: nekonexus
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: nicolas.fella
Priority: NOR Keywords: drkonqi, needs_verification
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
URL: https://bugs.kde.org/attachment.cgi?id=156583
Latest Commit: Version Fixed In:
Attachments: Kcrash Dump Backtrace - Provided by Dr.Konqi & Debuginfod

Description nekonexus 2023-02-22 00:25:19 UTC
Created attachment 156583 [details]
Kcrash Dump Backtrace - Provided by Dr.Konqi & Debuginfod

SUMMARY
I'm not sure if this is the correct component for this bug, but KDED5 crashes intermittently when I leave the screen locked overnight. I was going to upload the report via Dr.Konqi but it claimed that it couldn't because kded5 doesn't, itself, have a component page.

Side effects of this include:
1) The system task tray hides all open applications that were occupying it
2) Open application windows are either closed or, if still open, have their UI blown up to an absurd size; forcing me to relaunch remaining applications
3) This happens intermittently even after reboots

STEPS TO REPRODUCE
1. Lock the session
2. Return tomorrow

OBSERVED RESULT
System oddities occur where elements are either hidden, closed, or scaled incorrectly

EXPECTED RESULT
These system oddities should not be present

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 6.1.12-273-tkg-pds (64-bit) - (https://github.com/frogging-family/linux-tkg)
KDE Plasma Version: 5.27.0 - (Compiled from sources as x86-64-v3 from a repo: https://git.harting.dev/ALHP/ALHP.GO)
Frameworks Version: 5.103.0
Qt Version: 5.15.8
Windowing System: X11
Display Resolution: 3840x2160
Plasma Display Global Scale: 200%

Non-default Configurations?
None.

ADDITIONAL INFORMATION
(Ask me any questions you might have)
Comment 1 Nicolas Fella 2023-02-22 11:19:11 UTC

*** This bug has been marked as a duplicate of bug 464590 ***