GNOME Bugzilla – Bug 454184
crash in Tasks: Start up from standby mo...
Last modified: 2007-07-06 14:45:35 UTC
Version: 2.10 What were you doing when the application crashed? Start up from standby mode. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 163733504 vsize: 163733504 resident: 35721216 share: 21438464 rss: 35721216 rss_rlim: 4294967295 CPU usage: start_time: 1183682459 rtime: 12026 utime: 10979 stime: 1047 cutime:2566 cstime: 236 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208912160 (LWP 5653)] [New Thread -1341150320 (LWP 11735)] [New Thread -1330660464 (LWP 11733)] [New Thread -1265173616 (LWP 5713)] [New Thread -1286153328 (LWP 5710)] [New Thread -1221776496 (LWP 5676)] (no debugging symbols found) 0x00dd6402 in __kernel_vsyscall ()
+ Trace 146058
Thread 1 (Thread -1208912160 (LWP 5653))
----------- .xsession-errors (70 sec old) --------------------- (evolution:5653): libebook-CRITICAL **: file e-book.c: line 3807: assertion `source && E_IS_SOURCE (source)' failed (evolution:5653): libebook-CRITICAL **: e_book_get_source: assertion `book && E_IS_BOOK (book)' failed (evolution:5653): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (evolution:5653): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (evolution:5653): libebook-CRITICAL **: e_book_async_open: assertion `book && E_IS_BOOK (book)' failed Loading "installonlyn" plugin kbuildsycoca running... Reusing existing ksycoca ** (gnome-panel:2586): WARNING **: Could not ask power manager to hibernate: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security pol --------------------------------------------------
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 426807 ***