Bug 461900 – crash in Tasks: opening 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 461900 - crash in Tasks: opening mail


Summary:	crash in Tasks: opening mail


Status:	RESOLVED DUPLICATE of bug 433922

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:	aklapper[fc7]

Duplicates:	464817 464897 465081 466116 469079 471868 (view as bug list)
Depends on:
Blocks:

Reported:	2007-07-30 18:21 UTC by hurstel
Modified:	2007-08-30 16:38 UTC

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

Description hurstel 2007-07-30 18:21:27 UTC

What were you doing when the application crashed?
opening mail


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 134688768 vsize: 134688768 resident: 32317440 share: 20226048 rss: 32317440 rss_rlim: 4294967295
CPU usage: start_time: 1185819313 rtime: 437 utime: 416 stime: 21 cutime:2 cstime: 5 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 -1209116960 (LWP 5126)]
[New Thread -1315427440 (LWP 5214)]
[New Thread -1262408816 (LWP 5213)]
[New Thread -1284510832 (LWP 5154)]
[New Thread -1230521456 (LWP 5148)]
(no debugging symbols found)
0x00648402 in __kernel_vsyscall ()

+ Trace 151666

Thread 1 (Thread -1209116960 (LWP 5126))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 pango_attr_list_unref
from /usr/lib/libpango-1.0.so.0
#11 ??
from /usr/lib/libgtkhtml-3.14.so.19
#12 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#13 ??
from /usr/lib/libgtkhtml-3.14.so.19
#14 ??
from /usr/lib/libgtkhtml-3.14.so.19
#15 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#16 ??
from /usr/lib/libgtkhtml-3.14.so.19
#17 ??
from /usr/lib/libgtkhtml-3.14.so.19
#18 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#19 ??
from /usr/lib/libgtkhtml-3.14.so.19
#20 ??
from /usr/lib/libgtkhtml-3.14.so.19
#21 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#22 html_engine_parse
from /usr/lib/libgtkhtml-3.14.so.19
#23 gtk_html_begin_full
from /usr/lib/libgtkhtml-3.14.so.19
#24 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#25 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#26 ??
from /lib/libglib-2.0.so.0
#27 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#28 ??
from /lib/libglib-2.0.so.0
#29 g_main_loop_run
from /lib/libglib-2.0.so.0
#30 bonobo_main
from /usr/lib/libbonobo-2.so.0
#31 main
#0 __kernel_vsyscall

Comment 1 palfrey 2007-08-09 16:30:52 UTC

*** Bug 464817 has been marked as a duplicate of this bug. ***

Comment 2 palfrey 2007-08-09 16:36:00 UTC

*** Bug 464897 has been marked as a duplicate of this bug. ***

Comment 3 palfrey 2007-08-09 16:37:52 UTC

*** Bug 465081 has been marked as a duplicate of this bug. ***

Comment 4 palfrey 2007-08-13 14:12:07 UTC

*** Bug 466116 has been marked as a duplicate of this bug. ***

Comment 5 palfrey 2007-08-22 13:22:06 UTC

*** Bug 469079 has been marked as a duplicate of this bug. ***

Comment 6 Tobias Mueller 2007-08-22 19:38:40 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 ***

Comment 7 palfrey 2007-08-30 16:38:25 UTC

*** Bug 471868 has been marked as a duplicate of this bug. ***