Bug 450975 – crash in Tasks: closing 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 450975 - crash in Tasks: closing evolution


Summary:	crash in Tasks: closing 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-06-25 17:12 UTC by kevin
Modified:	2007-09-26 23:07 UTC

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

Description kevin 2007-06-25 17:12:11 UTC

Version: 2.10

What were you doing when the application crashed?
closing  evolution


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 173850624 vsize: 173850624 resident: 68259840 share: 45322240 rss: 68259840 rss_rlim: 4294967295
CPU usage: start_time: 1182786376 rtime: 7247 utime: 7004 stime: 243 cutime:2 cstime: 4 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 -1208953120 (LWP 3076)]
[New Thread -1337410672 (LWP 6823)]
[New Thread -1326920816 (LWP 4229)]
[New Thread -1278833776 (LWP 3135)]
[New Thread -1257854064 (LWP 3133)]
[New Thread -1211053168 (LWP 3130)]
(no debugging symbols found)
0x002da402 in __kernel_vsyscall ()

+ Trace 143626

Thread 2 (Thread -1337410672 (LWP 6823))

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



----------- .xsession-errors ---------------------
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x140438c
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1405c64
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x1405c64
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x4d
--------------------------------------------------

Comment 1 palfrey 2007-06-26 17:10:04 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:07:58 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 ***