GNOME Bugzilla – Bug 332693
Evolution crash on starting calendar
Last modified: 2006-07-11 00:15:13 UTC
Distribution: Debian testing/unstable Package: Evolution Severity: blocker Version: GNOME2.12.2 2.4.x Gnome-Distributor: Debian Synopsis: Evolution crash on starting calendar Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.12.1) Description: Description of the crash: Evolution segfaults when I try to run the calendar Steps to reproduce the crash: 1. Start evolution 2. Click on 'Calendars' 3. Boom! Expected Results: Calendar should start How often does this happen? Every time Additional Information: Deleteing all files under /home/rob/.evolution/calendar/ has no effect Deleting gconf node has no effect (including restartin gconfd) Can sometimes view forward a few days, but attempts to go back or view Todays or Tomorrows events cause the crash Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1230804768 (LWP 19560)] [New Thread -1313866832 (LWP 19585)] [New Thread -1286603856 (LWP 19580)] [New Thread -1295520848 (LWP 19573)] [New Thread -1274020944 (LWP 19570)] [New Thread -1264546896 (LWP 19569)] [New Thread -1255146576 (LWP 19567)] [New Thread -1244394576 (LWP 19566)] [New Thread -1235612752 (LWP 19564)] (no debugging symbols found) 0xb74d8231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 66542
Thread 1 (Thread -1230804768 (LWP 19560))
------- Bug created by bug-buddy at 2006-02-27 01:11 -------
What is the timezone being used ?
Time zone: Australia/Sydney Problem now only occurs when I go back to the days in question (Monday & Tuesday of the week before last). This means that the bug is likely being triggered by bad events for one of those days - where can I get this to provide it?
If debug rpms of evolution is installed and then try out this scenario you can make out if any events is causing this crash. Update this bug with those stack traces
Poornima: Not this way.
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. This bug is fixed in Evolution 2.6. *** This bug has been marked as a duplicate of 329866 ***