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 360908 - crash in Project Management: I had just opened a Plan...
crash in Project Management: I had just opened a Plan...
Status: RESOLVED DUPLICATE of bug 347555
Product: planner
Classification: Other
Component: General
0.14
Other All
: High critical
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2006-10-09 14:06 UTC by mdpoole
Modified: 2006-10-09 19:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description mdpoole 2006-10-09 14:06:29 UTC 
What were you doing when the application crashed?
I had just opened a Planner schedule created on an up-to-date Dapper install.  As the backtrace suggests, it was trying to display the Gantt chart (as the first view).  If it will help, I can try to sanitize the file (to remove proprietary information) and see if the problem recurs.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 42065920 vsize: 0 resident: 42065920 share: 0 rss: 18796544 rss_rlim: 0
CPU usage: start_time: 1160402436 rtime: 0 utime: 296 stime: 0 cutime:288 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

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)
[Thread debugging using libthread_db enabled]
[New Thread -1225844544 (LWP 15808)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 75430

Thread 1 (Thread -1225844544 (LWP 15808))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 planner_gantt_row_get_geometry
  • #5 planner_gantt_row_get_geometry
  • #6 gnome_canvas_root
    from /usr/lib/libgnomecanvas-2.so.0
  • #7 gnome_canvas_item_new
    from /usr/lib/libgnomecanvas-2.so.0
  • #8 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #9 g_type_class_meta_marshal
    at gclosure.c line 567
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #13 IA__g_signal_emit
    at gsignal.c line 2243
  • #14 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #15 IA__gtk_main_do_event
    at gtkmain.c line 1407
  • #16 gdk_window_process_updates_internal
    at gdkwindow.c line 2324
  • #17 IA__gdk_window_process_all_updates
    at gdkwindow.c line 2387
  • #18 gdk_window_update_idle
    at gdkwindow.c line 2245
  • #19 g_idle_dispatch
    at gmain.c line 3926
  • #20 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #21 g_main_context_iterate
    at gmain.c line 2677
  • #22 IA__g_main_loop_run
    at gmain.c line 2881
  • #23 IA__gtk_main
    at gtkmain.c line 1024
  • #24 main
  • #0 __kernel_vsyscall 






Comment 1


mdpoole





          2006-10-09 19:13:18 UTC
        



Updating to 0.14.1 fixes this, at least for now.  If I can still reproduce the problem (as reported in #358415), I will follow up there.

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