GNOME Bugzilla – Bug 311425
evolution alarm notifier crashes each time on evolution start up
Last modified: 2005-07-24 18:23:49 UTC
Distribution: Debian 3.1 (Ubuntu Hoary) Package: Evolution Severity: major Version: GNOME2.10.0 2.2.x Gnome-Distributor: Ubuntu Synopsis: evolution alarm notifier crashes each time on evolution start up Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Bugzilla-Version: 2.2.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: evolution alarm notifier crashes each time on evolution start up Steps to reproduce the crash: 1. restart x (not sure is always necessary 2. start evolution 3. Expected Results: get notification that evolution-alarm-notify crashes How often does this happen? each time i start evolution Additional Information: running Ubuntu Hoary Debugging Information: Backtrace was generated from '/usr/libexec/evolution-alarm-notify' Using host libthread_db library "/lib/tls/i686/cmov/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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 1094115712 (LWP 5693)] [New Thread 1104133040 (LWP 5694)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in ?? ()
+ Trace 61969
Thread 2 (Thread 1104133040 (LWP 5694))
------- Bug moved to this database by unknown@gnome.bugs 2005-07-24 17:24 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was serge@vanginderachter.be.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report? *** This bug has been marked as a duplicate of 273714 ***