Bug 499663 – crash in Tasks: Forwarding e-mail

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 499663 - crash in Tasks: Forwarding e-mail


Summary:	crash in Tasks: Forwarding e-mail


Status:	RESOLVED DUPLICATE of bug 458322

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-11-26 03:57 UTC by cupp
Modified:	2007-11-26 06:11 UTC

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

Description cupp 2007-11-26 03:57:12 UTC

Version: 2.10

What were you doing when the application crashed?
Forwarding e-mail



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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 324489216 vsize: 324489216 resident: 128413696 share: 93806592 rss: 128413696 rss_rlim: 4294967295
CPU usage: start_time: 1196047864 rtime: 1586 utime: 1461 stime: 125 cutime:26 cstime: 13 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 -1208863008 (LWP 3614)]
[New Thread -1445880944 (LWP 4193)]
[New Thread -1288508528 (LWP 3748)]
[New Thread -1350591600 (LWP 3743)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 179649

Thread 1 (Thread -1208863008 (LWP 3614))

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



----------- .xsession-errors ---------------------
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
(evolution:3614): libebook-WARNING **: invalid escape, passing it through
(evolution:3614): libebook-WARNING **: invalid escape, passing it through
(evolution:3614): libebook-WARNING **: invalid escape, passing it through
--------------------------------------------------

Comment 1 Akhil Laddha 2007-11-26 06:11:59 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 458322 ***