Summary: | It just crashed and said send this report | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Tony Clifton <usaywot> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | cfeck, homoludens1000, hvulin, jamundso, jdseris, kdebug, leopard.not.a, nigel.howard4 |
Priority: | NOR | Keywords: | triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
backtrace
backtrace backtrace backtrace error message |
Description
Tony Clifton
2009-02-04 15:01:16 UTC
*** Bug 193334 has been marked as a duplicate of this bug. *** *** Bug 198592 has been marked as a duplicate of this bug. *** *** Bug 200480 has been marked as a duplicate of this bug. *** Created attachment 36448 [details]
backtrace
Created attachment 36449 [details]
backtrace
Created attachment 36450 [details]
backtrace
Created attachment 36451 [details]
backtrace
Created attachment 36452 [details]
error message
I also get this. It happens about twice a day at different times, sometimes when I mark mail as read or anything, even all by itself! I will try to attach some backtraces and a png of error. It runs on Jaunty in VirtualBox, with Hardy as the host. I liked the version in Hardy, it never crashes, had to change some feeds to get them to work in Jaunty, I don't see any new function in the Jaunty version so why should it crash? *** Bug 212446 has been marked as a duplicate of this bug. *** *** Bug 216785 has been marked as a duplicate of this bug. *** *** Bug 220140 has been marked as a duplicate of this bug. *** 1. This might be a duplicate of bug #194591, but I'm guessing. 2. The backtrace attachments should be mimetype text/plain. 3. The bug Description is not helpful. 4. My account here cannot do anything about 1-3 above. In summary, this bug needs love. This crash report is at least 3 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources. If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED) Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |