GNOME Bugzilla – Bug 273714
Crash: Evolution alarm notify popped up with a message it had ended unexpectedly, a couple of seconds after opening my mailbox.
Last modified: 2013-09-10 13:52:05 UTC
Distribution: Debian 3.1 Package: Evolution Priority: Normal Version: GNOME2.10.0 2.2.0 Gnome-Distributor: Ubuntu Synopsis: Evolution alarm notify popped up with a message it had ended unexpectedly, a couple of seconds after opening my mailbox. Bugzilla-Product: Evolution Bugzilla-Component: Tasks Bugzilla-Version: 2.2.0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: 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 1093992832 (LWP 5766)] [New Thread 1102556080 (LWP 5768)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 56901
Thread 2 (Thread 1102556080 (LWP 5768))
Unknown reporter: m.hirschfeld@nl.tiscali.com, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Can you please give us the steps to reproduce the bug, and tell us how often it happens.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
*** Bug 273236 has been marked as a duplicate of this bug. ***
*** Bug 274444 has been marked as a duplicate of this bug. ***
*** Bug 274344 has been marked as a duplicate of this bug. ***
*** Bug 274281 has been marked as a duplicate of this bug. ***
*** Bug 273782 has been marked as a duplicate of this bug. ***
*** Bug 273618 has been marked as a duplicate of this bug. ***
*** Bug 301606 has been marked as a duplicate of this bug. ***
*** Bug 301990 has been marked as a duplicate of this bug. ***
This happens to me as well every time that evolution starts
This also happens to me. Evolution 2.2.2-3 on Fedora Core 4 test 2 with latest updates.
*** Bug 309985 has been marked as a duplicate of this bug. ***
*** Bug 308814 has been marked as a duplicate of this bug. ***
*** Bug 311259 has been marked as a duplicate of this bug. ***
I think this was closed by mistake. It's still being reported from recent versions of Evolution. Could someone please provide a stack trace with debugging symbols? See http://live.gnome.org/GettingTraces for more information on how to do so.
*** Bug 311425 has been marked as a duplicate of this bug. ***
*** Bug 311836 has been marked as a duplicate of this bug. ***
*** Bug 311963 has been marked as a duplicate of this bug. ***
(gdb) thread apply all bt
+ Trace 62088
Thread 1 (Thread -151217696 (LWP 10443))
*** Bug 312565 has been marked as a duplicate of this bug. ***
I've seen this several times too. Just got the same crash now with 2.2.2 on a (pretty) clean install of Fedora Core 4. I may be able to provide debugging assistance if needed. LMK.
I get this error, I can't open evolution at all now.
If I run evolution as root, it gives me a crash message/warning message on close of the application, but I can't even open the application as non-root user without the crash message/warning message.
Nope, nevermind. Now that doesn't even work.
This has been fixed.
chenthill: can you point me to the fix?
*** Bug 315809 has been marked as a duplicate of this bug. ***
*** Bug 329312 has been marked as a duplicate of this bug. ***
*** Bug 307775 has been marked as a duplicate of this bug. ***