GNOME Bugzilla – Bug 631342
crash in Evolution: Looking at various calen...
Last modified: 2013-09-13 01:10:59 UTC
Version: 2.92.x What were you doing when the application crashed? Looking at various calendar entries. I'd just clicked on the October 6 date. I see: evolution:24444): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** Gdk:ERROR:gdkregion-generic.c:1110:miUnionNonO: assertion failed: (y1 < y2) ** (bug-buddy:24648): WARNING **: Couldn't load /usr/share/applications/openoffice.org3-startcenter.desktop: No such file or directory On the console, however, I suspect that this was all before the crash. Distribution: Slackware Slackware 12.2.0 Gnome Release: 2.32.0 2010-09-27 (GARNOME) BugBuddy Version: 2.32.0 System: Linux 2.6.34-rc5-ge520683 #2 SMP PREEMPT Tue Jun 8 13:13:01 EDT 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10900000 Selinux: No Accessibility: Disabled GTK+ Theme: Default Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomesegvhandler Memory status: size: 261541888 vsize: 261541888 resident: 62271488 share: 27934720 rss: 62271488 rss_rlim: 18446744073709551615 CPU usage: start_time: 1286218657 rtime: 4978 utime: 4728 stime: 250 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/garnome-svn-2.31.92/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xa8fffb90 (LWP 24643)] [New Thread 0xac7ffb90 (LWP 24454)] [New Thread 0xacfffb90 (LWP 24453)] [New Thread 0xae24fb90 (LWP 24451)] [New Thread 0xaea4fb90 (LWP 24450)] [New Thread 0xb5b02b90 (LWP 24445)] 0xb5d3e01d in poll () from /lib/libc.so.6
+ Trace 224004
Thread 2 (Thread 0xa8fffb90 (LWP 24643))
Inferior 1 [process 24444] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
There seems to be some interaction between this bug and Bug 631341
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 626641 ***