GNOME Bugzilla – Bug 323613
Crash on calendar activation
Last modified: 2005-12-20 18:33:52 UTC
Distribution: Unknown Package: Evolution Severity: Normal Version: GNOME2.13.2 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Crash on calendar activation Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Evolution will crash (quit unexpectedly) when changing "window" to the calendar Steps to reproduce the crash: 1. Start evolution 2. Click "calendars" Expected Results: The calendars should show up How often does this happen? Every time Additional Information: I have the same problem with both evolution-2.4.2-2 from Fedora Devel, and evolution-2.5.2-1. I tried removing ~/.evolution/calendar with no luck. The main problem with this is that when evo starts up again, it will go directly to calendar mode, and then crash - again and again, until I am quick enough to press one of the other buttons to select another module (mail works fine). Maybe evolution should have some sort of a "failsafe" state that it will start after a crash, so it is easier to debug. An strace of the crash can be added to this bug if neccesary. Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/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) [Thread debugging using libthread_db enabled] [New Thread 46912506286368 (LWP 29114)] [New Thread 1094986080 (LWP 29131)] [New Thread 1094719840 (LWP 29130)] [New Thread 1084229984 (LWP 29129)] (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) (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) 0x0000003267e0c139 in waitpid () from /lib64/libpthread.so.0
+ Trace 64501
Thread 1 (Thread 46912506286368 (LWP 29114))
------- Bug moved to this database by unknown@gnome.bugs 2005-12-09 08:10 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 redhat@olen.net.
you can start in a different view by running "evolution -c mail" for example so evolution is working again. stacktrace very similar to bug 323616 and bug 323157.
adding dep
*** This bug has been marked as a duplicate of 323616 ***