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 619831 - crash in Evolution Mail: evolution crashed while ...
crash in Evolution Mail: evolution crashed while ...
Status: RESOLVED DUPLICATE of bug 612178
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.30.x
Other All
: Normal critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2010-05-27 13:57 UTC by Johannes Rohr
Modified: 2010-05-28 04:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description Johannes Rohr 2010-05-27 13:57:17 UTC
What were you doing when the application crashed?
evolution crashed while sending e-mail


Distribution: Debian squeeze/sid
Gnome Release: 2.30.0 2010-04-26 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-5-686 #1 SMP Wed May 19 19:51:54 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 607711232 vsize: 607711232 resident: 110231552 share: 20062208 rss: 110231552 rss_rlim: 18446744073709551615
CPU usage: start_time: 1274958765 rtime: 10466 utime: 9162 stime: 1304 cutime:67 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 0xa29fbb70 (LWP 29707)]
[New Thread 0x92bf9b70 (LWP 29705)]
[New Thread 0x9c3feb70 (LWP 21422)]
[New Thread 0x9cbffb70 (LWP 21421)]
[New Thread 0x9f5fab70 (LWP 21419)]
[New Thread 0xa05fcb70 (LWP 21418)]
[New Thread 0xa49ffb70 (LWP 21415)]
[New Thread 0xaeffeb70 (LWP 17528)]
[New Thread 0x9e5f8b70 (LWP 17343)]
[New Thread 0x9ddf7b70 (LWP 17281)]
[New Thread 0x9fdfbb70 (LWP 17280)]
[New Thread 0xa31fcb70 (LWP 17200)]
[New Thread 0xa5bf8b70 (LWP 17199)]
[New Thread 0xa8346b70 (LWP 17198)]
[New Thread 0xa8bfeb70 (LWP 17137)]
[New Thread 0xa93ffb70 (LWP 17135)]
[New Thread 0xa9dfab70 (LWP 17133)]
[New Thread 0xaa5fbb70 (LWP 17132)]
[New Thread 0xaadfcb70 (LWP 17131)]
[New Thread 0xab5fdb70 (LWP 17130)]
[New Thread 0xabdfeb70 (LWP 17129)]
[New Thread 0xac5ffb70 (LWP 17128)]
[New Thread 0xacffab70 (LWP 17126)]
[New Thread 0xae7fdb70 (LWP 17125)]
[New Thread 0xad7fbb70 (LWP 17124)]
[New Thread 0xadffcb70 (LWP 17123)]
[New Thread 0xb01feb70 (LWP 17119)]
[New Thread 0xb09ffb70 (LWP 17118)]
[New Thread 0xb132db70 (LWP 17116)]
[New Thread 0xb1b2eb70 (LWP 17115)]
0xb77c8424 in __kernel_vsyscall ()

Thread 3 (Thread 0x92bf9b70 (LWP 29705))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S line 142
  • #2 _L_lock_881
    from /lib/i686/cmov/libpthread.so.0
  • #3 __pthread_mutex_lock
    at pthread_mutex_lock.c line 61
  • #4 segv_redirect
    at main.c line 288
  • #5 <signal handler called>
  • #6 camel_exchange_utils_send_message
    from /usr/lib/evolution-data-server-1.2/camel-providers-14/libcamelexchange.so
  • #7 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers-14/libcamelexchange.so
  • #8 camel_transport_send_to
    at camel-transport.c line 133
  • #9 mail_send_message
    at mail-ops.c line 545
  • #10 send_queue_exec
    at mail-ops.c line 766
  • #11 mail_msg_proxy
    at mail-mt.c line 471
  • #12 g_thread_pool_thread_proxy
    at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gthreadpool.c line 315
  • #13 g_thread_create_proxy
    at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gthread.c line 1893
  • #14 start_thread
    at pthread_create.c line 300
  • #15 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130

	Inferior 1 [process 17110] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (241 sec old) ---------------------
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Error: FoFiType1::parse a line has more than 255 characters, we don't support this
Warnung der Fensterverwaltung:Received a _NET_WM_MOVERESIZE message for 0x2613995 (SV: Fwd: D); these messages lack timestamps and therefore suck.
--------------------------------------------------
Comment 1 Akhil Laddha 2010-05-28 04:30:46 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 bug 612178 ***