Bug 459890 – crash in Tasks: I was only writing a new...

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 459890 - crash in Tasks: I was only writing a new...


Summary:	crash in Tasks: I was only writing a new...


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-24 13:04 UTC by chopsse
Modified:	2007-07-28 13:03 UTC

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

Description chopsse 2007-07-24 13:04:50 UTC

What were you doing when the application crashed?
I was only writing a new message


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 326709248 vsize: 326709248 resident: 64950272 share: 27303936 rss: 64950272 rss_rlim: 4294967295
CPU usage: start_time: 1185258381 rtime: 12993 utime: 12210 stime: 783 cutime:4 cstime: 8 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 -1208453408 (LWP 3339)]
[New Thread -1312822384 (LWP 3464)]
[New Thread -1323312240 (LWP 3390)]
[New Thread -1302332528 (LWP 3388)]
[New Thread -1210553456 (LWP 3385)]
(no debugging symbols found)
0x004b3402 in __kernel_vsyscall ()

+ Trace 150216

Thread 1 (Thread -1208453408 (LWP 3339))

#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 (155 sec old) ---------------------
Decreasing itip formatter search count to 2
Decreasing itip formatter search count to 1
Decreasing itip formatter search count to 0
Increasing itip formatter search count to 1
Increasing itip formatter search count to 2
Increasing itip formatter search count to 3
Decreasing itip formatter search count to 2
Decreasing itip formatter search count to 1
Decreasing itip formatter search count to 0
Increasing itip formatter search count to 1
Increasing itip formatter search count to 2
Increasing itip formatter search count to 3
Decreasing itip formatter search count to 2
Decreasing itip formatter search cou
(evolution:3339): libecal-WARNING **: e-cal.c:317: Unexpected response
--------------------------------------------------

Comment 1 Iestyn Pryce 2007-07-28 13:03:36 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 ***