Bug 478751 – crash in Tasks: I'd just hit return in a...

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 478751 - crash in Tasks: I'd just hit return in a...


Summary:	crash in Tasks: I'd just hit return in a...


Status:	RESOLVED DUPLICATE of bug 458322

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:	aklapper[fc7]

Depends on:
Blocks:

Reported:	2007-09-20 20:52 UTC by jconway
Modified:	2007-09-21 18:15 UTC

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

Description jconway 2007-09-20 20:52:33 UTC

Version: 2.10

What were you doing when the application crashed?
I'd just hit return in an empty "To:" field in a new email.


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 244649984 vsize: 244649984 resident: 98779136 share: 75911168 rss: 98779136 rss_rlim: 4294967295
CPU usage: start_time: 1190307782 rtime: 5878 utime: 5565 stime: 313 cutime:63 cstime: 24 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 -1208449312 (LWP 3354)]
[New Thread -1210549360 (LWP 3749)]
[New Thread -1280922736 (LWP 3383)]
[New Thread -1270432880 (LWP 3365)]
[New Thread -1221039216 (LWP 3364)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 164242

Thread 1 (Thread -1208449312 (LWP 3354))

#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 (939 sec old) ---------------------
xscreensaver: 10:45:46: 0: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 10:45:46: 0: for window 0x3a0196c (Terminal / Terminal)
tangram: unable to load font "-*-times-bold-r-normal-*-180-*", using "fixed"
tangram: unable to load font "-*-times-bold-r-normal-*-120-*", using "-*-times-bold-r-normal-*-180-*"
tangram: unable to load font "-*-times-bold-r-normal-*-180-*", using "fixed"
tangram: unable to load font "-*-times-bold-r-normal-*-80-*", using "-*-times-bold-r-normal-*-180-*"
tangram: unable to load font "-*-times-bold-r-normal-*-180-*", using "fixed"
xscreensaver-command: activating and locking.
xscreensaver-command: activating and locking.
xscreensaver-command: activating and locking.
xscreensaver: 13:35:50: -1: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 13:35:50: -1: for window 0x2015338 ((null) / (null))
--------------------------------------------------

Comment 1 Tobias Mueller 2007-09-21 18:15:33 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 ***