Bug 374622 – crash in Evolution: reading mail and editing...

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 374622 - crash in Evolution: reading mail and editing...


Summary:	crash in Evolution: reading mail and editing...


Status:	RESOLVED DUPLICATE of bug 348126

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-13 10:20 UTC by pawal
Modified:	2006-11-21 18:21 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description pawal 2006-11-13 10:20:36 UTC

What were you doing when the application crashed?
reading mail and editing preferences


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 157794304 vsize: 0 resident: 157794304 share: 0 rss: 36212736 rss_rlim: 0
CPU usage: start_time: 1163413072 rtime: 0 utime: 2909 stime: 0 cutime:2719 cstime: 0 timeout: 190 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232869712 (LWP 5143)]
[New Thread -1325405280 (LWP 5300)]
[New Thread -1306539104 (LWP 5225)]
[New Thread -1306272864 (LWP 5161)]
[New Thread -1297486944 (LWP 5157)]
[New Thread -1289094240 (LWP 5156)]
[New Thread -1267782752 (LWP 5152)]
[New Thread -1259390048 (LWP 5151)]
[New Thread -1249498208 (LWP 5150)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 86020

Thread 7 (Thread -1267782752 (LWP 5152))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 camel_exchange_store_connected
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelexchange.so
#11 camel_object_trigger_event
from /usr/lib/libcamel-1.2.so.8
#12 camel_stub_send
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelexchange.so
#13 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#14 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 André Klapper 2006-11-13 11:28:22 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 348126 ***

Comment 2 Veerapuram Varadhan 2006-11-21 18:21:28 UTC

Thanks for reporting the bug.  As mentioned in comment#1, this has been reported already, however, it will be easy for devs to identify issues quickly, if stack traces with debug-symbols are attached.