After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 345545 - Planner crashes when opening XML from MS_Project.
Planner crashes when opening XML from MS_Project.
Status: RESOLVED DUPLICATE of bug 373008
Product: planner
Classification: Other
Component: General
0.13
Other All
: Normal critical
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2006-06-21 14:12 UTC by Fabiano Sanches
Modified: 2007-02-10 14:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Fabiano Sanches 2006-06-21 14:12:45 UTC 
Steps to reproduce:
1. Click on FILE menu
2. Import/XML From MS-Project
3. choose file

Expected Results:
File opened.

How often does this happen?
always.

Stack trace:
Backtrace was generated from '/usr/bin/planner'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224612160 (LWP 4944)]
[New Thread -1269875792 (LWP 4950)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 68976

Thread 1 (Thread -1224612160 (LWP 4944))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 mrp_old_xml_parse
    from /usr/lib/planner/file-modules/libmrp-xml.so
  • #11 ??
    from /usr/lib/planner/file-modules/libmrp-xml.so
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 _dl_rtld_di_serinfo
    from /lib/ld-linux.so.2
  • #16 mrp_file_reader_read_string
    from /usr/lib/libplanner-1.so.0
  • #17 mrp_project_load
    from /usr/lib/libplanner-1.so.0
  • #18 planner_window_open
  • #19 planner_window_open_in_existing_or_new
  • #20 ??
    from /usr/lib/planner/plugins/libmsp-plugin.so
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
    from /usr/lib/planner/plugins/libmsp-plugin.so
  • #25 ??
  • #26 ??
    from /usr/lib/planner/plugins/libmsp-plugin.so
  • #27 ??
  • #28 ??
  • #0 __kernel_vsyscall 

Other information:
Comment 1 Kurt Maute 2006-12-15 03:33:50 UTC 
Could you please provide an example of the MS xml file ?
I don't have a problem importing with the example files that I have.
tnx
Comment 2 André Klapper 2007-02-10 14:32:13 UTC 
bug 373008 provides a better stacktrace.

*** This bug has been marked as a duplicate of 373008 ***