https://bugs.kde.org/show_bug.cgi?id=478287
Matt Fagnani <matt.fagn...@bell.net> 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 <matt.fagn...@bell.net> ---
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.
