Bug 504126 – crash in Tasks: Sending an email.

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 504126 - crash in Tasks: Sending an email.


Summary:	crash in Tasks: Sending an email.


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-17 21:23 UTC by indika
Modified:	2007-12-17 22:32 UTC

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

Description indika 2007-12-17 21:23:30 UTC

Version: 2.10

What were you doing when the application crashed?
Sending an email.


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.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 179228672 vsize: 179228672 resident: 67117056 share: 25047040 rss: 67117056 rss_rlim: 4294967295
CPU usage: start_time: 1197912801 rtime: 11067 utime: 10249 stime: 818 cutime:4227 cstime: 262 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 -1208367392 (LWP 15182)]
[New Thread -1331283056 (LWP 18096)]
[New Thread -1244664944 (LWP 15216)]
[New Thread -1278186608 (LWP 15215)]
[New Thread -1234175088 (LWP 15202)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 182162

Thread 2 (Thread -1331283056 (LWP 18096))

#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 (13307 sec old) ---------------------
(evolution:15182): libebook-CRITICAL **: e_contact_set: assertion `field_id >= 1 && field_id <= E_CONTACT_FIELD_LAST' failed
(evolution:15182): GLib-GObject-WARNING **: value "TRUE" of type `gboolean' is invalid or out of range for property `wants-html' of type `gboolean'
(evolution:15182): libebook-CRITICAL **: e_contact_set: assertion `field_id >= 1 && field_id <= E_CONTACT_FIELD_LAST' failed
(evolution:15182): libebook-CRITICAL **: e_contact_set: assertion `field_id >= 1 && field_id <= E_CONTACT_FIELD_LAST' failed
(evolution:15182): libebook-CRITICAL **: e_contact_set: assertion `field_id >= 1 && field_id <= E_CONTACT_FIELD_LAST' failed
(evolution:15182): GLib-GObject-WARNING **: value "TRUE" of type `gboolean' is invalid or out of range for property `wants-html' of type `gboolean'
(evolution:15182): libebook-CRITICAL **: e_contact_set: assertion `field_id >= 1 && field_id <= E_CONTACT_FIELD_LAST' failed
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Tobias Mueller 2007-12-17 22:32:09 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 ***