| Summary: | Kmail/Kontact crash | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Kris <krisgamrat> |
| Component: | tdepim | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | bugwatch, darrella, kb9vqf, krisgamrat |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Attachments: | Backtrace for Kontact crash -- 100% identical to Kmail crash backtrace | ||
|
Description
Kris
2012-11-13 19:38:46 CST
(In reply to comment #0) > Created attachment 978 [details] > Backtrace for Kontact crash -- 100% identical to Kmail crash backtrace > > Kontact crashes (almost consistently) a few seconds after launching. After > looking at the attached backtrace, I launched Kmail on it's own, and it > produces the same exact crash plus backtrace. > > This may be related to bug #1193, as usually just before the crash, I get the > behavior described in comment 1 of that bug. However, this isn't always the > case -- sometimes the crash occurs before the dialogs appear, but normally it > occurs after. Based on further testing, I do not believe it is related to bug #1193. I removed my Kmail config files and relaunched Kmail. I re-added my email accounts. The crash no longer occurs, even when I try to open an encrypted email (although bug #1193 still occurs). Unfortunately the backtrace you attached earlier is missing the debugging symbols needed for analysis. Furthermore, since you have indicated that this crash does not occur on a new profile, it will not be possible to debug this crash further without additional information. Can you install the tdepim debugging symbols (tdepim-trinity-dbg), cause KMail to crash again, and post the resultant backtrace to this bug report? Thanks! I am unable to produce this bug. Strangely, I am having a memory lapse -- I don't remember this happening. If it did, it may be related to me upgrading from stable to the nightlies (the date in the report is right around the time I was using 3.5.13.1). I have the debug package installed. If I can reproduce this bug, I will attach another backtrace. Note: Bug #1193 still occurs. Closing as resolved. As discussed, should the problem resurface Kris will provide a new backtrace. |