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 440520 - crash in Project Management: ineractuando con el diag...
crash in Project Management: ineractuando con el diag...
Status: RESOLVED DUPLICATE of bug 372694
Product: planner
Classification: Other
Component: General
0.14.x
Other All
: High critical
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2007-05-22 18:17 UTC by jmoyano
Modified: 2007-06-29 00:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description jmoyano 2007-05-22 18:17:03 UTC
Version: 0.14.1

What were you doing when the application crashed?
ineractuando con el diagrama de gantt


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

Memory status: size: 36737024 vsize: 0 resident: 36737024 share: 0 rss: 18530304 rss_rlim: 0
CPU usage: start_time: 1179856828 rtime: 0 utime: 6477 stime: 0 cutime:6068 cstime: 0 timeout: 409 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 -1225787728 (LWP 6202)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225787728 (LWP 6202))

  • #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 mrp_task_manager_calculate_task_work
    from /usr/lib/libplanner-1.so.0
  • #5 mrp_task_manager_recalc
    from /usr/lib/libplanner-1.so.0
  • #6 mrp_task_manager_recalc
    from /usr/lib/libplanner-1.so.0
  • #7 g_cclosure_marshal_VOID__PARAM
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_class_override_property
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_enum_register_static
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_object_set_property
    from /usr/lib/libgobject-2.0.so.0
  • #15 planner_task_tree_select_all
  • #16 planner_cmd_new_size
  • #17 planner_task_tree_select_all
  • #18 planner_task_tree_new
  • #19 _gtk_marshal_VOID__STRING_STRING
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #24 gtk_cell_renderer_text_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #30 gtk_cell_editable_editing_done
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_entry_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #34 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #35 g_signal_emitv
    from /usr/lib/libgobject-2.0.so.0
  • #36 _gtk_binding_reset_parsed
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 _gtk_binding_reset_parsed
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 _gtk_binding_reset_parsed
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 gtk_bindings_activate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 gtk_widget_freeze_child_notify
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 gtk_entry_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #44 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #45 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #46 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #47 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #48 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 gtk_window_propagate_key_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #50 gtk_window_activate_key
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #52 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #53 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #54 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #55 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #56 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #57 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #58 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #59 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #60 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #61 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #62 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #63 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #64 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #65 main
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2007-06-29 00:24:34 UTC
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 ***