GNOME Bugzilla – Bug 253778
Evolution crashes often, for no reason I can discern.
Last modified: 2004-02-04 03:55:37 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: Evolution Priority: Major Version: GNOME2.4.0 unspecified Gnome-Distributor: GNOME.Org Synopsis: Evolution crashes often, for no reason I can discern. Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: During normal use of Evolution Mail, it will often crash. At the point it does, I'm reading emails, dragging them to folders and deleting them. Nothing fancy really. The crashes are not repeatable, in that it is not a specific action that causes it. I can restart, continue with what I was doing and it works fine, for another hour or two. How often does this happen? I crash 2-3 times a day; I do spend most of my day using Evolution so I am a heavy user. Additional Information: I am running version 1.4.5 which is not listed in the Bug Buddy drop-down version list. I am running strictly a stable release of Fedora Core 1, no test versions here. I am running Evolution Mail in Local Delivery mode, with some of the larger folders set to Maildir format and the rest in the default mbox format. I'm hoping the attach crash log will show something meaningful or that it is a bug you've seen before. I know these are the hard kind of bugs to track down, but perhaps if you get enough reports a pattern will emerge. 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)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (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 -1084545056 (LWP 30949)] [New Thread -1149965392 (LWP 31325)] [New Thread -1131680848 (LWP 30965)] [New Thread -1120928848 (LWP 30964)] [New Thread -1108759632 (LWP 30952)] [New Thread -1098269776 (LWP 30951)] [New Thread -1087779920 (LWP 30950)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x00323c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 43752
Thread 1 (Thread -1084545056 (LWP 30949))
Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
This is a known problem that is being worked on. As a workaround turn off gnome accessibility. *** This bug has been marked as a duplicate of 242867 ***