GNOME Bugzilla – Bug 254730
Crash: Fatal Error
Last modified: 2009-08-15 18:40:50 UTC
Package: Evolution Priority: Normal Version: 1.4.5 Synopsis: Fatal Error Bugzilla-Product: Evolution Bugzilla-Component: Mailer BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Just clicked on a new email and it crashed Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 1093436832 (LWP 13711)] [New Thread 1158921008 (LWP 13768)] [New Thread 1150528304 (LWP 13733)] [New Thread 1142135600 (LWP 13723)] [New Thread 1133742896 (LWP 13720)] [New Thread 1125350192 (LWP 13719)] [New Thread 1116957488 (LWP 13718)] 0xffffe002 in ?? ()
+ Trace 44475
Thread 1 (Thread 1093436832 (LWP 13711))
Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
I'm afraid that I couldn't provide too much specific information about this. I get fairly frequent crashes of the Evolution Mail component. I recently upgraded from the version which came with the RH 9 distro (with Redhat patches applied) to 1.4.5 partly in hopes that these crashes would become less frequent. I'd tried to report this with the earlier version, but it had a bad bug reporting e-mail address. I haven't been able to figure out a pattern to when the crash occurs, it usually happens when I select an email, but sometimes Evolution mail will just crash when Evolution is running in the background and I'm working with another application.
Although Bug buddy tagged this as Evo 1.4.5, I'm actually running 1.5.5
if you really run evo 1.5.5 you definitelly need gtkhtml 3.1
Whoops, I added the last comment to the wrong bug. This was indeed happening with 1.4.5
Unfortunately, through no fault of your own, this trace is pretty useless since it has no debugging symbols. If you can reproduce this crash with a specific set of actions using an unstripped Evolution 1.4.6 version, please let us know with a new report. Thanks!