Bug 493916 – crash in Evolution: responding to an email

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 493916 - crash in Evolution: responding to an email


Summary:	crash in Evolution: responding to an email


Status:	RESOLVED DUPLICATE of bug 492354

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-05 21:30 UTC by mark
Modified:	2007-11-07 22:32 UTC

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

Description mark 2007-11-05 21:30:40 UTC

What were you doing when the application crashed?
responding to an email


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.16-2-686 #1 Fri Aug 18 19:01:49 UTC 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 100290560 vsize: 100290560 resident: 24285184 share: 10268672 rss: 24285184 rss_rlim: 4294967295
CPU usage: start_time: 1194296665 rtime: 7813 utime: 7463 stime: 350 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage'

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xa663b6b0 (LWP 5123)]
[New Thread 0xa1bfbb90 (LWP 7407)]
[New Thread 0xa23fcb90 (LWP 7129)]
[New Thread 0xa6539b90 (LWP 5570)]
[New Thread 0xa6596b90 (LWP 5125)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 175546

Thread 2 (Thread 0xa1bfbb90 (LWP 7407))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#3 <signal handler called>
#4 IA__g_hash_table_foreach
at /tmp/buildd/glib2.0-2.14.1/glib/ghash.c line 680
#5 e_xmlhash_foreach_key
at e-xml-hash-utils.c line 322
#6 e_file_cache_get_object
at e-file-cache.c line 318
#7 e_file_cache_add_object
at e-file-cache.c line 380
#8 e_file_cache_replace_object
at e-file-cache.c line 413
#9 e_book_backend_cache_add_contact
at e-book-backend-cache.c line 297
#10 update_cache
at e-book-backend-exchange.c line 528
#11 g_thread_create_proxy
at /tmp/buildd/glib2.0-2.14.1/glib/gthread.c line 635
#12 start_thread
from /lib/i686/cmov/libpthread.so.0
#13 clone
from /lib/i686/cmov/libc.so.6



----------- .xsession-errors (68 sec old) ---------------------
Window manager warning: Property _NET_WM_ICON_NAME on window 0x2c00072 contained invalid UTF-8
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
LoadPlugin: failed to initialize shared library /usr/lib/totem/libtotem-complex-plugin.so [/usr/lib/totem/libtotem-complex-plugin.so: undefined symbol: _ZN13nsTArray_base9sEmptyHdrE]
(gnome-panel:4947): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8
Window manager warning: Property _NET_WM_NAME on window 0x2c008bc contained invalid UTF-8
Window manager warning: Property _NET_WM_ICON_NAME on window 0x2c008bc contained invalid UTF-8
(gnome-panel:4947): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8
--------------------------------------------------

Comment 1 André Klapper 2007-11-07 22:32:25 UTC

same crash as bug 492354

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