Summary: | kded crashes sometimes on startup, breaks some functionality | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Pascal Maillard <pascalmaillard> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | ben, cfeck |
Priority: | NOR | ||
Version: | 4.8 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Pascal Maillard
2012-11-09 09:25:37 UTC
If you can reproduce the crash, please add a backtrace. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Hi, I'd like to provide a backtrace, I am uncertain about two points though:
1) Of which packages should I install the debug versions (only kdelibs and
kdebase or more?)
2) The usual dialog that opens when an application crashes does not open in my
case. I only infer that kded crashed from the fact that it was running at some
point (see .xsession-errors file), but not anymore when startup is finished.
How can I see a backtrace in this case (assuming that the debug packages are
installed)? Do I have to start kde in a special way?
Am Freitag, 9. November 2012, 10:55:10 schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=309795
>
> Christoph Feck <christoph@maxiom.de> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |christoph@maxiom.de
>
> --- Comment #1 from Christoph Feck <christoph@maxiom.de> ---
> If you can reproduce the crash, please add a backtrace. For more
> information, see
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful
> _crash_reports
Which debug symbols are missing can be best seen when looking for "?" lines in the backtrace. If unsure, ask in a forum of your distribution. If kded4 crashes without showing the Dr. Konqi crash dialog window, please generate the backtrace with "gdb" from Konsole: killall kded4 gdb --args kded4 --nofork run (wait for crash) bt More information can be found in the link I posted. Thanks for your instructions. I ran kded from gdb as you said but I cannot
reproduce the error anymore and kded does not crash. Can you please tell me
how I can run gdb like this at startup ?
Am Samstag, 10. November 2012, 13:23:50 schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=309795
>
> --- Comment #3 from Christoph Feck <christoph@maxiom.de> ---
> Which debug symbols are missing can be best seen when looking for "?" lines
> in the backtrace. If unsure, ask in a forum of your distribution.
>
> If kded4 crashes without showing the Dr. Konqi crash dialog window, please
> generate the backtrace with "gdb" from Konsole:
>
> killall kded4
> gdb --args kded4 --nofork
> run
> (wait for crash)
> bt
>
> More information can be found in the link I posted.
Unmaintained version - let us know if it happens with more current versions. |