Bug 394133 – crash in Project Management: Linking 2 tasks graphica...

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 394133 - crash in Project Management: Linking 2 tasks graphica...


Summary:	crash in Project Management: Linking 2 tasks graphica...


Status:	RESOLVED DUPLICATE of bug 391737

Product:	planner
Classification:	Other
Component:	General
Version:	0.14
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	planner-maint
QA Contact:	planner-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-08 04:22 UTC by unixfanatic
Modified:	2007-02-05 23:02 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description unixfanatic 2007-01-08 04:22:21 UTC

What were you doing when the application crashed?
Linking 2 tasks graphically


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 59502592 vsize: 0 resident: 59502592 share: 0 rss: 22253568 rss_rlim: 0
CPU usage: start_time: 1168191051 rtime: 0 utime: 5084 stime: 0 cutime:4755 cstime: 0 timeout: 329 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 -1208654128 (LWP 21438)]
(no debugging symbols found)
0x001fd402 in __kernel_vsyscall ()

+ Trace 100358

Thread 1 (Thread -1208654128 (LWP 21438))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/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 /lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /lib/libgobject-2.0.so.0
#9 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#11 g_signal_emit
from /lib/libgobject-2.0.so.0
#12 g_object_class_override_property
from /lib/libgobject-2.0.so.0
#13 g_enum_register_static
from /lib/libgobject-2.0.so.0
#14 g_object_set_property
from /lib/libgobject-2.0.so.0
#15 planner_gantt_row_get_geometry
#16 planner_cmd_new_size
#17 planner_gantt_row_get_geometry
#18 gnome_canvas_marshal_BOOLEAN__BOXED
from /usr/lib/libgnomecanvas-2.so.0
#19 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /lib/libgobject-2.0.so.0
#21 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#23 g_signal_emit
from /lib/libgobject-2.0.so.0
#24 gnome_canvas_window_to_world
from /usr/lib/libgnomecanvas-2.so.0
#25 gnome_canvas_set_scroll_region
from /usr/lib/libgnomecanvas-2.so.0
#26 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#27 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#28 g_closure_invoke
from /lib/libgobject-2.0.so.0
#29 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#31 g_signal_emit
from /lib/libgobject-2.0.so.0
#32 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#35 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#36 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#37 g_main_context_check
from /lib/libglib-2.0.so.0
#38 g_main_loop_run
from /lib/libglib-2.0.so.0
#39 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#40 main
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-02-05 23:02:17 UTC

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 391737 ***