GNOME Bugzilla – Bug 490345
crash in Project Management: double clicking on a tas...
Last modified: 2007-10-29 23:00:46 UTC
Version: 0.14.2 What were you doing when the application crashed? double clicking on a task in Planner to edit duration. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 70967296 vsize: 70967296 resident: 31174656 share: 19546112 rss: 31174656 rss_rlim: 4294967295 CPU usage: start_time: 1193357643 rtime: 16076 utime: 13542 stime: 2534 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/planner' (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 -1209063184 (LWP 6168)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 172909
Thread 1 (Thread -1209063184 (LWP 6168))
----------- .xsession-errors (348 sec old) --------------------- ** (gnome-help:6373): WARNING **: failure: no device event controller found. ** (gnome-help:6373): WARNING **: failure: no device event controller found. (gnome-help:6373): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed ** (planner:6168): WARNING **: IPP request failed with status 1030 ** (planner:6168): WARNING **: IPP request failed with status 1030 Unmatched element: biblioentry (gnome-help:6700): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed Unmatched element: biblioentry --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 372694 ***