Bug 436895 – crash in Evolution: adding a cached email to...

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 436895 - crash in Evolution: adding a cached email to...


Summary:	crash in Evolution: adding a cached email to...


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:	2007-05-08 14:00 UTC by lior
Modified:	2007-05-09 11:46 UTC

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

Description lior 2007-05-08 14:00:32 UTC

What were you doing when the application crashed?
adding a cached email to the CC


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

Memory status: size: 169553920 vsize: 0 resident: 169553920 share: 0 rss: 40321024 rss_rlim: 0
CPU usage: start_time: 1178632612 rtime: 0 utime: 594 stime: 0 cutime:554 cstime: 0 timeout: 40 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 -1233275216 (LWP 23776)]
[New Thread -1320862816 (LWP 23860)]
[New Thread -1334060128 (LWP 23856)]
[New Thread -1322255456 (LWP 23833)]
[New Thread -1310237792 (LWP 23812)]
[New Thread -1301451872 (LWP 23807)]
[New Thread -1293059168 (LWP 23806)]
[New Thread -1275053152 (LWP 23803)]
[New Thread -1266660448 (LWP 23802)]
[New Thread -1257411680 (LWP 23801)]
[New Thread -1247962208 (LWP 23799)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 133073

Thread 10 (Thread -1257411680 (LWP 23801))

#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 palfrey 2007-05-09 11:15:12 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 daniel.dodge 2007-05-09 11:25:59 UTC

Thanks for doing the debugging.  I'm trying to understand how this base bug applies to the bug I submitted since the base bug talks about a crash but I only had problems booking a resource for a calendar meeting entry.  However, I have been experiencing back-end crashes and slowness in looking up names in the GAL.

Keep up the good work!
D

Comment 3 palfrey 2007-05-09 11:46:53 UTC

(In reply to comment #2)
> Thanks for doing the debugging.  I'm trying to understand how this base bug
> applies to the bug I submitted since the base bug talks about a crash but I
> only had problems booking a resource for a calendar meeting entry.  However, I
> have been experiencing back-end crashes and slowness in looking up names in the
> GAL.

Your bug report and stacktrace was for a crash while trying to talk to the exchange server. You had the same stacktrace as the other bug, ergo probably the same bug.