[plasmashell] [Bug 478287] drkonqi, kioslave5, and gdb crashed when creating traces of plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=478287 Akseli Lahtinen changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478287] drkonqi, kioslave5, and gdb crashed when creating traces of plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=478287 Matt Fagnani changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 Status|RESOLVED|REPORTED --- Comment #10 from Matt Fagnani --- (In reply to Akseli Lahtinen from comment #9) > Hi, has this issue appeared on Fedora 40 KDE? > > If so, can you make sure that you have debug symbols installed and send a > backtrace with them included? > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Backtraces > > Thanks! I haven't seen this problem with 6.0.0-6.0.90 in Fedora 40 and Rawhide in which I think drkonqi used the core dumps created by systemd-coredump instead of attaching gdb directly to the crashed plasmashell processes. I don't think this problem would happen with 6.0 and higher because the 40 s timeout before the plasmashell.service is killed by systemd isn't a factor any longer. The 5.27 branch might still be affected, but I haven't used it in a few months. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478287] drkonqi, kioslave5, and gdb crashed when creating traces of plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=478287 Akseli Lahtinen changed: What|Removed |Added CC||akse...@akselmo.dev Resolution|--- |WAITINGFORINFO Status|REOPENED|RESOLVED --- Comment #9 from Akseli Lahtinen --- Hi, has this issue appeared on Fedora 40 KDE? If so, can you make sure that you have debug symbols installed and send a backtrace with them included? https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Backtraces Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478287] drkonqi, kioslave5, and gdb crashed when creating traces of plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=478287 Matt Fagnani changed: What|Removed |Added Status|RESOLVED|REOPENED Component|general |generic-crash Ever confirmed|0 |1 Resolution|BACKTRACE |--- Version|5.27.9 |5.27.10 Product|drkonqi |plasmashell Target Milestone|--- |1.0 --- Comment #8 from Matt Fagnani --- This problem still happens with 5.27.10. I'm reassigning this report to plasmashell because /usr/lib/systemd/user/plasma-plasmashell.service had TimeoutSec=40sec. When drkonqi was still creating the trace of plasmashell with gdb 40 s after plasmashell crashed, systemd aborted plasma-plasmashell.service's processes plasmashell, drkonqi, kioslave5, and gdb. Those processes were aborted because Fedora services use the drop-in configuration file /usr/lib/systemd/user/service.d/10-timeout-abort.conf which had TimeoutStopFailureMode=abort. The default timeout of 40 s for plasma-plasmashell.service wasn't long enough for drkonqi and gdb to trace plasmashell when qt5 debuginfo packages were installed and report the crash. The tracing didn't take as long when qt5 debuginfo packages weren't installed, but there still wouldn't be enough time to report crashes in 40 s. The crashes' core dumps weren't saved for viewing with coredumpctl so the crashes' information was lost. Thanks. -- You are receiving this mail because: You are watching all bug changes.
