GNOME Bugzilla – Bug 329312
e-a-n crash (was: Choosing Preferences Crashes Evolution)
Last modified: 2006-02-15 21:55:47 UTC
1. Build Evolution from CVS (via jhbuild) 2. Start Evolution. 3. Choose Edit->Preferences 4. Watch Evolution crash, every time. I sent a report via bug-buddy, but it does not appear to have got through.
Debugging Information: Backtrace was generated from '/usr/libexec/evolution-alarm-notify' (no debugging symbols found) Using host libthread_db library "/lib/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) [Thread debugging using libthread_db enabled] [New Thread -1209108000 (LWP 4457)] [New Thread -1211503696 (LWP 4504)] [New Thread -1211237456 (LWP 4458)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00fa4402 in ?? ()
+ Trace 65775
Thread 1 (Thread -1209108000 (LWP 4457))
Now this is a strange one... John, your description does not match the crash in comment 1. The stacktrace was generated from evolution-alarm-notify, and actually appears to be a duplicate of an old Evo 2.2.x crasher (same stacktrace as bug 315809). According to the stacktrace, I will mark this bug as a duplicate for now, adjusting Version, Component and Summary. If you get the correct stacktrace, please feel free to either re-open this bug with the stacktrace, or file a new one. Given the potential confusion with the stacktrace in comment 1 I'd prefer if you could file a new report. Thanks for taking the time to report this issue. *** This bug has been marked as a duplicate of 273714 ***