GNOME Bugzilla – Bug 462144
crash in Project Management: Importing MS Project XML...
Last modified: 2007-09-11 19:22:27 UTC
Version: 0.14.2 What were you doing when the application crashed? Importing MS Project XML output by MS Project 2003 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.1-33.fc7 #1 SMP Mon Jul 23 17:33:07 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Bluecurve Memory status: size: 109285376 vsize: 109285376 resident: 47198208 share: 34783232 rss: 47198208 rss_rlim: 4294967295 CPU usage: start_time: 1185891803 rtime: 636 utime: 628 stime: 8 cutime:0 cstime: 0 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 -1208514848 (LWP 1137)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 151820
Thread 1 (Thread -1208514848 (LWP 1137))
----------- .xsession-errors --------------------- haldaemon hald (pid 2621) is running... haldaemon hald (pid 2621) is running... haldaemon hald (pid 708) is running... kbuildsycoca running... Reusing existing ksycoca Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000058 (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000058 (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** ERROR **: file mrp-old-xml.c: line 1449 (old_xml_process_delayed_relations): assertion failed: (predecessor_task != NULL) aborting... --------------------------------------------------
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 373008 ***