SUMMARY No backtrace unfortunately because even Dr Konqi is crashing. What happened is that for some time, I wasn't using Breeze directly but actually forks which are being compiled locally, like ClassikStyles and Lightly. It is probably because I was using them, that I didn't realize how broken breeze was. I enabled it once to try replicate another bug I found but then all applications or anything really that would use Breeze in context menus or another form, crash immediately. It also applied to Latte Dock, from all things. I'm on the KDE Unstable repos for openSUSE since it's easier to test it that way. I want to generate a backtrace to see how I can make this bug report more useful but without Dr Konqi or the assistant to install debug symbols, I'm not sure how to do that System is still usable if I'm using another Widget Style like the ones I cited above but otherwise... I don't know what could have happened. Not sure if could have been old config files either because I haven't swapped home directories ever since I started using this computer about a year ago
YOu can get a backtrace using `gdb` manually. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports for how.
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!
I've tried obtaining a backtrace with drkonqi, since some attempts do keep it running but it says the debugger has quit unexpectedly. Other times it takes an exceedingly long time and a backtrace is not generated. Then I tried running gdb manually with system settings, which is one of the apps that crash almost immediately after launching. After typing the backtrace command, it displayed "No stack". The same appeared for dolphin and latte-dock, which also crash in similar situations. Latte does not even display. Dolphin crashes whenever a context menu is open. System Settings may or not crash, depending on what is happening. This allows me to switch off from Breeze after some persistence. I'll keep insisting with Dr Konqi and see if it spits a backtrace without crashing first, unless there is something about gdb that I'm missing
Created attachment 144363 [details] System Settings crash related to this report Attaching a backtrace made by drkonqi after some persistence
Created attachment 144364 [details] Same as the previous backtrace but with dolphin instead Another backtrace but under different circumstances, in case the previous one is not enough
Thanks, that's helpful! *** This bug has been marked as a duplicate of bug 444519 ***