Bug 438877 – crash in Project Management:

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 438877 - crash in Project Management:


Summary:	crash in Project Management:


Status:	RESOLVED DUPLICATE of bug 347555

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-05-16 12:22 UTC by sgg
Modified:	2007-06-22 21:50 UTC

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

Description sgg 2007-05-16 12:22:05 UTC

What were you doing when the application crashed?



Distribution: CentOS release 5 (Final)
Gnome Release: 2.16.0 2007-02-18 (CentOS)
BugBuddy Version: 2.16.0

Memory status: size: 49573888 vsize: 0 resident: 49573888 share: 0 rss: 18948096 rss_rlim: 0
CPU usage: start_time: 1179318017 rtime: 0 utime: 412 stime: 0 cutime:401 cstime: 0 timeout: 11 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 -1208506672 (LWP 4845)]
(no debugging symbols found)
0x0071e402 in __kernel_vsyscall ()

+ Trace 134441

Thread 1 (Thread -1208506672 (LWP 4845))

#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 planner_gantt_print_do
#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__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#9 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 g_signal_emit
from /lib/libgobject-2.0.so.0
#14 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#16 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#17 gdk_window_process_updates
from /usr/lib/libgdk-x11-2.0.so.0
#18 gtk_label_new
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_cclosure_marshal_VOID__VOID
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 gtk_adjustment_value_changed
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_adjustment_set_value
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_scrolled_window_new
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#28 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#29 g_closure_invoke
from /lib/libgobject-2.0.so.0
#30 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#32 g_signal_emit
from /lib/libgobject-2.0.so.0
#33 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#36 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#37 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#38 g_main_context_check
from /lib/libglib-2.0.so.0
#39 g_main_loop_run
from /lib/libglib-2.0.so.0
#40 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#41 main
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-06-22 21:50:07 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 347555 ***