Bug 475312 – crash in Tasks: normal typing

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 475312 - crash in Tasks: normal typing


Summary:	crash in Tasks: normal typing


Status:	RESOLVED DUPLICATE of bug 440422

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-09-10 01:15 UTC by nprasad
Modified:	2007-09-21 18:52 UTC

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

Description nprasad 2007-09-10 01:15:57 UTC

Version: 2.10

What were you doing when the application crashed?
normal typing


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 152309760 vsize: 152309760 resident: 61526016 share: 42913792 rss: 61526016 rss_rlim: 4294967295
CPU usage: start_time: 1189384977 rtime: 1118 utime: 1015 stime: 103 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208576288 (LWP 8800)]
[New Thread -1284813936 (LWP 27166)]
[New Thread -1296110704 (LWP 27165)]
[New Thread -1237320816 (LWP 27163)]
[New Thread -1258693744 (LWP 8878)]
[New Thread -1235932272 (LWP 8824)]
[New Thread -1247810672 (LWP 8823)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 161669

Thread 1 (Thread -1208576288 (LWP 8800))

#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_item_free
from /usr/lib/libpango-1.0.so.0
#11 html_text_pango_info_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#12 ??
from /usr/lib/libgtkhtml-3.14.so.19
#13 ??
from /usr/lib/libgtkhtml-3.14.so.19
#14 html_object_split
from /usr/lib/libgtkhtml-3.14.so.19
#15 ??
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_engine_insert_text_with_extra_attributes
from /usr/lib/libgtkhtml-3.14.so.19
#19 html_engine_paste_text_with_extra_attributes
from /usr/lib/libgtkhtml-3.14.so.19
#20 html_engine_paste_text
from /usr/lib/libgtkhtml-3.14.so.19
#21 ??
from /usr/lib/libgtkhtml-3.14.so.19
#22 g_cclosure_marshal_VOID__STRING
from /lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /lib/libgobject-2.0.so.0
#24 ??
from /lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#26 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 g_cclosure_marshal_VOID__STRING
from /lib/libgobject-2.0.so.0
#29 g_closure_invoke
from /lib/libgobject-2.0.so.0
#30 ??
from /lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#32 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_im_context_filter_keypress
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib/libgtk-x11-2.0.so.0
#37 gtk_im_context_filter_keypress
from /usr/lib/libgtk-x11-2.0.so.0
#38 ??
from /usr/lib/libgtkhtml-3.14.so.19
#39 ??
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
from /lib/libgobject-2.0.so.0
#41 g_closure_invoke
from /lib/libgobject-2.0.so.0
#42 ??
from /lib/libgobject-2.0.so.0
#43 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#44 g_signal_emit
from /lib/libgobject-2.0.so.0
#45 ??
from /usr/lib/libgtk-x11-2.0.so.0
#46 gtk_window_propagate_key_event
from /usr/lib/libgtk-x11-2.0.so.0
#47 ??
from /usr/lib/libgtk-x11-2.0.so.0
#48 ??
from /usr/lib/libbonoboui-2.so.0
#49 ??
from /usr/lib/libgtk-x11-2.0.so.0
#50 ??
from /lib/libgobject-2.0.so.0
#51 g_closure_invoke
from /lib/libgobject-2.0.so.0
#52 ??
from /lib/libgobject-2.0.so.0
#53 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#54 g_signal_emit
from /lib/libgobject-2.0.so.0
#55 ??
from /usr/lib/libgtk-x11-2.0.so.0
#56 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#57 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#58 ??
from /usr/lib/libgdk-x11-2.0.so.0
#59 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#60 ??
from /lib/libglib-2.0.so.0
#61 g_main_loop_run
from /lib/libglib-2.0.so.0
#62 bonobo_main
from /usr/lib/libbonobo-2.so.0
#63 main
#0 __kernel_vsyscall



----------- .xsession-errors (7 sec old) ---------------------
warning: .dynamic section for "/usr/lib/libaspell.so.15" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libstdc++.so.6" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libbeagle.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Suman Manjunath 2007-09-15 17:52:55 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 440422 ***