Bug 508823 – crash in Tasks: Nothing!!

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 508823 - crash in Tasks: Nothing!!


Summary:	crash in Tasks: Nothing!!


Status:	RESOLVED DUPLICATE of bug 508541

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-11 18:58 UTC by w2ads
Modified:	2008-02-06 10:23 UTC

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

Description w2ads 2008-01-11 18:58:58 UTC

Version: 2.10

What were you doing when the application crashed?
Nothing!!


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 134520832 vsize: 134520832 resident: 28696576 share: 16338944 rss: 28696576 rss_rlim: 4294967295
CPU usage: start_time: 1199892947 rtime: 29665 utime: 26539 stime: 3126 cutime:0 cstime: 1 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 -1208431888 (LWP 2337)]
[New Thread -1318630512 (LWP 24116)]
[New Thread -1231844464 (LWP 13868)]
[New Thread -1282589808 (LWP 13866)]
[New Thread -1221354608 (LWP 2476)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 184969

Thread 2 (Thread -1318630512 (LWP 24116))

#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 (13287 sec old) ---------------------
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834
(evolution:2337): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:2337): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9b5b140'
(evolution:2337): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9b5b260'
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-06 10:23:16 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 508541 ***