Bug 476357 – crash in Tasks: closing evolution with t...

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 476357 - crash in Tasks: closing evolution with t...


Summary:	crash in Tasks: closing evolution with t...


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-09-12 22:00 UTC by slovas
Modified:	2007-09-26 23:08 UTC

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

Description slovas 2007-09-12 22:00:21 UTC

Version: 2.10

What were you doing when the application crashed?
closing evolution with the quit command


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: No
Accessibility: Disabled
GTK+ Theme: Bluecurve-BerriesAndCream
Icon Theme: gnome

Memory status: size: 177410048 vsize: 177410048 resident: 65228800 share: 42242048 rss: 65228800 rss_rlim: 4294967295
CPU usage: start_time: 1189603707 rtime: 1931 utime: 1618 stime: 313 cutime:12 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208264992 (LWP 28137)]
[New Thread -1326421104 (LWP 7175)]
[New Thread -1315931248 (LWP 28244)]
[New Thread -1337304176 (LWP 28221)]
[New Thread -1258300528 (LWP 28182)]
[New Thread -1247810672 (LWP 28181)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 162476

Thread 2 (Thread -1326421104 (LWP 7175))

#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 ??
#5 <signal handler called>
#6 camel_message_info_ptr
from /usr/lib/libcamel-provider-1.2.so.10
#7 ??
from /usr/lib/libcamel-provider-1.2.so.10
#8 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
#9 camel_folder_summary_save
from /usr/lib/libcamel-provider-1.2.so.10
#10 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
#11 camel_folder_sync
from /usr/lib/libcamel-provider-1.2.so.10
#12 ??
from /usr/lib/libcamel-provider-1.2.so.10
#13 camel_store_sync
from /usr/lib/libcamel-provider-1.2.so.10
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#15 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#16 ??
from /lib/libglib-2.0.so.0
#17 ??
from /lib/libglib-2.0.so.0
#18 start_thread
from /lib/libpthread.so.0
#19 clone
from /lib/libc.so.6



----------- .xsession-errors (36 sec old) ---------------------
beagleShouldIndex: strange page: [object XULElement]
beagleShouldIndex: strange page: [object XULElement]
beagleShouldIndex: strange page: [object XULElement]
beagleShouldIndex: strange page: [object XPCNativeWrapper [object HTMLDocument]]
beaglePageLoad: storing page: http://www.google.com/ig
beaglePageLoad: beagleWriteContent sucessful!
beaglePageLoad: beagleWriteMetadata sucessful!
beagleShouldIndex: strange page: [object XULElement]
beagleShouldIndex: strange page: [object XULElement]
beagleShouldIndex: strange page: [object XULElement]
beagleShouldIndex: strange page: [object XULElement]
beagleShouldIndex: strange page: [object XULElement]
beagleShouldIndex: strange page: [object XULElement]
beagleShouldIndex: strange page: [object XULElement]
beagleShouldIndex: strange page: [object XULElement]
--------------------------------------------------

Comment 1 Kjartan Maraas 2007-09-19 15:41:20 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 2 Tobias Mueller 2007-09-26 23:08:16 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 ***