Bug 396918 – crash in Evolution:

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 396918 - crash in Evolution:


Summary:	crash in Evolution:


Status:	RESOLVED DUPLICATE of bug 373312

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-15 16:20 UTC by stefano-grassi
Modified:	2007-01-16 15:27 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description stefano-grassi 2007-01-15 16:20:04 UTC

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 217354240 vsize: 0 resident: 217354240 share: 0 rss: 27017216 rss_rlim: 0
CPU usage: start_time: 1168877976 rtime: 0 utime: 196 stime: 0 cutime:185 cstime: 0 timeout: 11 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233443152 (LWP 5853)]
[New Thread -1302705248 (LWP 5875)]
[New Thread -1300440160 (LWP 5874)]
[New Thread -1378657376 (LWP 5872)]
[New Thread -1387050080 (LWP 5870)]
[New Thread -1369871456 (LWP 5869)]
[New Thread -1361478752 (LWP 5866)]
[New Thread -1327907936 (LWP 5862)]
[New Thread -1319515232 (LWP 5861)]
[New Thread -1311122528 (LWP 5860)]
[New Thread -1285919840 (LWP 5857)]
[New Thread -1277527136 (LWP 5856)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 102419

Thread 1 (Thread -1233443152 (LWP 5853))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 segv_redirect
at main.c line 426
#4 <signal handler called>
#5 icalparser_string_line_generator
at icalparser.c line 1075
#6 icalparser_get_line
at icalparser.c line 473
#7 icalparser_parse
at icalparser.c line 585
#8 icalparser_parse_string
at icalparser.c line 1118
#9 format_itip_object
at itip-formatter.c line 1224
#10 efh_object_requested
at em-format-html.c line 601
#11 html_g_cclosure_marshal_BOOLEAN__OBJECT
from /usr/lib/libgtkhtml-3.8.so.15
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 gtk_html_get_top_html
from /usr/lib/libgtkhtml-3.8.so.15
#17 html_g_cclosure_marshal_BOOLEAN__OBJECT
from /usr/lib/libgtkhtml-3.8.so.15
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 html_engine_add_object_with_id
from /usr/lib/libgtkhtml-3.8.so.15
#23 html_engine_add_object_with_id
from /usr/lib/libgtkhtml-3.8.so.15
#24 html_engine_update_focus_if_necessary
from /usr/lib/libgtkhtml-3.8.so.15
#25 html_engine_flush
from /usr/lib/libgtkhtml-3.8.so.15
#26 gtk_html_flush
from /usr/lib/libgtkhtml-3.8.so.15
#27 emhs_sync_flush
at em-html-stream.c line 127
#28 emcs_gui_received
at em-sync-stream.c line 161
#29 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#30 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#31 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#32 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#33 bonobo_main
from /usr/lib/libbonobo-2.so.0
#34 main
at main.c line 615
#0 __kernel_vsyscall

Comment 1 Kjartan Maraas 2007-01-16 15:12:40 UTC

Looks like a sane trace.

Comment 2 palfrey 2007-01-16 15:27:15 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 373312 ***