https://bugs.kde.org/show_bug.cgi?id=438046
Bug Janitor Service changed:
What|Removed |Added
Resolution|BACKTRACE |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=438046
--- Comment #6 from Bug Janitor Service ---
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
https://bugs.kde.org/show_bug.cgi?id=438046
--- Comment #5 from Lyubomir ---
Sorry for the spam, just fount out one can apport-unpack the crash report and
gdb the coredump afterwards. I suggest including such apport instructions here:
https://bugs.kde.org/show_bug.cgi?id=438046
--- Comment #4 from Lyubomir ---
Just installed systemd-coredump over apport. It shows many crashes, all of
which "missing" corefiles. It seems this bug would be a no-op.
That said can apport be used for invoking gdb (and if so updating KDE
https://bugs.kde.org/show_bug.cgi?id=438046
--- Comment #3 from Lyubomir ---
My memory betrays me, but judging from the plain stupid comment i made
("Attaching stacktrace from forced SIGSEGV") i guess i manually send signal 11
using htop to the process and that should be why it crashed.
If this
https://bugs.kde.org/show_bug.cgi?id=438046
Nate Graham changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Summary|Dolphin high CPU
