Bug 476966 – crash in Project Management: si esoty en visuta Gantt...

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 476966 - crash in Project Management: si esoty en visuta Gantt...


Summary:	crash in Project Management: si esoty en visuta Gantt...


Status:	RESOLVED DUPLICATE of bug 358415

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-09-14 16:10 UTC by DiegoEsJames
Modified:	2007-09-15 06:27 UTC

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

Description DiegoEsJames 2007-09-14 16:10:01 UTC

What were you doing when the application crashed?
si esoty en visuta Gantt y maximizo se cierra, asi que  me moví a tareas, maximize, me regrese a Gantt y se cerró


Distribution: Mandriva Linux release 2007.0 (Official) for i586
Gnome Release: 2.16.0 2006-09-04 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 39862272 vsize: 0 resident: 39862272 share: 0 rss: 14712832 rss_rlim: 0
CPU usage: start_time: 1189786108 rtime: 0 utime: 145 stime: 0 cutime:134 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/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227060352 (LWP 6591)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 162925

Thread 1 (Thread -1227060352 (LWP 6591))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/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_item_request_update
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 /usr/lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_override_class_closure
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/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_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#18 gtk_container_check_resize
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 main

Comment 1 Pascal Terjan 2007-09-15 06:27:37 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 358415 ***