GNOME Bugzilla – Bug 473929
crash in Project Management: editing tasks
Last modified: 2007-09-11 19:19:07 UTC
Version: 0.14.2 What were you doing when the application crashed? editing tasks Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2962.fc6 #1 SMP Tue Jun 19 19:27:14 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Disabled Memory status: size: 70418432 vsize: 0 resident: 70418432 share: 0 rss: 23175168 rss_rlim: 0 CPU usage: start_time: 1189000038 rtime: 0 utime: 3968 stime: 0 cutime:3777 cstime: 0 timeout: 191 it_real_value: 0 frequency: 0 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 -1208420656 (LWP 26441)] (no debugging symbols found) 0x0059d402 in __kernel_vsyscall ()
+ Trace 160650
Thread 1 (Thread -1208420656 (LWP 26441))
----------- .xsession-errors (196481 sec old) --------------------- Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp Window manager warning: last_focus_time (1) is greater than comparison timestamp (3394690189). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp Window manager warning: last_focus_time (1) is greater than comparison timestamp (3394743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp Window manager warning: last_focus_time (1) is greater than comparison timestamp (3394850492). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp Window manager warning: last_focus_time (1) is greater than comparison timestamp (3394901390). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp Window manager warning: last_focus_time (1) is greater than comparison timestamp (3394907292). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a007ec (Find & Rep) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp ...Too much output, ignoring rest... --------------------------------------------------
I think I could identify the exact crash situation: when trying to add a predecessor to a task without work hours assigned and without milestone or duration ticked, the planner crashed.
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 372694 ***