GNOME Bugzilla – Bug 272556
Closing Evolution caushes a "crash error"
Last modified: 2013-09-10 14:04:15 UTC
Distribution: Debian 3.1 Package: Evolution Priority: Normal Version: GNOME2.9.91 2.1.5 Gnome-Distributor: Ubuntu Synopsis: Closing Evolution cashes a "crash error" Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.1.5 BugBuddy-GnomeVersion: 2.0 (2.9.1) Description: Description of the crash: Steps to reproduce the crash: 1. Using Evolution 2. Closing it with the mouse on the top right (X) 3. Crash error message appears Expected Results: Close normal How often does this happen? After having used this new Evolution version with hoary it happend all the times I had started Evolution (2 times so far). Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.2' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232501216 (LWP 10248)] [New Thread -1393562704 (LWP 10282)] [New Thread -1385170000 (LWP 10276)] [New Thread -1376777296 (LWP 10275)] [New Thread -1368384592 (LWP 10274)] [New Thread -1351599184 (LWP 10272)] [New Thread -1326421072 (LWP 10269)] [New Thread -1309635664 (LWP 10267)] [New Thread -1292637264 (LWP 10265)] [New Thread -1284244560 (LWP 10264)] [New Thread -1248855120 (LWP 10262)] [New Thread -1266033744 (LWP 10261)] [New Thread -1257641040 (LWP 10260)] [New Thread -1239217232 (LWP 10250)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 55657
Thread 14 (Thread -1239217232 (LWP 10250))
Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** Bug 274493 has been marked as a duplicate of this bug. ***
*** Bug 300656 has been marked as a duplicate of this bug. ***
Stack trace in bug 300656 contains some debugging symbols (not much, but some...)
My problem has seemed to have gone away in the latest Fedora Rawhide Builds version 2.2.2. Christian, you should see if this is is fixed for you so we can close this.
I am still using Evolution 2.2.1.1 and it continues to crash. As soon as an update for my distribution (Ubuntu Hoary) is available I will let you know. If I can send more debugging information in the meantime please let me know how.
i'll close assuming this is fixed in newer releases.
*** Bug 313217 has been marked as a duplicate of this bug. ***
I still get the same problem in evolution 2.2.2 (Debian package 2.2.2-4, my report being in bug #313217)... I'd like very much to know what exactly fixed the problem in the 2.2.2 package from Fedora in order to be able to patch, upgrade or whatever is needed to have the same version in Debian correct it also... Could anybody provide this information ? Thanks in advance. Best regards,
FYI, I am still using Evolutin 2.2.1.1 and the bug is still there. My workaround is to not close Evolution at all when logging out from Gnome.
*** Bug 307795 has been marked as a duplicate of this bug. ***
*** Bug 306452 has been marked as a duplicate of this bug. ***
*** Bug 316453 has been marked as a duplicate of this bug. ***
*** Bug 318551 has been marked as a duplicate of this bug. ***
*** Bug 319141 has been marked as a duplicate of this bug. ***
I'm using 2.4.1 and this ain't fixed...
I am reopening this bug as I have found 5 new bugs that contain the same stack trace as this one (Please see the above 5 bugs marked as duplicates, I have verified the stack trace using simple-dup-finder.cgi script as well as manually). Some of these duplicates were found in 2.2.x and some in 2.4.x. As many of these dup bugs were find recently, we can say with some surety that the problem is still present in the current evolution sources.
reassigning old bugs to get rid of triage@ximian.com as assignee. adding version number.
*** Bug 322723 has been marked as a duplicate of this bug. ***
*** Bug 328436 has been marked as a duplicate of this bug. ***
Yet another diplicate. Originally reported for 2.2.x, still valid in 2.4.x Raising Priority. According to the stacktrace, looks like Mailer. Shifting over.
hi Michael, is it possible for you at attach your vfolders.xml file in ~/.evolution/mail/ - that will actually help me in solving the issue. Currently there is no way i am able to reproduce this problem. Changing to NEEDINFO, please REOPEN when back with information. TIA
Created attachment 58069 [details] vfolders.xml file from crashing setup Ok, here's my vfolders.xml. /Mikael
BTW, if some of the folder names look strange, it's because of bug #323106. This crash occured before then, however. /Mikael
Thanks for providing the info, Mikael. REOPENing.
hey Mikael, is it possible for you to delete your vfolder settings and re-create them?? I tried creating similar rules as of that in your setup: * mails greater than 0 * mails which are flagged I really dont see the crash. I think its one of those importing of settings when upgrading bug.
So, this is what I did: 1. Closed evo 2. moved mail/vfolders.xml to mail/vfolders.xml-old 3. Removed mail/vfolder (a directory) 4. Started evo 5. Recreated my vfolders 6. Closed evo (no crash!) 7. Moved mail/vfolders.xml-old to mail/vfolders.xml 8. started evo (vfolders look ok) 9. Closed evo (no crash!) So it seems you were right - and I can no longer reproduce the crash! /Mikael
(BTW: the size > 0Kb was a bad workaround for the "Match all" option, which I have now found!)
Created attachment 59031 [details] Reoccuring crash Unfortunately, evo has now started to crash on exit *again*. So, the "recreate vfolders" did something to help, but not permanently. Is there something in my mail/vfolder dir that can help? /Mikael
quoting comment 28: > Unfortunately, evo has now started to crash on exit *again*. This sounds fimilar. IIRC Evo did not crash for me on closing, after setting up a fresh one. At some point later, it started to, again. I believe I have went though this more than once already... (see bug 330157)
This is the same experience I have. On my computer 2 separate users use evolution. The bug is only happening to one of the two. My current setup is Evolution 2.4.1 on Ubuntu Breezy Badger. If I can provide more debug infos please advise how to do this.
*** Bug 331281 has been marked as a duplicate of this bug. ***
335267 also looks very similar, though the stacktrace is not totally identical.
*** Bug 336430 has been marked as a duplicate of this bug. ***
Still crashes on 2.6.0 (Debian)
(In reply to comment #34) > Still crashes on 2.6.0 (Debian) > I confirm it's still there, also on Debian (testing) : Backtrace was generated from '/usr/bin/evolution-2.6' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233324352 (LWP 19673)] [New Thread -1291326544 (LWP 19685)] [New Thread -1282536528 (LWP 19681)] [New Thread -1265845328 (LWP 19677)] [New Thread -1257452624 (LWP 19676)] [New Thread -1248384080 (LWP 19675)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 68723
Thread 1 (Thread -1233324352 (LWP 19673))
retargetting.
*** Bug 345170 has been marked as a duplicate of this bug. ***
*** Bug 346469 has been marked as a duplicate of this bug. ***
Still crashes on 2.7.3 (Ubuntu Edgy Eft).
Created attachment 70219 [details] Kyrre's vfolders.xml (crashing setup)
Hi! I just upgraded from the 1.x series to 2.6.2 (FC2 -> FC5), moving my mail setup with me. I had some trouble doing that, as i had started Evo once before copying over the "Evolution" folder. I then had to delete some folders (everything i found related to evo) in gconf. It then worked. (It would be a GOOD thing to have "import from evolution 1.x" in the import dialog...). Everything imported perfectly and works, even my fairly complicated vfolder setup (i'll attach my vfolders.xml). Except that it crashes on shutdown. At least it seems like no data being lost? I once managed to shut it down without crashing, by closing it very fast after starting the app. Not that i have been able to reproduce that...
*** Bug 374909 has been marked as a duplicate of this bug. ***
This particular bug is fixed in 2.8.x branch and current CVS head. Please reopen, if it is not fixed for you in these version. Thanks. *** This bug has been marked as a duplicate of 330157 ***
Will the fix be backported to the 2.6.x branch (or fedora 5 updated to that version)? I love evolution, imo its the best mailer around, but this crashing is really bugging me. As long as it isn't loosing data it isn't a major problem, but still...
kyrre: you have to ask your vendor (Fedora Core) for an update, we (here at GNOME) don't have anything to do with distro updates... :-)