Summary: | KDE daemon error report | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | mahendra <mahendra> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | andresbajotierra, Brian.Meg, finex, lorenzo, mail, mumismo, Sroka.Steven |
Priority: | NOR | Keywords: | needs_verification |
Version: | 4.1.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
mahendra
2008-11-21 14:31:48 UTC
I have pasted the carsh report as it is Can you explain if and how the bug is reproducible? What did you do for having this crash? If you can reproduce the crash, you should install the debug enabled packages and provide a new backtrace. Read this page for the instructions: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Thanks! Same bug. Happened 3 times, always when running tasks related with kpackage-update. The backtrace was void or poor, too poor to found usable infos... nothing too in logs... :-( sorry. Still keep an eye on that, will try to get more verbosity in some way and will say back something. Ciao. @Lorenzo: if you want, you can follow this guide in order to have more detailed backtrace. http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports *** Bug 176052 has been marked as a duplicate of this bug. *** I have taken a look to downstream (launchpad), they don't have any bug about this. *** Bug 176189 has been marked as a duplicate of this bug. *** *** Bug 176258 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 165548 *** |