Bug 510655 – crash in Evolution Mail:

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 510655 - crash in Evolution Mail:


Summary:	crash in Evolution Mail:


Status:	RESOLVED DUPLICATE of bug 445309

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:	2008-01-19 18:15 UTC by ingo.theiss
Modified:	2008-03-04 23:08 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description ingo.theiss 2008-01-19 18:15:46 UTC

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.21.1 #1 PREEMPT Tue May 8 19:52:29 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: nuoveXT

Memory status: size: 149098496 vsize: 149098496 resident: 30740480 share: 17891328 rss: 30740480 rss_rlim: 4294967295
CPU usage: start_time: 1200766440 rtime: 717 utime: 615 stime: 102 cutime:1 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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

(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 0xb6889b10 (LWP 4548)]
[New Thread 0xb0594b90 (LWP 4942)]
[New Thread 0xb0defb90 (LWP 4916)]
[New Thread 0xb15efb90 (LWP 4841)]
[New Thread 0xb1e5cb90 (LWP 4836)]
[New Thread 0xb265cb90 (LWP 4795)]
[New Thread 0xb36cdb90 (LWP 4761)]
[New Thread 0xb3ecdb90 (LWP 4760)]
[New Thread 0xb46cdb90 (LWP 4759)]
[New Thread 0xb4ecdb90 (LWP 4758)]
[New Thread 0xb56cdb90 (LWP 4757)]
[New Thread 0xb5ecdb90 (LWP 4756)]
(no debugging symbols found)
0xb78fabf1 in waitpid () from /lib/libpthread.so.0

+ Trace 185987

Thread 1 (Thread 0xb6889b10 (LWP 4548))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 ??
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 <signal handler called>
#13 fsync
from /lib/libpthread.so.0
#14 camel_certdb_save
from /usr/lib/libcamel-1.2.so.10
#15 ??
from /usr/lib/libcamel-1.2.so.10
#16 ??
#17 ??
from /usr/lib/libbonoboui-2.so.0
#18 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (13 sec old) ---------------------
(evolution:4548): e-data-server-WARNING **: Could not open converter for 'unicode-1-1-utf-7' to 'UTF-8' charset
(evolution:4548): camel-local-provider-WARNING **: Didn't get the next message where I expected (24748405) got 25380946 instead
(evolution:4548): camel-local-provider-WARNING **: Didn't get the next message where I expected (24748405) got 25380946 instead
(evolution:4548): e-data-server-WARNING **: Error in execution: Nachricht konnte nicht abgerufen werden
(evolution:4548): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:4548): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:4548): e-data-server-WARNING **: Error in execution: Nachricht konnte nicht abgerufen werden
--------------------------------------------------

Comment 1 André Klapper 2008-03-04 23:08:22 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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