Bug 373176 – crash in Project Management: Editando uma tarefa em r...

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 373176 - crash in Project Management: Editando uma tarefa em r...


Summary:	crash in Project Management: Editando uma tarefa em r...


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:	2006-11-09 23:12 UTC by otomiltonab
Modified:	2007-02-10 17:49 UTC

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

Description otomiltonab 2006-11-09 23:12:02 UTC

Version: 0.14.1

What were you doing when the application crashed?
Editando uma tarefa em relação à sua duração


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

Memory status: size: 219394048 vsize: 219394048 resident: 34545664 share: 15638528 rss: 34545664 rss_rlim: -1
CPU usage: start_time: 1163105717 rtime: 6057 utime: 5849 stime: 208 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 46923721284768 (LWP 5099)]
(no debugging symbols found)
0x00002aad43be2eef in waitpid () from /lib/libpthread.so.0

+ Trace 84886

Thread 1 (Thread 46923721284768 (LWP 5099))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 mrp_task_manager_calculate_task_work
from /usr/lib/libplanner-1.so.0
#4 mrp_task_manager_recalc
from /usr/lib/libplanner-1.so.0
#5 mrp_object_set
from /usr/lib/libplanner-1.so.0
#6 planner_task_date_widget_new
#7 planner_cmd_new_size
#8 planner_task_date_widget_new
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 gtk_toggle_button_toggled
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 gtk_toggle_action_new
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#24 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#29 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#32 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#33 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#35 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Marc-Andre Lureau 2007-02-10 17:49:15 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 372694 ***