GNOME Bugzilla – Bug 399537
Calendar randomly crashes
Last modified: 2007-06-17 21:19:45 UTC
Steps to reproduce: 1. Unfortunately I can only reproduce it by leaving Evolution running and waiting for the calendar to die, which happens about once a day while I'm not even actively using Evolution. Stack trace: Here is the report generated by bug-buddy, which for some reason thinks that Evolution is not tracked in GNOME's bugzilla. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- (evolution:5534): GLib-GObject-WARNING **: IA__g_object_set_valist: property `width' of object class `GtkTreeViewColumn' is not writable (evolution:5534): libglade-WARNING **: unknown property `ellipsize' for class `GtkImage' (evolution:5534): libglade-WARNING **: unknown property `width_chars' for class `GtkImage' (evolution:5534): libglade-WARNING **: unknown property `single_line_mode' for class `GtkImage' (evolution:5534): libglade-WARNING **: unknown property `angle' for class `GtkImage' Playing WAVE '/home/drfickle/src/st-perl/sounds/received.wav' : Unsigned 8 bit, Rate 8012 Hz, Mono Playing WAVE '/home/drfickle/src/st-perl/sounds/received.wav' : Unsigned 8 bit, Rate 8012 Hz, Mono ** (bug-buddy:22914): WARNING **: Couldn't load icon for Encryption Preferences ** (bug-buddy:22914): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 282603520 vsize: 0 resident: 282603520 share: 0 rss: 90460160 rss_rlim: 0 CPU usage: start_time: 1169223318 rtime: 0 utime: 23529 stime: 0 cutime:20487 cstime: 0 timeout: 3042 it_real_value: 0 frequency: 3 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209014048 (LWP 5534)] [New Thread -1292231792 (LWP 5564)] [New Thread -1307575408 (LWP 5562)] [New Thread -1261446256 (LWP 5559)] [New Thread -1274020976 (LWP 5558)] [New Thread -1250956400 (LWP 5556)] [New Thread -1240466544 (LWP 5555)] [New Thread -1228272752 (LWP 5554)] [New Thread -1217782896 (LWP 5552)] 0x00be9402 in __kernel_vsyscall ()
+ Trace 104392
Thread 1 (Thread -1209014048 (LWP 5534))
Other information: I have installed just about every relevant debuginfo package I can think of to generate a usable stack trace. Please let me know if I missed anything.
Here's a similar or identical backtrace I got. I believe I was looking at a memo instead though. The crash was either after closing a memo dialog or slightly after that during scrolling or component changing. (Nothing relevant in .xsession-errors, just "checking for junk..?" spam from before [why does that spam into xsession-errors anyway?]) Distribution: Gentoo Base System version 1.12.9 Gnome Release: 2.16.2 2006-12-20 (Gentoo) BugBuddy Version: 2.16.0 Memory status: size: 300621824 vsize: 0 resident: 300621824 share: 0 rss: 162680832 rss_rlim: 0 CPU usage: start_time: 1169749319 rtime: 0 utime: 183215 stime: 0 cutime:151629 cstime: 0 timeout: 31586 it_real_value: 0 frequency: 1040 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1231305024 (LWP 18764)] [New Thread -1330644080 (LWP 31498)] [New Thread -1304978544 (LWP 23596)] [New Thread -1295815792 (LWP 18775)] [New Thread -1274369136 (LWP 18774)] [New Thread -1264624752 (LWP 18772)] [New Thread -1255838832 (LWP 18771)] [New Thread -1247446128 (LWP 18769)] 0xb7f58410 in __kernel_vsyscall ()
+ Trace 105481
Thread 1 (Thread -1231305024 (LWP 18764))
*** Bug 420876 has been marked as a duplicate of this bug. ***
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 has been marked as a duplicate of 224322 ***