Bug 476979 – crash in Tasks: chossing the 'contacts' ...

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 476979 - crash in Tasks: chossing the 'contacts' ...


Summary:	crash in Tasks: chossing the 'contacts' ...


Status:	RESOLVED DUPLICATE of bug 475330

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-14 17:19 UTC by Jeff Payne
Modified:	2007-10-23 17:01 UTC

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

Description Jeff Payne 2007-09-14 17:19:47 UTC

Version: 2.10

What were you doing when the application crashed?
chossing the 'contacts' icon in th evolution preferences window.


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

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 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: 708702208 vsize: 708702208 resident: 66359296 share: 36397056 rss: 66359296 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189789734 rtime: 1540 utime: 1420 stime: 120 cutime:19 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496414864 (LWP 8636)]
[New Thread 1136679248 (LWP 8766)]
[New Thread 1136945488 (LWP 8665)]
[New Thread 1115699536 (LWP 8662)]
0x0000003d1ca0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 162936

Thread 1 (Thread 46912496414864 (LWP 8636))

#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 ??
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 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#39 bonobo_socket_add_id
from /usr/lib64/libbonoboui-2.so.0
#40 bonobo_control_frame_get_remote_window
from /usr/lib64/libbonoboui-2.so.0
#41 ??
from /usr/lib64/libbonoboui-2.so.0
#42 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#43 ??
from /lib64/libgobject-2.0.so.0
#44 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#45 g_signal_emit
from /lib64/libgobject-2.0.so.0
#46 gtk_widget_realize
from /usr/lib64/libgtk-x11-2.0.so.0
#47 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#48 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#49 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#50 ??
from /lib64/libgobject-2.0.so.0
#51 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#52 g_signal_emit
from /lib64/libgobject-2.0.so.0
#53 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#54 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#55 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#56 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#57 ??
from /lib64/libgobject-2.0.so.0
#58 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#59 g_signal_emit
from /lib64/libgobject-2.0.so.0
#60 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#61 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#62 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#63 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#64 ??
from /lib64/libgobject-2.0.so.0
#65 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#66 g_signal_emit
from /lib64/libgobject-2.0.so.0
#67 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#68 gtk_widget_set_child_visible
from /usr/lib64/libgtk-x11-2.0.so.0
#69 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#70 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#71 ??
from /lib64/libgobject-2.0.so.0
#72 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#73 g_signal_emit
from /lib64/libgobject-2.0.so.0
#74 set_page_timeout_callback
at e-multi-config-dialog.c line 122
#75 ??
from /lib64/libglib-2.0.so.0
#76 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#77 ??
from /lib64/libglib-2.0.so.0
#78 g_main_loop_run
from /lib64/libglib-2.0.so.0
#79 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#80 main
at main.c line 586
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Tobias Mueller 2007-10-23 17:01:22 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 475330 ***