https://bugs.kde.org/show_bug.cgi?id=501061
--- Comment #2 from stellarpower ---
Thanks for getting back to me quickly,
DrKonqi is installed, but generally hasn't shown up for past KWin crashes. I
guessed that gathering that info might be more complicated than it could
provide - e.g. that it was designed around single applications, not the whole
windowing system. I have now seen my first one a few days ago though so clearly
it works sometimes.
I still believe it'd be useful to be able to gather this info more suitably for
e.g. launching from a TTY. If I have to restart Plasma to get the window up,
wait for a load of previous applications to try to relaunch themselves, then
hope that the coredump can be read, etc. If the crash happens overnight then it
may be several hours until I'm awake to take a look which makes it harder to
collate that information, I'm not sure how long core dumps persist on this
machine, and it needs root access too. And after one just now the machine is
whirring away like mad trying to gather the information as well as restart what
I had open, and I was just seeing a lot of "Python exception: value has been
optimized out" messages for about five minutes until it finally got me a trace.
So in terms of bisecting the error I reckon it'd still be helpful to have as an
option getting a backtrace into the systemd logs at the exact point it went
down, so I can more clearly see what just happened, rather than try to
post-mortem next time the shell comes back up.. The UI all good stuff for
regular users, but as a poweruser, if I could e.g. wrap a plasma session
with/alongside DrKonqi from a TTY or otherwise, so I automatically get the
info, maybe specify a path to save timestamped logs (or I can do that myself),
get it in the journal, I think that would help in isolating patterns of what
happens.
Maybe some of this can be done already; and if so, then it'd be great to have
that in the wiki, as it doesn't really cover it in more detail. When I have a
spare minute I'll look to see more on how it works and what options there are.
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
