Bug 597418 – crash in Evolution Mail and Calendar: i opened a mail to read ...

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 597418 - crash in Evolution Mail and Calendar: i opened a mail to read ...


Summary:	crash in Evolution Mail and Calendar: i opened a mail to read ...


Status:	RESOLVED DUPLICATE of bug 569700

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.24.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-10-05 13:41 UTC by kari.heinonen
Modified:	2009-10-05 22:58 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description kari.heinonen 2009-10-05 13:41:39 UTC

What were you doing when the application crashed?
i opened a mail to read it


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.24.3 2009-06-17 (Gentoo)
BugBuddy Version: 2.24.2

System: Linux 2.6.30-gentoo-r4 #1 SMP Wed Aug 26 10:02:32 EEST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 2441330688 vsize: 2441330688 resident: 168509440 share: 25640960 rss: 168509440 rss_rlim: 18446744073709551615
CPU usage: start_time: 1254204096 rtime: 622326 utime: 620524 stime: 1802 cutime:0 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6326720 (LWP 23765)]
[New Thread 0x2bff8b90 (LWP 7885)]
[New Thread 0x30000b90 (LWP 6065)]
[New Thread 0xb3bffb90 (LWP 26106)]
[New Thread 0xb28ffb90 (LWP 26104)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 218063

Thread 2 (Thread 0x2bff8b90 (LWP 7885))

#0 __kernel_vsyscall
#1 __lll_lock_wait
at ../nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S line 136
#2 _L_lock_93
from /lib/libpthread.so.0
#3 __pthread_mutex_lock
at pthread_mutex_lock.c line 86
#4 <signal handler called>
#5 camel_mime_parser_read
at camel-mime-parser.c line 655
#6 stream_read
at camel-http-stream.c line 487
#7 camel_stream_read
at camel-stream.c line 98
#8 emfh_gethttp
at em-format-html.c line 529
#9 efh_format_exec
at em-format-html.c line 1302
#10 mail_msg_proxy
at mail-mt.c line 520
#11 IA__g_unichar_digit_value
at guniprop.c line 672
#12 g_tree_node_rotate_right
at gtree.c line 1177
#13 start_thread
at pthread_create.c line 297
#14 clone
at ../sysdeps/unix/sysv/linux/i386/clone.S line 130



----------- .xsession-errors (3467464 sec old) ---------------------
	->foomatic-ppds/Gestetner/Gestetner-3532_4235g-Postscript.ppd.gz (Gestetner 3532/4235g PS)[0]

** (gnome-cups-add:14158): WARNING **: Two ppds have driver == 'PXL'
	->foomatic-ppds/Gestetner/Gestetner-3532_4235g-pxlmono.ppd.gz (Gestetner 3532/4235g PXL[0]) and
	->foomatic-db-ppds/Gestetner/PXL/Gestetner-3532_4235g_PXL.ppd.gz (Gestetner 3532/4235g PXL)[0]

** (gnome-cups-add:14158): WARNING **: Two ppds have driver == 'PXL'
	->lsb/usr/Gestetner/Gestetner-3532_4235g-pxlmono.ppd.gz (Gestetner 3532/4235g PXL[0]) and
	->foomatic-ppds/Gestetner/Gestetner-3532_4235g-pxlmono.ppd.gz (Gestetner 3532/4235g PXL)[0]

** (gnome-cups-add:14158): WARNING **: Two ppds have driver == 'PS'
	->foomatic-ppds/Gestetner/Gestetner-4502-Postscript.ppd.gz (Gestetner 4502 PS[0]) and
	->foomatic-db-ppds/Gestetner/PS/Gestetner-4502_PS.ppd.gz (Gestetner 4502 PS)[0]
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-10-05 22:58:23 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 bug 569700 ***