Bug 459753 – crash in Tasks: Reading mail

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 459753 - crash in Tasks: Reading mail


Summary:	crash in Tasks: Reading mail


Status:	RESOLVED DUPLICATE of bug 433922

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-23 23:42 UTC by burker
Modified:	2007-07-29 18:27 UTC

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

Description burker 2007-07-23 23:42:37 UTC

Version: 2.10

What were you doing when the application crashed?
Reading mail


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.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 742309888 vsize: 742309888 resident: 101191680 share: 67104768 rss: 101191680 rss_rlim: 18446744073709551615
CPU usage: start_time: 1185221933 rtime: 3124 utime: 1165 stime: 1959 cutime:1 cstime: 7 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 46912496459920 (LWP 5272)]
[New Thread 1094719824 (LWP 6409)]
[New Thread 1126189392 (LWP 6408)]
[New Thread 1157925200 (LWP 5331)]
[New Thread 1115699536 (LWP 5312)]
(no debugging symbols found)
0x0000003f3260d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 150108

Thread 1 (Thread 46912496459920 (LWP 5272))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
from /lib64/libglib-2.0.so.0
#4 ??
from /lib64/libglib-2.0.so.0
#5 ??
from /lib64/libglib-2.0.so.0
#6 g_slice_free_chain_with_offset
from /lib64/libglib-2.0.so.0
#7 pango_attr_list_unref
from /usr/lib64/libpango-1.0.so.0
#8 ??
from /usr/lib64/libgtkhtml-3.14.so.19
#9 ??
from /usr/lib64/libgtkhtml-3.14.so.19
#10 ??
from /usr/lib64/libgtkhtml-3.14.so.19
#11 ??
from /usr/lib64/libgtkhtml-3.14.so.19
#12 html_engine_parse
from /usr/lib64/libgtkhtml-3.14.so.19
#13 gtk_html_begin_full
from /usr/lib64/libgtkhtml-3.14.so.19
#14 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#15 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#16 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#17 ??
from /lib64/libglib-2.0.so.0
#18 g_main_loop_run
from /lib64/libglib-2.0.so.0
#19 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#20 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Susana 2007-07-29 18:27:07 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 433922 ***