Bug 458073 – crash in Tasks: I

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 458073 - crash in Tasks: I


Summary:	crash in Tasks: I


Status:	RESOLVED DUPLICATE of bug 455158

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-07-18 19:42 UTC by janek.czajkowski
Modified:	2007-07-19 15:11 UTC

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

Description janek.czajkowski 2007-07-18 19:42:17 UTC

Version: 2.10

What were you doing when the application crashed?
I'm clossing evolution


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

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 620417024 vsize: 620417024 resident: 54513664 share: 29257728 rss: 54513664 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184786436 rtime: 509 utime: 450 stime: 59 cutime:25 cstime: 25 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496367296 (LWP 5648)]
[New Thread 1126455632 (LWP 5909)]
[New Thread 1115965776 (LWP 5702)]
(no debugging symbols found)
0x000000330de0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 148923

Thread 2 (Thread 1126455632 (LWP 5909))

#0 __lll_mutex_lock_wait
from /lib64/libpthread.so.0
#1 _L_mutex_lock_103
from /lib64/libpthread.so.0
#2 pthread_mutex_lock
from /lib64/libpthread.so.0
#3 <signal handler called>
#4 ??
from /lib64/libglib-2.0.so.0
#5 ??
from /lib64/libglib-2.0.so.0
#6 ??
from /lib64/libglib-2.0.so.0
#7 __nptl_deallocate_tsd
from /lib64/libpthread.so.0
#8 start_thread
from /lib64/libpthread.so.0
#9 clone
from /lib64/libc.so.6



----------- .xsession-errors (5302 sec old) ---------------------
(evolution:4163): evolution-mail-WARNING **: Failed to refresh folders: Cannot get folder `/home/janek/.gconf/desktop/gnome': not a maildir directory.
(evolution:4163): evolution-mail-WARNING **: Failed to refresh folders: Cannot get folder `/home/janek/.gconf/desktop/gnome/background': not a maildir directory.
(evolution:4163): evolution-mail-WARNING **: Failed to refresh folders: Cannot get folder `/home/janek/.gconf/desktop/gnome/accessibility': not a maildir directory.
(evolution:4163): evolution-mail-WARNING **: Failed to refresh folders: Cannot get folder `/home/janek/.gconf/desktop/gnome/accessibility/keyboard': not a maildir directory.
(evolution:4163): evolution-mail-WARNING **: Failed to refresh folders: Cannot get folder `/home/janek/.gconf/desktop/gnome/peripherals': not a maildir directory.
(evolution:4163): evolution-mail-WARNING **: Failed to refresh folders: Cannot get folder `/home/janek/.gconf/desktop/gnome/peripherals/keyboard': not a maildir directory.
(evolution:4163): evolution-mail-WARNING **: Failed to refresh folders: Cannot get folder `/home/janek/.gconf/desktop/gnome/peripherals/keyboard/kbd': not a maildir directory.
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-07-19 15:11:36 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 455158 ***