GNOME Bugzilla – Bug 597499
crash in Evolution: I was running evolution ...
Last modified: 2009-10-06 04:05:08 UTC
Version: 2.30.x What were you doing when the application crashed? I was running evolution remotely. Had switched to calendar and clicked (several times rapidly) on a blank spot on the calendar in order to create a new appointment. Distribution: Slackware Slackware 12.2.0 Gnome Release: 2.28.0 2009-09-21 (GARNOME) BugBuddy Version: 2.28.0 System: Linux 2.6.31.1 #44 SMP PREEMPT Tue Sep 29 12:17:33 EDT 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad Memory status: size: 236232704 vsize: 236232704 resident: 77803520 share: 28581888 rss: 77803520 rss_rlim: 18446744073709551615 CPU usage: start_time: 1254793622 rtime: 5628 utime: 5166 stime: 462 cutime:67 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/garnome-svn-2.28/bin/evolution' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb5f31710 (LWP 10611)] [New Thread 0xaf764b90 (LWP 10638)] [New Thread 0xaffd3b90 (LWP 10637)] [New Thread 0xb1283b90 (LWP 10627)] [New Thread 0xb1a83b90 (LWP 10626)] [New Thread 0xb2e1bb90 (LWP 10625)] [New Thread 0xb361bb90 (LWP 10624)] 0xb61f5171 in waitpid () from /lib/libpthread.so.0
+ Trace 218082
Thread 1 (Thread 0xb5f31710 (LWP 10611))
---- Critical and fatal warnings logged during execution ---- ** e-utils **: Plugin "Exchange Operations" is missing a function named eex_ui_mail_init() ** e-activity.c **: e_activity_set_percent: assertion `E_IS_ACTIVITY (activity)' failed ** Gdk **: gdk_drawable_get_colormap: assertion `GDK_IS_DRAWABLE (drawable)' failed ** Gdk **: gdk_window_set_background: assertion `GDK_IS_WINDOW (window)' failed ** evolution **: Out of memory
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 bug 596822 ***