GNOME Bugzilla – Bug 270822
Crash: Evolution "unexpectedly exits" upon being launched
Last modified: 2013-09-10 14:03:26 UTC
Distribution: Debian 3.1 Package: Evolution Priority: Blocker Version: GNOME2.8.1 2.0.2 Gnome-Distributor: Debian Synopsis: Evolution "unexpectedly exits" upon being launched Bugzilla-Product: Evolution Bugzilla-Component: Shell Bugzilla-Version: 2.0.2 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Evolution exists imediately upon being started. The main window displays, followed by an error message stating that the program has unexpectedly quit. Evolution appears to still work as long as I don't click on any button in the error dialog, but if I do, Evolution quits. Steps to reproduce the crash: 1. start Evolution 2. 3. Expected Results: The program runs How often does this happen? Every time this morning. Additional Information: It worked fine Wednesday 2004-12-22. I came in to work today, and it doesn't work anymore. I've updated against my Debian mirror, logged out, and killed all processes belonging to this user before logging back in. No luck, same behavior. Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/tls/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) [Thread debugging using libthread_db enabled] [New Thread -1226133376 (LWP 15099)] [New Thread -1268274256 (LWP 15130)] [New Thread -1259885648 (LWP 15129)] [New Thread -1242563664 (LWP 15110)] [New Thread -1250952272 (LWP 15109)] [New Thread -1233028176 (LWP 15107)] (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) 0xb705afe3 in poll () from /lib/tls/libc.so.6
+ Trace 53899
Thread 4 (Thread -1242563664 (LWP 15110))
Unknown reporter: adingman@cook-inc.com, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Slightly more detail. As long as I ignore the error dialog, things *almost* work, but as far as I can tell it won't expunge deleted messages from my mailboxes, nor does it seem to carry over any changed information other than new messages between invocations of Evolution. No matter how many times I read, delete, and move messages, every time I start Evolution again all messages retrieved since the problem started are still new and unread in my inbox. For what it is worth, I also use much the same set of software at home, and have had no problems with Evolution there. The only difference in Evolution itself is that here I have the Exchange plugin installed, and at home I do not. I just uninstalled that, and I'm still experiencing the same problem. This bug is also actually a 2.0.3 issue, not 2.0.2, but Bug Buddy wouldn't let me pick 2.0.3 when I submitted the bug yesterday.
Are you using the same distro and packages in both places?
search for and remove the *.ibex.* files in your evolution mail directories. looks just like a busted index.
Yes, same distro and package in both places. I couldn't live w/o my e-mail working right this long, so I've already blown away my config and then re-imported all the mbox files, which worked even though it is quite crude. The index suggestion sounds reasonable, though.
marking as a duplicate of an existing bug, not quite the same bug but probably the same reason, corrupt files *** This bug has been marked as a duplicate of 236778 ***