Bug 450025 – crash in Tasks: closing folder

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 450025 - crash in Tasks: closing folder


Summary:	crash in Tasks: closing folder


Status:	RESOLVED DUPLICATE of bug 432796

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-22 11:28 UTC by qa
Modified:	2007-06-29 16:41 UTC

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

Description qa 2007-06-22 11:28:47 UTC

What were you doing when the application crashed?
closing folder


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 117768192 vsize: 117768192 resident: 36962304 share: 20381696 rss: 36962304 rss_rlim: 4294967295
CPU usage: start_time: 1182510888 rtime: 656 utime: 621 stime: 35 cutime:0 cstime: 2 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 -1208215840 (LWP 3854)]
[New Thread -1314944112 (LWP 3932)]
[New Thread -1282794608 (LWP 3881)]
(no debugging symbols found)
0x001a4402 in __kernel_vsyscall ()

+ Trace 142868

Thread 2 (Thread -1314944112 (LWP 3932))

#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 (100 sec old) ---------------------
(evolution:3854): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(evolution:3854): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(evolution:3854): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(evolution:3854): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(evolution:3854): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3854): 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?)
(evolution:3854): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9f6d498'
(evolution:3854): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9f6d5b8'
--------------------------------------------------

Comment 1 palfrey 2007-06-29 16:41:39 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 432796 ***