Bug 483787 – crash in Project Management: Using the REsource usage...

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 483787 - crash in Project Management: Using the REsource usage...


Summary:	crash in Project Management: Using the REsource usage...


Status:	RESOLVED DUPLICATE of bug 372694

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-05 15:32 UTC by enuresist
Modified:	2007-10-19 00:51 UTC

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

Description enuresist 2007-10-05 15:32:19 UTC

Version: 0.14.1

What were you doing when the application crashed?
Using the REsource usage window to reallocate some human resources (change the number of units)


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

Memory status: size: 62111744 vsize: 0 resident: 62111744 share: 0 rss: 25501696 rss_rlim: 0
CPU usage: start_time: 1191583981 rtime: 0 utime: 3815 stime: 0 cutime:3686 cstime: 0 timeout: 129 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 -1225869120 (LWP 9377)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 168038

Thread 1 (Thread -1225869120 (LWP 9377))

#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_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_object_set
from /usr/lib/libgobject-2.0.so.0
#16 planner_task_date_widget_new
#17 planner_cmd_new_size
#18 planner_task_dialog_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 gtk_cell_renderer_text_new
from /usr/lib/libgtk-x11-2.0.so.0
#26 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#31 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_window_set_auto_startup_notification
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
#34 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-10-19 00:51:30 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 ***