Bug 509113 – crash in Tasks: Closing update of prefe...

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 509113 - crash in Tasks: Closing update of prefe...


Summary:	crash in Tasks: Closing update of prefe...


Status:	RESOLVED DUPLICATE of bug 449996

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-13 11:11 UTC by hansforsgren
Modified:	2008-02-06 08:39 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description hansforsgren 2008-01-13 11:11:19 UTC

Version: 2.10

What were you doing when the application crashed?
Closing  update of preferences ( text size).


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 20:27:10 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 687927296 vsize: 687927296 resident: 53313536 share: 33464320 rss: 53313536 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200221198 rtime: 3347 utime: 2484 stime: 863 cutime:36 cstime: 87 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496399728 (LWP 3606)]
[New Thread 1084496208 (LWP 3658)]
[New Thread 1115699536 (LWP 3656)]
[New Thread 1084229968 (LWP 3628)]
(no debugging symbols found)
0x000000332720d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 185149

Thread 1 (Thread 46912496399728 (LWP 3606))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
from /lib64/libglib-2.0.so.0
#4 ??
from /lib64/libglib-2.0.so.0
#5 ??
from /lib64/libglib-2.0.so.0
#6 g_slice_free_chain_with_offset
from /lib64/libglib-2.0.so.0
#7 pango_layout_line_unref
from /usr/lib64/libpango-1.0.so.0
#8 ??
from /usr/lib64/libpango-1.0.so.0
#9 ??
from /usr/lib64/libpango-1.0.so.0
#10 g_object_unref
from /lib64/libgobject-2.0.so.0
#11 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#12 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#13 ??
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit
from /lib64/libgobject-2.0.so.0
#16 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#35 gtk_widget_unparent
from /usr/lib64/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#38 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#39 ??
from /lib64/libgobject-2.0.so.0
#40 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#41 g_signal_emit
from /lib64/libgobject-2.0.so.0
#42 gtk_widget_unrealize
from /usr/lib64/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#44 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#45 ??
from /lib64/libgobject-2.0.so.0
#46 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#47 g_signal_emit
from /lib64/libgobject-2.0.so.0
#48 gtk_widget_unrealize
from /usr/lib64/libgtk-x11-2.0.so.0
#49 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#50 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#51 ??
from /lib64/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#53 g_signal_emit
from /lib64/libgobject-2.0.so.0
#54 gtk_widget_unrealize
from /usr/lib64/libgtk-x11-2.0.so.0
#55 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#56 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#57 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#58 ??
from /lib64/libgobject-2.0.so.0
#59 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#60 g_signal_emit
from /lib64/libgobject-2.0.so.0
#61 gtk_widget_unrealize
from /usr/lib64/libgtk-x11-2.0.so.0
#62 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#63 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#64 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#65 ??
from /lib64/libgobject-2.0.so.0
#66 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#67 g_signal_emit
from /lib64/libgobject-2.0.so.0
#68 gtk_widget_unrealize
from /usr/lib64/libgtk-x11-2.0.so.0
#69 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#70 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#71 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#72 ??
from /lib64/libgobject-2.0.so.0
#73 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#74 g_signal_emit
from /lib64/libgobject-2.0.so.0
#75 gtk_widget_unrealize
from /usr/lib64/libgtk-x11-2.0.so.0
#76 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#77 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#78 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#79 ??
from /lib64/libgobject-2.0.so.0
#80 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#81 g_signal_emit
from /lib64/libgobject-2.0.so.0
#82 gtk_widget_unrealize
from /usr/lib64/libgtk-x11-2.0.so.0
#83 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#84 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#85 ??
from /lib64/libgobject-2.0.so.0
#86 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#87 g_signal_emit
from /lib64/libgobject-2.0.so.0
#88 gtk_widget_unrealize
from /usr/lib64/libgtk-x11-2.0.so.0
#89 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#90 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#91 ??
from /usr/lib64/evolution/2.10/libemiscwidgets.so.0
#92 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#93 ??
from /lib64/libgobject-2.0.so.0
#94 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#95 g_signal_emit
from /lib64/libgobject-2.0.so.0
#96 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#97 ??
from /lib64/libgobject-2.0.so.0
#98 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#99 g_signal_emit
from /lib64/libgobject-2.0.so.0
#100 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#101 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#102 ??
from /lib64/libgobject-2.0.so.0
#103 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#104 g_signal_emit
from /lib64/libgobject-2.0.so.0
#105 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#106 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#107 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#108 ??
from /lib64/libgobject-2.0.so.0
#109 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#110 g_signal_emit
from /lib64/libgobject-2.0.so.0
#111 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#112 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#113 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#114 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#115 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#116 ??
from /lib64/libglib-2.0.so.0
#117 g_main_loop_run
from /lib64/libglib-2.0.so.0
#118 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#119 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Akhil Laddha 2008-02-06 08:39:51 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
the maintainers need more information to fix the bug. Could you please answer
the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 449996 ***