Bug 425978 – crash in Evolution: trying to exit evolution...

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 425978 - crash in Evolution: trying to exit evolution...


Summary:	crash in Evolution: trying to exit evolution...


Status:	RESOLVED DUPLICATE of bug 455329

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-04-03 19:33 UTC by krobertson
Modified:	2007-09-26 23:05 UTC

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

Description krobertson 2007-04-03 19:33:41 UTC

What were you doing when the application crashed?
trying to exit evolution by clicking on the right hand corner X. 


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

Memory status: size: 218603520 vsize: 0 resident: 218603520 share: 0 rss: 60141568 rss_rlim: 0
CPU usage: start_time: 1175616246 rtime: 0 utime: 8197 stime: 0 cutime:7854 cstime: 0 timeout: 343 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 -1232750928 (LWP 5766)]
[New Thread -1341670496 (LWP 8916)]
[New Thread -1340773472 (LWP 6227)]
[New Thread -1316807776 (LWP 5784)]
[New Thread -1308415072 (LWP 5781)]
[New Thread -1300022368 (LWP 5780)]
[New Thread -1268728928 (LWP 5779)]
[New Thread -1278219360 (LWP 5777)]
[New Thread -1260336224 (LWP 5775)]
[New Thread -1250776160 (LWP 5774)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 124719

Thread 5 (Thread -1308415072 (LWP 5781))

#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 ??
#5 camel_message_info_ptr
from /usr/lib/libcamel-provider-1.2.so.8
#6 camel_folder_summary_new
from /usr/lib/libcamel-provider-1.2.so.8
#7 camel_exchange_summary_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelexchange.so
#8 camel_folder_summary_save
from /usr/lib/libcamel-provider-1.2.so.8
#9 camel_exchange_folder_get_type
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelexchange.so
#10 camel_folder_sync
from /usr/lib/libcamel-provider-1.2.so.8
#11 camel_store_sync
from /usr/lib/libcamel-provider-1.2.so.8
#12 camel_store_sync
from /usr/lib/libcamel-provider-1.2.so.8
#13 mail_empty_trash
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#14 mail_enable_stop
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#15 e_msgport_reply
from /usr/lib/libedataserver-1.2.so.7
#16 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#17 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 Akhil Laddha 2007-04-04 04:11:36 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here.  Thanks!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions

Comment 2 Bruno Boaventura 2007-05-05 15:01:36 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 3 Tobias Mueller 2007-09-26 23:05:30 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 455329 ***