Bug 456429 – crash in Calendar: update

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 456429 - crash in Calendar: update


Summary:	crash in Calendar: update


Status:	RESOLVED DUPLICATE of bug 433922

Product:	evolution
Classification:	Applications
Component:	Calendar
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-12 23:52 UTC by guanenliang
Modified:	2007-07-17 19:09 UTC

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

Description guanenliang 2007-07-12 23:52:26 UTC

What were you doing when the application crashed?
update


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.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: 136101888 vsize: 136101888 resident: 47091712 share: 32075776 rss: 47091712 rss_rlim: 4294967295
CPU usage: start_time: 1184284204 rtime: 435 utime: 371 stime: 64 cutime:42 cstime: 12 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 -1208670496 (LWP 3299)]
[New Thread -1291453552 (LWP 3419)]
[New Thread -1280963696 (LWP 3418)]
[New Thread -1280672880 (LWP 3353)]
[New Thread -1230058608 (LWP 3324)]
(no debugging symbols found)
0x0051c402 in __kernel_vsyscall ()

+ Trace 147661

Thread 1 (Thread -1208670496 (LWP 3299))

#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



----------- .xsession-errors (236 sec old) ---------------------
(gedit:3053): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
bad image index
(gedit:3053): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
bad image index
(gedit:3053): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
bad image index
(gedit:3053): Gtk-WARNING **: Icon cach
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Tobias Mueller 2007-07-17 19:09:53 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 ***