GNOME Bugzilla – Bug 618808
crash in Evolution: No user interaction at a...
Last modified: 2010-05-16 20:52:34 UTC
What were you doing when the application crashed? No user interaction at all, nothing in the evolution status pane (checking email, etc...) so I don't know what was happening behind the scenes. This is on a SLED 11 SP1 RC4 system (x86_64). Distribution: SUSE Linux Enterprise Desktop 11 (x86_64) Gnome Release: 2.28.2 (null) (SUSE) BugBuddy Version: 2.28.0 System: Linux 2.6.32.12-0.3-default #1 SMP 2010-04-28 13:17:26 +0200 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Gilouche GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 1376821248 vsize: 1376821248 resident: 484614144 share: 32899072 rss: 484614144 rss_rlim: 18446744073709551615 CPU usage: start_time: 1273838979 rtime: 33746 utime: 29836 stime: 3910 cutime:16 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution.bin' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0x7fd8fb9fe710 (LWP 17354)] [New Thread 0x7fd901df9710 (LWP 15361)] [New Thread 0x7fd907d36710 (LWP 3441)] [New Thread 0x7fd906374710 (LWP 1481)] [New Thread 0x7fd908c1a710 (LWP 1461)] [New Thread 0x7fd90941b710 (LWP 1460)] [New Thread 0x7fd90ffff710 (LWP 1458)] [New Thread 0x7fd90a41d710 (LWP 1455)] [New Thread 0x7fd914d20710 (LWP 1452)] [New Thread 0x7fd915521710 (LWP 1451)] [New Thread 0x7fd915d22710 (LWP 1450)] [New Thread 0x7fd916730710 (LWP 1449)] [New Thread 0x7fd918b7c710 (LWP 1446)] [New Thread 0x7fd91837b710 (LWP 1445)] 0x00007fd92dcd213f in __libc_waitpid (pid=17529, stat_loc=0x7fff01ec0b20, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 221936
Thread 1 (Thread 0x7fd932663800 (LWP 1434))
Inferior 1 [process 1434] 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_ref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_ref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_ref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_notify: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed ** Gtk **: gtk_widget_get_screen: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed ** Gtk **: gtk_icon_theme_get_icon_sizes: assertion `GTK_IS_ICON_THEME (icon_theme)' failed ----------- .xsession-errors (2089 sec old) --------------------- Got Event! 22, -1 Got Event! 100, -1 Got Event! 101, -1 Got Event! 22, -1 Got Event! 100, -1 Got Event! 22, -1 e-data-server-ui-Message: Received a password from keyring 'login'. But looking for the password from 'default' keyring e-data-server-ui-Message: Received a password from keyring 'login'. But looking for the password from 'default' keyring (gnome-panel:13586): libecal-WARNING **: e-cal.c:317: Unexpected response e-data-server-ui-Message: Received a password from keyring 'login'. But looking for the password from 'default' keyring ** (gnome-panel:13586): DEBUG: helper refused; returned polkit_result='auth_admin_keep_always <-- (action, result)' and polkit_action='org.gnome.clockapplet.mechanism.settime' --------------------------------------------------
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 586972 ***