Bug 577519 – crash in Evolution Mail and Calendar: starting 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 577519 - crash in Evolution Mail and Calendar: starting evolution


Summary:	crash in Evolution Mail and Calendar: starting evolution


Status:	RESOLVED DUPLICATE of bug 577198

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.24.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-03-31 19:28 UTC by bugreports
Modified:	2009-04-01 08:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description bugreports 2009-03-31 19:28:45 UTC

What were you doing when the application crashed?
starting evolution


Distribution: Debian squeeze/sid
Gnome Release: 2.24.2 2009-01-04 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.29-sonne #2 SMP PREEMPT Wed Mar 25 07:33:31 CET 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10599901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 77791232 vsize: 77791232 resident: 16629760 share: 13520896 rss: 16629760 rss_rlim: 18446744073709551615
CPU usage: start_time: 1238527642 rtime: 72 utime: 61 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb526e770 (LWP 20149)]
[New Thread 0xb3effb90 (LWP 20156)]
[New Thread 0xb48fbb90 (LWP 20155)]
0xb808d424 in __kernel_vsyscall ()

+ Trace 214062

Thread 3 (Thread 0xb48fbb90 (LWP 20155))

#0 __kernel_vsyscall
#1 __lll_lock_wait
at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S line 136
#2 _L_lock_89
from /lib/i686/cmov/libpthread.so.0
#3 __pthread_mutex_lock
at pthread_mutex_lock.c line 86
#4 segv_redirect
at main.c line 423
#5 <signal handler called>
#6 unixCheckReservedLock
at sqlite3.c line 23253
#7 camel_sqlite3_file_xCheckReservedLock
at camel-db.c line 283
#8 sqlite3PagerAcquire
at sqlite3.c line 12943
#9 sqlite3BtreeGetPage
at sqlite3.c line 38534
#10 sqlite3BtreeBeginTrans
at sqlite3.c line 39190
#11 sqlite3BtreeCursor
at sqlite3.c line 39293
#12 sqlite3InitOne
at sqlite3.c line 73438
#13 sqlite3Init
at sqlite3.c line 73617
#14 sqlite3ReadSchema
at sqlite3.c line 73653
#15 sqlite3Pragma
at sqlite3.c line 72427
#16 sqlite3Parser
at sqlite3.c line 87350
#17 sqlite3RunParser
at sqlite3.c line 88489
#18 sqlite3Prepare
at sqlite3.c line 73794
#19 sqlite3LockAndPrepare
at sqlite3.c line 73875
#20 sqlite3_exec
at sqlite3.c line 70703
#21 cdb_sql_exec
at camel-db.c line 432
#22 camel_db_command
at camel-db.c line 555
#23 camel_db_open
at camel-db.c line 496
#24 construct
at camel-store.c line 238
#25 offline_store_construct
at camel-offline-store.c line 97
#26 construct
at camel-imap-store.c line 243
#27 camel_service_construct
at camel-service.c line 315
#28 get_service
at camel-session.c line 198
#29 camel_session_get_service
at camel-session.c line 243
#30 get_store_exec
at mail-ops.c line 1350
#31 mail_msg_proxy
at mail-mt.c line 520
#32 g_thread_pool_thread_proxy
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gthreadpool.c line 265
#33 g_thread_create_proxy
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gthread.c line 635
#34 start_thread
at pthread_create.c line 297
#35 clone
at ../sysdeps/unix/sysv/linux/i386/clone.S line 130

Comment 1 Gianluca Borello 2009-04-01 08:56:05 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 577198 ***