Bug 516751 – crash in Evolution: Nothing. A turn on compu...

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 516751 - crash in Evolution: Nothing. A turn on compu...


Summary:	crash in Evolution: Nothing. A turn on compu...


Status:	RESOLVED DUPLICATE of bug 498508

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.10.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-15 21:45 UTC by Łukasz Wojciech Hebda
Modified:	2008-03-02 17:32 UTC

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

Description Łukasz Wojciech Hebda 2008-02-15 21:45:05 UTC

What were you doing when the application crashed?
Nothing. A turn on computer, then X server raise up, and evolution was turn on.


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.3 2007-11-20 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-gentoo-r4 #12 Thu Nov 1 20:12:59 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 94613504 vsize: 94613504 resident: 7073792 share: 5439488 rss: 7073792 rss_rlim: 4294967295
CPU usage: start_time: 1195667332 rtime: 6 utime: 5 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-data-server-1.10'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1221998912 (LWP 5967)]
[New Thread -1268376688 (LWP 5981)]
[New Thread -1259983984 (LWP 5980)]
[New Thread -1251591280 (LWP 5979)]
[New Thread -1234805872 (LWP 5976)]
[New Thread -1226146928 (LWP 5970)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 189347

Thread 5 (Thread -1234805872 (LWP 5976))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_82
from /lib/libpthread.so.0
#3 __pthread_mutex_lock
at pthread_mutex_lock.c line 81
#4 gnome_segv_handler
at server.c line 97
#5 <signal handler called>
#6 e_cal_backend_file_open
at e-cal-backend-file.c line 697
#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 e_cal_backend_open
at e-cal-backend.c line 618
#10 impl_Cal_open
at e-data-cal.c line 81
#11 _ORBIT_skel_small_GNOME_Evolution_Calendar_Cal_open
at Evolution-DataServer-Calendar-common.c line 44
#12 ORBit_POAObject_invoke
at poa.c line 1142
#13 ORBit_OAObject_invoke
at orbit-adaptor.c line 338
#14 ORBit_small_invoke_adaptor
at orbit-small.c line 844
#15 ORBit_POAObject_handle_request
at poa.c line 1351
#16 ORBit_POAObject_invoke_incoming_request
at poa.c line 1421
#17 giop_thread_queue_process
at giop.c line 771
#18 giop_request_handler_thread
at giop.c line 481
#19 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#20 g_thread_create_proxy
at gthread.c line 635
#21 start_thread
at pthread_create.c line 296
#22 clone
from /lib/libc.so.6



----------- .xsession-errors (22 sec old) ---------------------
** 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
(evolution:5921): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Host lookup failed: imap.gmail.com: Temporary failure in name resolution
** (gnome-session:5878): WARNING **: Host name lookup failure on localhost.
--------------------------------------------------

Comment 1 Tobias Mueller 2008-03-02 17:32:18 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 ***