Bug 449659 – crash in Tasks: Quiting

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 449659 - crash in Tasks: Quiting


Summary:	crash in Tasks: Quiting


Status:	RESOLVED DUPLICATE of bug 405646

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-21 02:06 UTC by sergey
Modified:	2007-06-21 02:49 UTC

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

Description sergey 2007-06-21 02:06:36 UTC

Version: 2.10

What were you doing when the application crashed?
Quiting


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 140333056 vsize: 140333056 resident: 57057280 share: 44883968 rss: 57057280 rss_rlim: 4294967295
CPU usage: start_time: 1182391386 rtime: 408 utime: 384 stime: 24 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 -1209116960 (LWP 4206)]
[New Thread -1332536432 (LWP 4321)]
[New Thread -1266787440 (LWP 4234)]
[New Thread -1244423280 (LWP 4232)]
(no debugging symbols found)
0x00ae1402 in __kernel_vsyscall ()

+ Trace 142563

Thread 4 (Thread -1244423280 (LWP 4232))

#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 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 ??
from /lib/libglib-2.0.so.0
#9 __nptl_deallocate_tsd
from /lib/libpthread.so.0
#10 start_thread
from /lib/libpthread.so.0
#11 clone
from /lib/libc.so.6



----------- .xsession-errors (18 sec old) ---------------------
** Message: No pilot cradle information located
** Message: Unable to load pilot cradle info, assuming unset
gpilotd-Message: Activating object OAFIID:GNOME_Pilot_Daemon
** Message: No pilot userid/username information located
** Message: Unable to load pilot id/username, assuming unset
** Message: No pilot cradle information located
** Message: Unable to load pilot cradle info, assuming unset
** Message: No pilot userid/username information located
** Message: Unable to load pilot id/username, assuming unset
** Message: No pilot cradle information located
** Message: Unable to load pilot cradle info, assuming unset
** Message: No pilot userid/username information located
** Message: Unable to load pilot id/username, assuming unset
** Message: No pilot cradle information located
** Message: Unable to load pilot cradle info, assuming unset
--------------------------------------------------

Comment 1 Karsten Bräckelmann 2007-06-21 02:49:38 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 405646 ***