Bug 500810 – crash in Tasks:

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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 441638

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
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-12-01 05:10 UTC by Daye Liu
Modified:	2007-12-01 16:06 UTC

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

Description Daye Liu 2007-12-01 05:10:24 UTC

Version: 2.10

What were you doing when the application crashed?



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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 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: 135979008 vsize: 135979008 resident: 53383168 share: 34070528 rss: 53383168 rss_rlim: 4294967295
CPU usage: start_time: 1196475606 rtime: 1658 utime: 1291 stime: 367 cutime:112 cstime: 15 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 -1208973600 (LWP 3474)]
[New Thread -1311798384 (LWP 5013)]
[New Thread -1238373488 (LWP 5011)]
[New Thread -1226327152 (LWP 4941)]
[New Thread -1280328816 (LWP 3636)]
[New Thread -1301308528 (LWP 3630)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 180285

Thread 3 (Thread -1238373488 (LWP 5011))

#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 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#10 g_slist_free
from /lib/libglib-2.0.so.0
#11 g_strsplit
from /lib/libglib-2.0.so.0
#12 camel_uid_cache_new
from /usr/lib/libcamel-provider-1.2.so.10
#13 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#15 ??
from /lib/libglib-2.0.so.0
#16 ??
from /lib/libglib-2.0.so.0
#17 start_thread
from /lib/libpthread.so.0
#18 clone
from /lib/libc.so.6



----------- .xsession-errors ---------------------
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
(evolution:3474): 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:3474): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x90fe140'
(evolution:3474): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x90fe260'
(evolution:3474): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
--------------------------------------------------

Comment 1 Tobias Mueller 2007-12-01 16:06:12 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 441638 ***