Summary: | kontact crashes in background with signal 6 | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | bve |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | andresbajotierra, kde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | kcrash backtrace with "kdepim-dbg" |
Description
bve
2009-04-02 09:37:42 UTC
The crash information isn't very useful. You can try to install the "kdepim-dbg" package in order to get a complete backtrace the next time. YOu can also run KMail/Kontact from the Konsole and then paste the shell output after the app crashed, here. (specially the "ASSERT" line) Thanks for reporting. Same behavior/backtrace for me. Having: KDE 4.2.2 Kontact 1.4.2 KMail 1.11.2 Just installing "kdepim-dbg" right now to get a `better` backtrace for this bug. Created attachment 32849 [details] kcrash backtrace with "kdepim-dbg" KCrash Backtrace, after Kontact-Crash. "kdepim-dbg" is installed. Just added the same Attachement at Bug 187736. Just a Question: Why i didnt find "#188641" at "Search Existing-Report", only at "Check for Duplicate Bugs"? @Jens Schmidt: your crash seems to be different from this report and even different from bug 187736. (the crash traces are indeed different, so it's a different crash). There are a lot of crash reports but a lot of them are different and unique. Your crash seems to be more like bug 189376: (compare the functions name and order) Anyway I can't assure that they are indeed duplicates. So the best is put every crash on a NEW bug report and let the bugs.kde.org maintainers / developers decide if they are the same crash or not. Thanks Closing the old crash reports which don't have a useful backtrace. Thanks. |