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 619168 - crash in Evolution Mail: Writing an E-Mail and se...
crash in Evolution Mail: Writing an E-Mail and se...
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-05-20 07:46 UTC by ben.szurpit
Modified: 2010-05-21 07:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description ben.szurpit 2010-05-20 07:46:18 UTC 
What were you doing when the application crashed?
Writing an E-Mail and send it.


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

System: Linux 2.6.33-2010.05.06 #1 SMP PREEMPT Thu May 6 15:02:17 CEST 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: tropical
Icon Theme: tropical
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 224292864 vsize: 224292864 resident: 63815680 share: 26177536 rss: 63815680 rss_rlim: 18446744073709551615
CPU usage: start_time: 1274339203 rtime: 9995 utime: 4409 stime: 5586 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 0xac19db70 (LWP 6439)]
[New Thread 0xafafeb70 (LWP 6436)]
[New Thread 0xab99cb70 (LWP 16829)]
[New Thread 0xae815b70 (LWP 16824)]
[New Thread 0xae014b70 (LWP 16823)]
[New Thread 0xb02ffb70 (LWP 16810)]
[New Thread 0xb0c91b70 (LWP 16809)]
[New Thread 0xb1570b70 (LWP 16808)]
[New Thread 0xb1d71b70 (LWP 16807)]
0xb78b7424 in __kernel_vsyscall ()

+ Trace 222011

Thread 2 (Thread 0xac19db70 (LWP 6439))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_lock_881
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #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 ??
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #15 clone
    from /lib/i686/cmov/libc.so.6 

	Inferior 1 [process 16805] will be detached.

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


----------- .xsession-errors (3852 sec old) ---------------------
Error (42575): Illegal character <c5> in hex string
Error (42576): Illegal character <50> in hex string
Error (42578): Illegal character <c3> in hex string
Error (42580): Illegal character <f8> in hex string
Error (42581): Illegal character <ca> in hex string
Error (42582): Illegal character <4c> in hex string
Error (42583): Illegal character <a3> in hex string
Error (42585): Illegal character <e9> in hex string
Error (42586): Illegal character <04> in hex string
Error (42587): Illegal character <8c> in hex string
Error (42588): Illegal character <d1> in hex string
Error (42589): Illegal character <d0> in hex string
Error (42590): Illegal character <a5> in hex string
Error (42591): Illegal character <a3> in hex string
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2010-05-20 15:05:18 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 ***
Comment 2 ben.szurpit 2010-05-21 07:09:10 UTC 
(In reply to comment #1)
> 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 ***

complied