Bug 469869

Summary: [regression] KCM_SDDM Crashes Utilizing over 100% CPU
Product: [Applications] systemsettings Reporter: John <kdelovaa>
Component: kcm_sddmAssignee: David Edmundson <kde>
Status: RESOLVED WORKSFORME    
Severity: crash CC: kde, nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.27.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description John 2023-05-16 20:44:21 UTC 
SUMMARY
***
When trying to change SDDM background "systemsettings kcm_sddm" crashes utilizing over 100% CPU.
***


STEPS TO REPRODUCE
1. Type "login" and chose "Login Screen (SDDM)"
2. Chose "Breeze (KDE Visual Design Group)" and click the secon icon "Change Background"
3. Nothing happens, but "systemsettings kcm_sddm" goes haywire utilizing over 100% CPU

OBSERVED RESULT
"systemsettings kcm_sddm"  crashes going haywire with over 100% CPU utilization.

EXPECTED RESULT
Revert changes that lead to this nasty regression.

SOFTWARE/OS VERSIONS
Linux: Archlinux (not Manjaro) 
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
sddm 0.19.0-9 (Archlinux)
x11
ADDITIONAL INFORMATION
Comment 1 Nate Graham 2023-05-17 19:50:20 UTC 
Did you miss the big banner in the template that said that if you're reporting a crash, you need to attach a backtrace of the crash? I notice you deleted that text, but did not attach a backtrace. C'mon, John, I know you can do better than this. :) Because if something crashed, we need a backtrace of it so we can figure out what's going on. Otherwise it's a waste of both of our time. So can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!
Comment 2 Bug Janitor Service 2023-06-01 03:45:31 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2023-06-16 03:45:29 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!