Bug 492253
Summary: | No crash info with kmail | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Arthur Pemberton <pembo13> |
Component: | kdepim | Assignee: | Than Ngo <than> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 9 | CC: | arbiter, jreznik, kevin, ltinkl, rdieter, than |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-07-14 18:23:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Arthur Pemberton
2009-03-26 05:17:56 UTC
Do you have the KDE 4 kdebase-runtime installed on that machine? Our kdelibs3 is patched to use drkonqi from it. 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. Canceling needinfo, see the reporter's reply on the upstream bug. Closing this bug here as these problems are 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. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping What should we do about this bug? I'm moving to F11 soon, and no longer have this specific problem in F10 I still see this happening with the KDE 3 KMail on F9. I'll see if I can reproduce the problem with the current KDE 4 Amarok, though I'm not sure it's the same bug. I'll also try to send some signals to the KDE 4 KMail on F10 or F11 and see if I can get it to vanish with no crash report. Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |