Bug 608163
| Summary: | [abrt] crash in evolution-2.30.1-8 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Linuxguy123 <linuxguy123> | ||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 13 | CC: | agentbwoy007, alex-kas, arouse, benoit.alary, bmillett, christoph.wickert, cristian.colombo, devel.niks, dimi, dimitriakos, dlesage, don_dietz, drewskiwooskie, eck3ko, flokip, gene02, gfullmer, ian, james, jan_schaefer, jeremy, jhauva, jje47, kjb, kmb4215, lkundrak, loup.des.neiges, lucilanga, mbarnes, mcrha, milan, mstrewe, naoki, oded, oriol.rius, palango, peter.green, pkoehrer, rafeek, richard.hogaboom, rouckat, russo.lutions, sb, storri, timothy.mcconnell, trweniger, tstclair, warren.sturm, wdc | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | abrt_hash:cbfd3bf64dff635c69f25a52b9ac7d68a5c4cddb | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-06-27 18:56:55 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Linuxguy123
2010-06-25 20:48:40 UTC
Created attachment 426987 [details]
File: backtrace
It will crash a dozen times in a day of working at my computer. Evolution was perfectly stable in F12. This all started with the upgrade to F13. Some of my email folders have in excess of 200K messages in them. These days evolution generally just starts right up again. When it was first crashing in F13, I had to do an evolution --force-shutdown to get it to run again. Everything else is stable on my computer. $ uname -a Linux localhost.localdomain 2.6.33.5-124.fc13.i686.PAE #1 SMP Fri Jun 11 09:42:24 UTC 2010 i686 i686 i386 GNU/Linux Firefox wasn't stable when I first upgraded, but it is now. I did a yum remove \*evolution\* and then a yum install evolution. Let me know if you need anything else. Created attachment 427005 [details]
abrt trace
It did it again, a couple times. Here is the trace from the last one.
BTW: It would be nice if ABRT had some means to allow the user to attach a trace to an existing bug.
Created attachment 427010 [details]
Another one
Here is another crash trace.
Thanks for a bug report. Each backtrace is different, the first seems like something not much related to evolution itself, "only" possible some memory issue caused by Evolution; the second comes from gnome-key-ring, and the third is from evolution, but as you do not have installed debug info packages for evolution, then it doesn't show line numbers for code in evolution. But maybe they all are related to the same issue, I do not know yet. Could you install debug info packages for gtkhtml3, evolution-data-server, evolution and if you use also evolution-exchange and evolution-mapi, and then run evolution as follows, please? $ G_SLICE=always-malloc valgrind evolution &>evo.log And upload here a result of your crashing evolution, together with exact version numbers of installed evolution-data-server and evolution and other packages you'll install debug information for, please? Also make sure the evo.log file you'll upload here will not contain any private information, even this kind of log usually doesn't contain any. Thanks in advance. I don't want to say this too hastily, but I think its solved. According to ABRT, the last crash I had was Saturday, June 26th at 1:35 PM. According to /var/log/yum.log, the following packages were installed later that day. Jun 26 21:54:45 Updated: gnome-keyring-2.30.3-1.fc13.i686 Jun 26 21:54:46 Updated: gtkhtml3-3.30.2-1.fc13.i686 Jun 26 21:54:48 Updated: evolution-data-server-2.30.2-2.fc13.i686 Jun 26 21:54:48 Updated: baekmuk-ttf-fonts-common-2.2-29.fc13.noarch Jun 26 21:54:51 Updated: baekmuk-ttf-dotum-fonts-2.2-29.fc13.noarch Jun 26 21:54:54 Updated: baekmuk-ttf-gulim-fonts-2.2-29.fc13.noarch Jun 26 21:54:57 Updated: baekmuk-ttf-hline-fonts-2.2-29.fc13.noarch Jun 26 21:55:00 Updated: baekmuk-ttf-batang-fonts-2.2-29.fc13.noarch Jun 26 21:55:01 Updated: baekmuk-ttf-fonts-ghostscript-2.2-29.fc13.noarch Jun 26 21:55:01 Updated: gnome-keyring-devel-2.30.3-1.fc13.i686 Jun 26 21:55:03 Updated: python-foolscap-0.5.1-1.fc13.noarch Jun 26 21:55:20 Updated: evolution-2.30.2-1.fc13.i686 Jun 26 21:55:20 Updated: gnome-keyring-pam-2.30.3-1.fc13.i686 When I refreshed evolution the day previous to that, I had the following: Jun 25 10:30:15 Installed: evolution-data-server-2.30.1-2.fc13.i686 Jun 25 10:30:21 Installed: evolution-2.30.1-8.fc13.i686 Evolution went from 2.30.1-8 to 2.30.2-2 and gnome-keyring was bumped as well. I think its been totally solid since the update on June 26th. I'll monitor the situation and perform the steps you requested should it crash again. Thanks for giving my bug report some attention. ABRT rules ! *** Bug 574142 has been marked as a duplicate of this bug. *** *** Bug 597224 has been marked as a duplicate of this bug. *** *** Bug 597237 has been marked as a duplicate of this bug. *** *** Bug 597367 has been marked as a duplicate of this bug. *** *** Bug 598717 has been marked as a duplicate of this bug. *** *** Bug 600309 has been marked as a duplicate of this bug. *** *** Bug 600541 has been marked as a duplicate of this bug. *** *** Bug 600848 has been marked as a duplicate of this bug. *** *** Bug 602488 has been marked as a duplicate of this bug. *** *** Bug 603880 has been marked as a duplicate of this bug. *** *** Bug 604426 has been marked as a duplicate of this bug. *** *** Bug 605350 has been marked as a duplicate of this bug. *** *** Bug 605762 has been marked as a duplicate of this bug. *** *** Bug 606041 has been marked as a duplicate of this bug. *** *** Bug 606218 has been marked as a duplicate of this bug. *** *** Bug 606338 has been marked as a duplicate of this bug. *** *** Bug 606780 has been marked as a duplicate of this bug. *** *** Bug 607165 has been marked as a duplicate of this bug. *** *** Bug 608896 has been marked as a duplicate of this bug. *** *** Bug 608926 has been marked as a duplicate of this bug. *** *** Bug 609009 has been marked as a duplicate of this bug. *** *** Bug 609670 has been marked as a duplicate of this bug. *** *** Bug 610326 has been marked as a duplicate of this bug. *** *** Bug 613718 has been marked as a duplicate of this bug. *** *** Bug 614429 has been marked as a duplicate of this bug. *** *** Bug 616308 has been marked as a duplicate of this bug. *** *** Bug 616550 has been marked as a duplicate of this bug. *** *** Bug 616836 has been marked as a duplicate of this bug. *** *** Bug 621311 has been marked as a duplicate of this bug. *** *** Bug 622131 has been marked as a duplicate of this bug. *** *** Bug 622815 has been marked as a duplicate of this bug. *** *** Bug 625675 has been marked as a duplicate of this bug. *** *** Bug 628010 has been marked as a duplicate of this bug. *** *** Bug 630427 has been marked as a duplicate of this bug. *** *** Bug 634694 has been marked as a duplicate of this bug. *** *** Bug 634796 has been marked as a duplicate of this bug. *** *** Bug 639966 has been marked as a duplicate of this bug. *** *** Bug 641897 has been marked as a duplicate of this bug. *** *** Bug 642889 has been marked as a duplicate of this bug. *** *** Bug 644848 has been marked as a duplicate of this bug. *** *** Bug 648451 has been marked as a duplicate of this bug. *** *** Bug 557462 has been marked as a duplicate of this bug. *** *** Bug 557750 has been marked as a duplicate of this bug. *** *** Bug 563290 has been marked as a duplicate of this bug. *** *** Bug 577337 has been marked as a duplicate of this bug. *** *** Bug 583570 has been marked as a duplicate of this bug. *** *** Bug 584858 has been marked as a duplicate of this bug. *** *** Bug 585192 has been marked as a duplicate of this bug. *** *** Bug 595824 has been marked as a duplicate of this bug. *** *** Bug 603756 has been marked as a duplicate of this bug. *** *** Bug 605412 has been marked as a duplicate of this bug. *** *** Bug 606502 has been marked as a duplicate of this bug. *** *** Bug 615042 has been marked as a duplicate of this bug. *** *** Bug 625826 has been marked as a duplicate of this bug. *** *** Bug 635584 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. |