Bug 477626 – crash in Calendar: return to Evolution from...

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 477626 - crash in Calendar: return to Evolution from...


Summary:	crash in Calendar: return to Evolution from...


Status:	RESOLVED DUPLICATE of bug 444866

Product:	evolution
Classification:	Applications
Component:	Calendar
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-09-17 01:36 UTC by shi5jin
Modified:	2007-10-02 03:42 UTC

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

Description shi5jin 2007-09-17 01:36:26 UTC

Version: 2.10

What were you doing when the application crashed?
return to Evolution from Eva, and click on a unread 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MacOS-X
Icon Theme: MacOS-X

Memory status: size: 151359488 vsize: 151359488 resident: 51412992 share: 37023744 rss: 51412992 rss_rlim: 4294967295
CPU usage: start_time: 1189992154 rtime: 492 utime: 453 stime: 39 cutime:41 cstime: 14 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 -1208207648 (LWP 12895)]
[New Thread -1239417968 (LWP 13068)]
[New Thread -1270887536 (LWP 13067)]
[New Thread -1302664304 (LWP 12924)]
[New Thread -1260397680 (LWP 12922)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 163434

Thread 1 (Thread -1208207648 (LWP 12895))

#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 ??
from /usr/lib/libgtkhtml-3.14.so.19
#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 (44 sec old) ---------------------
72:  1 ba c7 ba c7 21 c4 e3 
80: d0 c4 ba dc cf b8 b0 a1 
88: 21 d0 bb d0 bb c1 cb  a 
96: 20  0  9  0  0  0  0 86 
104:  2 cb ce cc e5  d 
----====== Normal Text Finished ======----
From Buddy -- DV (171261490)  : 呵呵!你心很细啊!谢谢了
 
send im reply
received new message
IM: seq: -1754586952 ----- msg seq: 22379
Unknow IM Type: 0x79
sender: 171261490, receiver: 165673362, sender IP: 255.255.255.255, sender port: 22
version:0x 100, command: 0x  17, sequence: 0x576b
after InPacket he
--------------------------------------------------

Comment 1 Tobias Mueller 2007-10-02 03:42:26 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 444866 ***