Bug 459626 – crash in Tasks: Creating a new mail mess...

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 459626 - crash in Tasks: Creating a new mail mess...


Summary:	crash in Tasks: Creating a new mail mess...


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-07-23 16:57 UTC by hoover
Modified:	2007-07-24 01:54 UTC

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

Description hoover 2007-07-23 16:57:55 UTC

Version: 2.10

What were you doing when the application crashed?
Creating a new mail message - entering names in the To: list.


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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 173592576 vsize: 173592576 resident: 84545536 share: 45559808 rss: 84545536 rss_rlim: 4294967295
CPU usage: start_time: 1185133909 rtime: 32730 utime: 30515 stime: 2215 cutime:9941 cstime: 844 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 -1208510752 (LWP 1781)]
[New Thread -1253950576 (LWP 1979)]
[New Thread -1289098352 (LWP 1920)]
[New Thread -1232577648 (LWP 1877)]
(no debugging symbols found)
0x00587402 in __kernel_vsyscall ()

+ Trace 150020

Thread 1 (Thread -1208510752 (LWP 1781))

#0 __kernel_vsyscall
#1 waitpid
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 (2676 sec old) ---------------------
(evolution:1781): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:1781): camel-WARNING **: camel_exception_get_id called with NULL parameter.
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
(gnome-terminal:3853): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
camel-Message: --
--------------------------------------------------

Comment 1 Susana 2007-07-24 01:54:55 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 458322 ***