Bug 483474 – crash in Evolution: iniciando sesion

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 483474 - crash in Evolution: iniciando sesion


Summary:	crash in Evolution: iniciando sesion


Status:	RESOLVED DUPLICATE of bug 498508

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	2.10.x (obsolete)
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-10-04 20:08 UTC by yeiko6
Modified:	2008-07-03 13:57 UTC

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

Description yeiko6 2007-10-04 20:08:26 UTC

What were you doing when the application crashed?
iniciando sesion


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-amd64 #1 SMP Tue Jul 10 21:39:38 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Smokey-Blue
Icon Theme: Smokey-Blue

Memory status: size: 311099392 vsize: 311099392 resident: 8695808 share: 6291456 rss: 8695808 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191516865 rtime: 5 utime: 3 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-data-server-1.10'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b4f4d3b4380 (LWP 7872)]
[New Thread 0x43046950 (LWP 7898)]
[New Thread 0x42044950 (LWP 7895)]
[New Thread 0x40040950 (LWP 7877)]
0x00002b4f4abbaa9f in waitpid () from /lib/libc.so.6

+ Trace 167787

Thread 2 (Thread 0x43046950 (LWP 7898))

#0 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#1 _L_mutex_lock_100
from /lib/libpthread.so.0
#2 pthread_mutex_lock
from /lib/libpthread.so.0
#3 gnome_segv_handler
at server.c line 97
#4 <signal handler called>
#5 get_uri_string_for_gnome_vfs
at e-cal-backend-file.c line 650
#6 e_cal_backend_file_open
at e-cal-backend-file.c line 698
#7 e_cal_backend_sync_open
at e-cal-backend-sync.c line 186
#8 _e_cal_backend_open
at e-cal-backend-sync.c line 706
#9 ORBit_small_invoke_adaptor
from /usr/lib/libORBit-2.so.0
#10 ??
from /usr/lib/libORBit-2.so.0
#11 ??
from /usr/lib/libORBit-2.so.0
#12 giop_thread_queue_process
from /usr/lib/libORBit-2.so.0
#13 ??
from /usr/lib/libORBit-2.so.0
#14 ??
from /usr/lib/libglib-2.0.so.0
#15 ??
from /usr/lib/libglib-2.0.so.0
#16 start_thread
from /lib/libpthread.so.0
#17 clone
from /lib/libc.so.6
#18 ??



----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------

Comment 1 Milan Crha 2008-07-03 13:57:37 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 498508 ***