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 621501 - crash in Evolution Mail: sending emails
crash in Evolution Mail: sending emails
Status: RESOLVED DUPLICATE of bug 612178
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.30.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-06-14 06:52 UTC by Oli
Modified: 2010-06-14 10:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description Oli 2010-06-14 06:52:12 UTC 
What were you doing when the application crashed?
sending emails


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

System: Linux 2.6.32 #1 SMP PREEMPT Wed Jan 27 08:59:56 CET 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ThinIce
Icon Theme: Mac4Lin_Icons_v1.0
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 210624512 vsize: 210624512 resident: 58118144 share: 23760896 rss: 58118144 rss_rlim: 18446744073709551615
CPU usage: start_time: 1276496752 rtime: 5050 utime: 4715 stime: 335 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xad07ab70 (LWP 8755)]
[New Thread 0xac6dcb70 (LWP 8754)]
[New Thread 0xac723b70 (LWP 5537)]
[New Thread 0xb3bffb70 (LWP 5528)]
[New Thread 0xb46c1b70 (LWP 5527)]
[New Thread 0xb4ec4b70 (LWP 5524)]
[New Thread 0xb56c5b70 (LWP 5523)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 222392

Thread 2 (Thread 0xad07ab70 (LWP 8755))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S line 142
  • #2 _L_lock_748
    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
    at camel-exchange-utils.c line 3005
  • #7 exchange_send_to
    at camel-exchange-transport.c line 167
  • #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 5521] will be detached.

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


----------- .xsession-errors (326 sec old) ---------------------
(firefox-bin:7046): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:7046): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:7046): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:7046): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:7046): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:7046): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:7046): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:7046): Gdk-WARNING **: XID collision, trouble ahead
--------------------------------------------------
Comment 1 Akhil Laddha 2010-06-14 10:58:14 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 ***