Bug 472024 – crash in Tasks: Exited 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 472024 - crash in Tasks: Exited Evolution.


Summary:	crash in Tasks: Exited Evolution.


Status:	RESOLVED DUPLICATE of bug 455329

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-30 21:29 UTC by m3freak
Modified:	2007-09-26 23:07 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description m3freak 2007-08-30 21:29:16 UTC

Version: 2.10

What were you doing when the application crashed?
Exited Evolution.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 153698304 vsize: 153698304 resident: 56168448 share: 39047168 rss: 56168448 rss_rlim: 4294967295
CPU usage: start_time: 1188505121 rtime: 1058 utime: 979 stime: 79 cutime:3 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208744224 (LWP 6043)]
[New Thread -1275466864 (LWP 6574)]
[New Thread -1308140656 (LWP 6553)]
[New Thread -1275200624 (LWP 6088)]
[New Thread -1243718768 (LWP 6085)]
[New Thread -1232835696 (LWP 6084)]
0x00110402 in __kernel_vsyscall ()

+ Trace 159217

Thread 2 (Thread -1275466864 (LWP 6574))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 segv_redirect
at main.c line 417
#5 <signal handler called>
#6 ??
#7 camel_message_info_ptr
from /usr/lib/libcamel-provider-1.2.so.10
#8 ??
from /usr/lib/libcamel-provider-1.2.so.10
#9 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
#10 camel_folder_summary_save
from /usr/lib/libcamel-provider-1.2.so.10
#11 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
#12 camel_folder_sync
from /usr/lib/libcamel-provider-1.2.so.10
#13 ??
from /usr/lib/libcamel-provider-1.2.so.10
#14 camel_store_sync
from /usr/lib/libcamel-provider-1.2.so.10
#15 sync_store_exec
at mail-ops.c line 1484
#16 mail_msg_proxy
at mail-mt.c line 500
#17 ??
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 start_thread
from /lib/libpthread.so.0
#20 clone
from /lib/libc.so.6



----------- .xsession-errors (4199 sec old) ---------------------
Thu Aug 30 10:09:08 2007
 TXImage:     Using default colormap and visual, TrueColor, depth 24.
 CConn:       Using pixel format depth 8 (8bpp) colour-map
 CConn:       Using ZRLE encoding
BBDB spinning up...
(evolution:3653): gtkhtml-WARNING **: No such file or directory
(evolution:3653): gtkhtml-WARNING **: No such file or directory
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:6043): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:6043): DEBUG: mailto URL program: evolution
(evolution:6043): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__globalive%5crsandhu;auth_NTLM@mail.globalive.com_'
--------------------------------------------------

Comment 1 Tobias Mueller 2007-09-26 23:07:31 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 ***