Bug 485976 – crash in Tasks: writing 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 485976 - crash in Tasks: writing an email


Summary:	crash in Tasks: writing an email


Status:	RESOLVED DUPLICATE of bug 458322

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-10-12 10:44 UTC by cs
Modified:	2007-10-15 09:22 UTC

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

Description cs 2007-10-12 10:44:25 UTC

Version: 2.10

What were you doing when the application crashed?
writing an email


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.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 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: 702889984 vsize: 702889984 resident: 80351232 share: 41517056 rss: 80351232 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192178965 rtime: 4529 utime: 4206 stime: 323 cutime:105 cstime: 22 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 46912496410768 (LWP 15249)]
[New Thread 1074006352 (LWP 15353)]
[New Thread 1115699536 (LWP 15351)]
[New Thread 1094719824 (LWP 15255)]
(no debugging symbols found)
0x0000003ccc20d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 169695

Thread 1 (Thread 46912496410768 (LWP 15249))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_utf8_offset_to_pointer
from /lib64/libglib-2.0.so.0
#4 ??
from /usr/lib64/libedataserverui-1.2.so.8
#5 ??
from /usr/lib64/libedataserverui-1.2.so.8
#6 ??
from /usr/lib64/libedataserverui-1.2.so.8
#7 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#8 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#9 ??
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit
from /lib64/libgobject-2.0.so.0
#12 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#17 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#18 ??
from /lib64/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#20 g_signal_emit
from /lib64/libgobject-2.0.so.0
#21 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#22 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#24 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#25 ??
from /lib64/libglib-2.0.so.0
#26 g_main_loop_run
from /lib64/libglib-2.0.so.0
#27 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#28 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (282 sec old) ---------------------
(evolution:15249): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:15249): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:15249): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:15249): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:15249): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:15249): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:15249): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:15249): camel-WARNING **: camel_exception_get_id called with NULL parameter.
--------------------------------------------------

Comment 1 Akhil Laddha 2007-10-15 09:22:19 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 458322 ***