| Summary: | No crash info with kmail | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Arthur Pemberton <pembo13> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | andresbajotierra, christophe, kevin.kofler, rdieter, tuju |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Arthur Pemberton
2009-03-26 06:20:45 UTC
Version: (using KDE 4.2.1) Version-Release number of selected component (if applicable): kdepim-3.5.10-2.fc9 You have two different KDE versions mixed. So your KMail (part of kdepim) is using the old KDE3, and probably you don't have installed the "kdebase" package for KDE3 (which contains DrKonqi). So you are not getting the crash handler dialog for that app. Please, fix your installation. Thanks confirmed, looks like we (fedora) omitted drkonqi from packaging. That's not the issue. Our kdelibs3 is patched to use /usr/libexec/kde4/drkonqi from the KDE 4 kdebase-runtime. See https://bugzilla.redhat.com/show_bug.cgi?id=453243 where this was addressed long ago. Then, that's a different story. Reopening It may still turn out to be a downstream issue, mind you. But we have to figure out what's causing the bug. Now, this is a fun bug. I tried reproducing this with: kdepim-3.5.10-3.fc9.i386 kdelibs3-3.5.10-3.fc9.i386 kdebase-runtime-4.2.1-2.fc9.i386 What I did: 1. Install kdepim-debuginfo. 2. Run KMail. 3. Simulate a crash with: killall -SIGSEGV kmail Then I repeated only steps 2 and 3 multiple times, running KMail either from a Konsole with "kmail &" or from the menu. Interestingly, when I run KMail from a Konsole, I get the KDE 4 drkonqi popping up with valid backtraces including debugging symbols for kdepim. When I run it from the menu, it just vanishes. The apparent consistency might just be an accident, as for you it also doesn't work when run from a Konsole. According to yum: kdebase-runtime.i386 4.2.1-2.fc9 kdebase-runtime-libs 4.2.1-2.fc9 I've only ever ran it from Konsole as `kmail` not `kmail &` In both cases, `killall -SIGSEGV kmail` causes a KCrash report. Kmail has crashes on me several times since I installed the kdepim debug symbols, this is the first time I've seen it followed up by Kcrash report. There have been no significant changes to my system of late. If I can a real crash again, I'll attempt `kmail &` My suspicion is that it depends on where in the code the crash happens, which for the real crashes will always be the same place (for a given crash). Closing this bug as it is no longer reproducible. Still reproducible here, just killall -SIGABRT kmail. Also note that this might not be specific to KDE 3 apps at all, it has also been seen with Amarok 2.0. Version-Release number of selected component (if applicable): kdepim-3.5.10-2.fc9 This version of kdepim isn't maintained anymore. So unless you can reproduce the issue with KMail 1.11.x or higher, please close this bug report. i see this too, unfortunately. With what apps? KMail? What version? Marking as NEEDSINFO Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you! |