GNOME Bugzilla – Bug 468999
crash in Evolution: GNOME was logging in & r...
Last modified: 2007-11-15 14:55:36 UTC
What were you doing when the application crashed? GNOME was logging in & restoring my session Distribution: Unknown Gnome Release: 2.18.3 2007-07-07 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.22-ARCH #1 SMP PREEMPT Wed Aug 15 23:33:00 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: OSX Memory status: size: 71090176 vsize: 71090176 resident: 7430144 share: 5877760 rss: 7430144 rss_rlim: 4294967295 CPU usage: start_time: 1187730769 rtime: 7 utime: 6 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/evolution-data-server-1.10' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1222674752 (LWP 5132)] [New Thread -1252246640 (LWP 5152)] [New Thread -1225557104 (LWP 5137)] 0xb7fac410 in __kernel_vsyscall ()
+ Trace 156957
Thread 1 (Thread -1222674752 (LWP 5132))
----------- .xsession-errors (1024879 sec old) --------------------- (linuxdcpp:6605): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (linuxdcpp:6605): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer (linuxdcpp:6605): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (linuxdcpp:6605): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer (linuxdcpp:6605): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (linuxdcpp:6605): libgnomevfs-WARNING **: Failed to re-activate daemon: Connection is closed ** (evolution-2.10:6620): WARNING **: could not get system bus: Failed to connect to socket /tmp/dbus-xxSZNlmuGX: Connection refused --------------------------------------------------
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 426237 ***