GNOME Bugzilla – Bug 307775
evolution-alarm-notify keeps crashing
Last modified: 2006-02-15 22:10:30 UTC
Distribution: Fedora Core release 4 (Stentz) Package: Evolution Priority: Major Version: GNOME2.10.0 2.2.2 Gnome-Distributor: Red Hat, Inc Synopsis: evolution-alarm-notify keeps crashing Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Bugzilla-Version: 2.2.2 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: When I launch evolution, a few minutes later, the evolution-alarm-notify crashes. I can't figure out if something in particular is causing the crash. I have an Exchange server configured, but currently disabled. I'll try running from the command line and see if it keeps happening. Steps to reproduce the crash: 1. Launch evolution. 2. 3. Expected Results: evolution-alarm-notify does not crash :) How often does this happen? Every time since upgrading to Evo 2.2 (FC4), which is about 3-4 times now. Additional Information: Debugging Information: Backtrace was generated from '/usr/libexec/evolution-alarm-notify' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208953152 (LWP 5520)] [New Thread -1211077712 (LWP 5522)] 0x007b0402 in ?? ()
+ Trace 61046
Thread 1 (Thread -1208953152 (LWP 5520))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-15 14:19 UTC ------- Unknown version 2.2.2 in product Evolution. Setting version to "2.2.x".
Running from command line shows alarm-notify trying to resolve my exchange account's calendar. I tried deleting the Exchange server account entirely, and this did seem to do the trick (so far). However, I would expect if an account is disabled, that the alarm-notify program would not try to resolve items under it (such as calendar, etc.).
I take it back... it's crashed again even without the exchange account, but it is still trying to load old exchange items, though that doesn't always cause a crash running from terminal with E2KDEBUG=3).
Prothonotar: Looks similar to Bug 272835 ? Can you check with latest Evolution once ?
Nagappan: It looks like bug 272835 was fixed in 2.2.1, but I'm running version 2.2.2, so it's either a different bug, or 272835 is not fixed. The stack trace also looks a little different.
reopening as per last comment
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. FYI: This bug definitely was valid in Evo 2.2.2 (see bug 273714 comment 12 for example) and has been fixed about half a year ago. Identical stacktrace as bug 315809, duplicate of bug 273714. *** This bug has been marked as a duplicate of 273714 ***