Bug 456248 – crash in Project Management: Abriendo un proyecto al ...

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 456248 - crash in Project Management: Abriendo un proyecto al ...


Summary:	crash in Project Management: Abriendo un proyecto al ...


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-07-12 13:55 UTC by jessicalir
Modified:	2007-08-27 09:14 UTC

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

Description jessicalir 2007-07-12 13:55:59 UTC

What were you doing when the application crashed?
Abriendo un proyecto al cual le había cambiado las relaciones de precedencia entre sus tareas.

Opening a project recently changed in it's task relationships


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: 73850880 vsize: 0 resident: 73850880 share: 0 rss: 16134144 rss_rlim: 0
CPU usage: start_time: 1184248402 rtime: 0 utime: 247 stime: 0 cutime:222 cstime: 0 timeout: 25 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 -1226664256 (LWP 4691)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 147531

Thread 1 (Thread -1226664256 (LWP 4691))

#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 gnome_canvas_item_move
from /usr/lib/libgnomecanvas-2.so.0
#16 gnome_canvas_item_move
from /usr/lib/libgnomecanvas-2.so.0
#17 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 main

Comment 1 Pascal Terjan 2007-08-27 09:14:39 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 ***