https://bugs.kde.org/show_bug.cgi?id=478287
--- Comment #4 from Matt Fagnani <matt.fagn...@bell.net> --- (In reply to Harald Sitter from comment #3) > You haven't posted a drkonqi backtrace though? There wasn't a drkonqi trace for the crash when creating the plasmashell trace because drkonqi crashed the second time when creating the drkonqi trace as I reported in "Another drkonqi window appeared for the drkonqi trace. I pressed Developer Information again in drkonqi. drkonqi crashed again." After reproducing the problem again twice, I think the trace involving File "/usr/share/drkonqi/gdb/preamble.py", line 518, in qml_trace_frame at the end of the summary section on my report was from the second drkonqi crash when creating the trace of the previous drkonqi crash. The following similar trace only appeared in the journal after I selected Developer Information in drkonqi to create the trace for the first drkonqi crash, but not when I didn't try to create the trace of the first drkonqi crash at a different time going through the reproduction steps. Dec 09 21:24:47 plasmashell[6584]: Traceback (most recent call last): Dec 09 21:24:47 plasmashell[6584]: File "<string>", line 1, in <module> Dec 09 21:24:47 plasmashell[6584]: File "/usr/share/drkonqi/gdb/preamble.py", line 620, in print_preamble Dec 09 21:24:47 plasmashell[6584]: print_qml_trace() Dec 09 21:24:47 plasmashell[6584]: File "/usr/share/drkonqi/gdb/preamble.py", line 578, in print_qml_trace Dec 09 21:24:47 plasmashell[6584]: ret = qml_trace_frame(frame) Dec 09 21:24:47 plasmashell[6584]: ^^^^^^^^^^^^^^^^^^^^^^ Dec 09 21:24:47 plasmashell[6584]: File "/usr/share/drkonqi/gdb/preamble.py", line 510, in qml_trace_frame Dec 09 21:24:47 plasmashell[6584]: value = symbol.value(frame) Dec 09 21:24:47 plasmashell[6584]: ^^^^^^^^^^^^^^^^^^^ Dec 09 21:24:47 plasmashell[6584]: KeyboardInterrupt Dec 09 21:24:47 plasmashell[6584]: /tmp/drkonqi.qnFYEn:3: Error in sourced command file: Dec 09 21:24:47 plasmashell[6584]: Error while executing Python code. Dec 09 21:24:47 systemd[3541]: plasma-plasmashell.service: Failed with result 'timeout'. Dec 09 21:24:47 systemd[3541]: plasma-plasmashell.service: Consumed 1min 58.780s CPU time. Dec 09 21:24:47 systemd[3541]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 3. Dec 09 21:24:47 systemd[3541]: Starting plasma-plasmashell.service - KDE Plasma Workspace... The creation of the trace for the plasmashell crash took 20-40 seconds and appeared to get SIGTERM sent to plasma-plasmashell.service which timed out instead of terminating and resulted in SIGABRT being sent to plasmashell, drkonqi, kioslave5, and gdb. I don't know what specifically during the plasmashell trace creation resulted in the SIGTERM being sent to plasma-plasmashell.service. Thanks. -- You are receiving this mail because: You are watching all bug changes.
