Bug 514769 – crash in Tasks: editing an email

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 514769 - crash in Tasks: editing an email


Summary:	crash in Tasks: editing an email


Status:	RESOLVED DUPLICATE of bug 458670

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-06 14:51 UTC by cs
Modified:	2008-02-08 04:23 UTC

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

Description cs 2008-02-06 14:51:20 UTC

Version: 2.10

What were you doing when the application crashed?
editing an email


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 20:27:10 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 593391616 vsize: 593391616 resident: 52375552 share: 36052992 rss: 52375552 rss_rlim: 18446744073709551615
CPU usage: start_time: 1202309424 rtime: 151 utime: 135 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496452976 (LWP 3414)]
[New Thread 1115699536 (LWP 3440)]
[New Thread 1157925200 (LWP 3431)]
[New Thread 1094719824 (LWP 3419)]
(no debugging symbols found)
0x0000003ccc20d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 188297

Thread 1 (Thread 46912496452976 (LWP 3414))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_utf8_offset_to_pointer
from /lib64/libglib-2.0.so.0
#4 ??
from /usr/lib64/libedataserverui-1.2.so.8
#5 ??
from /usr/lib64/libedataserverui-1.2.so.8
#6 ??
from /usr/lib64/libedataserverui-1.2.so.8
#7 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#8 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#9 ??
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit
from /lib64/libgobject-2.0.so.0
#12 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#15 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#16 ??
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /lib64/libgobject-2.0.so.0
#19 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#20 ??
from /lib64/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#22 g_signal_emit
from /lib64/libgobject-2.0.so.0
#23 gtk_widget_grab_focus
from /usr/lib64/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib64/libgtkhtml-3.14.so.19
#25 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#26 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#27 ??
from /lib64/libgobject-2.0.so.0
#28 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#29 g_signal_emit
from /lib64/libgobject-2.0.so.0
#30 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#31 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#32 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#34 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#35 ??
from /lib64/libglib-2.0.so.0
#36 g_main_loop_run
from /lib64/libglib-2.0.so.0
#37 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#38 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (183529 sec old) ---------------------
5734] 11:52:21: TRACE: playing
5734] 11:52:21: TRACE: playing
5734] 11:52:21: TRACE: playing
5734] 11:52:21: TRACE: playing
5734] 11:52:21: TRACE: playing
5734] 11:52:21: TRACE: playing
5734] 11:52:21: TRACE: playing
5734] 11:52:21: TRACE: playing
5734] 11:52:21: TRACE: playing
5734] 11:52:22: TRACE: playing
5734] 11:52:22: TRACE: playing
5734] 11:52:22: TRACE: playing
5734] 11:52:22: TRACE: playing
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-08 04:23:36 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in the next software version. You may want to check for a software
upgrade.


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