Bug 502287 – crash in Tasks: 1:st fetch of mail after...

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 502287 - crash in Tasks: 1:st fetch of mail after...


Summary:	crash in Tasks: 1:st fetch of mail after...


Status:	RESOLVED DUPLICATE of bug 493378

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
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-12-07 10:33 UTC by hansforsgren
Modified:	2007-12-07 16:28 UTC

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

Description hansforsgren 2007-12-07 10:33:03 UTC

What were you doing when the application crashed?
1:st fetch of mail after configuration


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 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: 612491264 vsize: 612491264 resident: 40304640 share: 22106112 rss: 40304640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1197022874 rtime: 967 utime: 794 stime: 173 cutime:4 cstime: 7 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 46912507839520 (LWP 3153)]
[New Thread 1157658960 (LWP 3456)]
[New Thread 1147169104 (LWP 3454)]
[New Thread 1115699536 (LWP 3219)]
(no debugging symbols found)
0x000000369e00d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 181087

Thread 1 (Thread 46912507839520 (LWP 3153))

#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_free1
from /lib64/libglib-2.0.so.0
#7 g_ptr_array_free
from /lib64/libglib-2.0.so.0
#8 ??
from /usr/lib64/librsvg-2.so.2
#9 ??
from /usr/lib64/librsvg-2.so.2
#10 ??
from /usr/lib64/librsvg-2.so.2
#11 ??
from /usr/lib64/librsvg-2.so.2
#12 g_object_unref
from /lib64/libgobject-2.0.so.0
#13 ??
from /usr/lib64/gtk-2.0/2.10.0/loaders/svg_loader.so
#14 gdk_pixbuf_loader_close
from /usr/lib64/libgdk_pixbuf-2.0.so.0
#15 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#16 gtk_icon_info_load_icon
from /usr/lib64/libgtk-x11-2.0.so.0
#17 gtk_icon_theme_load_icon
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 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#22 ??
from /lib64/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#24 g_signal_emit
from /lib64/libgobject-2.0.so.0
#25 gtk_widget_realize
from /usr/lib64/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#27 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#28 ??
from /lib64/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#30 g_signal_emit
from /lib64/libgobject-2.0.so.0
#31 gtk_widget_show
from /usr/lib64/libgtk-x11-2.0.so.0
#32 gtk_dialog_run
from /usr/lib64/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib64/libedataserverui-1.2.so.8
#34 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#35 ??
from /lib64/libglib-2.0.so.0
#36 g_main_loop_run
from /lib64/libglib-2.0.so.0
#37 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#38 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 palfrey 2007-12-07 16:28:07 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 493378 ***