Bug 458649 – 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 458649 - 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 13:28 UTC by giordanoyoshida
Modified:	2007-07-20 16:35 UTC

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

Description giordanoyoshida 2007-07-20 13:28:39 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: 114442240 vsize: 114442240 resident: 35536896 share: 28692480 rss: 35536896 rss_rlim: 4294967295
CPU usage: start_time: 1184938067 rtime: 87 utime: 76 stime: 11 cutime:5 cstime: 11 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 -1208698128 (LWP 4708)]
[New Thread -1282598000 (LWP 4764)]
[New Thread -1241134192 (LWP 4744)]
[New Thread -1230644336 (LWP 4742)]
[New Thread -1220154480 (LWP 4741)]
(no debugging symbols found)
0x00228402 in __kernel_vsyscall ()

+ Trace 149352

Thread 5 (Thread -1220154480 (LWP 4741))

#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 strlen
from /lib/libc.so.6
#7 camel_pop3_engine_iterate
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
#8 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
#9 camel_folder_refresh_info
from /usr/lib/libcamel-provider-1.2.so.10
#10 camel_pop3_folder_new
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
#11 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
#12 ??
from /usr/lib/libcamel-provider-1.2.so.10
#13 camel_store_get_inbox
from /usr/lib/libcamel-provider-1.2.so.10
#14 mail_tool_get_inbox
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#15 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#16 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#17 ??
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 start_thread
from /lib/libpthread.so.0
#20 clone
from /lib/libc.so.6



----------- .xsession-errors (11 sec old) ---------------------
(evolution:4611): camel-pop3-provider-WARNING **: Bad server response: 1 28237
(evolution:4611): camel-pop3-provider-WARNING **: Bad server response: 2 3307
(evolution:4611): camel-pop3-provider-WARNING **: Bad server response: 25
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:4708): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4708): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
--------------------------------------------------

Comment 1 palfrey 2007-07-20 16:35:00 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 ***