Bug 458579 – crash in 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 458579 - crash in Email:


Summary:	crash in Email:


Status:	RESOLVED DUPLICATE of bug 456623

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-20 09:05 UTC by giordanoyoshida
Modified:	2007-07-20 16:34 UTC

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

Description giordanoyoshida 2007-07-20 09:05:14 UTC

Version: 2.10

What were you doing when the application crashed?



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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 114294784 vsize: 114294784 resident: 35659776 share: 28663808 rss: 35659776 rss_rlim: 4294967295
CPU usage: start_time: 1184922302 rtime: 93 utime: 81 stime: 12 cutime:5 cstime: 9 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 -1208497424 (LWP 4307)]
[New Thread -1251427440 (LWP 4343)]
[New Thread -1230443632 (LWP 4340)]
(no debugging symbols found)
0x00e55402 in __kernel_vsyscall ()

+ Trace 149297

Thread 3 (Thread -1230443632 (LWP 4340))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 camel_pop3_engine_command_new
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
#7 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
#8 camel_pop3_delete_old
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
#9 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
#10 camel_folder_sync
from /usr/lib/libcamel-provider-1.2.so.10
#11 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#12 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#13 ??
from /lib/libglib-2.0.so.0
#14 ??
from /lib/libglib-2.0.so.0
#15 start_thread
from /lib/libpthread.so.0
#16 clone
from /lib/libc.so.6



----------- .xsession-errors (8 sec old) ---------------------
(evolution:4307): camel-pop3-provider-WARNING **: Bad server response: Subject: SUSPECT: TreSiti di oggi (11/07/07)
(evolution:4307): camel-pop3-provider-WARNING **: Bad server response: Date: Wed, 11 Jul 2007 01:53:10 +0100
(evolution:4307): camel-pop3-provider-WARNING **: Bad server response: MIME-Version: 1.0
(evolution:4307): camel-pop3-provider-WARNING **: Bad server response: *
(evolution:4307): camel-pop3-provider-WARNING **: Bad server response: I nostri prodotti in prova gratuita! 
--------------------------------------------------

Comment 1 palfrey 2007-07-20 16:34:27 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 456623 ***