Bug 484831 – crash in Tasks:

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 484831 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 469574

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-10-08 19:36 UTC by mferris
Modified:	2007-10-09 19:31 UTC

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

Description mferris 2007-10-08 19:36:18 UTC

Version: 2.10

What were you doing when the application crashed?



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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 372404224 vsize: 372404224 resident: 287956992 share: 44396544 rss: 287956992 rss_rlim: 4294967295
CPU usage: start_time: 1191850354 rtime: 12910 utime: 12090 stime: 820 cutime:5 cstime: 17 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 -1208592672 (LWP 4348)]
[New Thread -1304069232 (LWP 4416)]
[New Thread -1219953776 (LWP 4405)]
[New Thread -1231029360 (LWP 4353)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 168855

Thread 1 (Thread -1208592672 (LWP 4348))

#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 ??
from /usr/lib/libedataserverui-1.2.so.8
#9 ??
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 ??
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 g_signal_emit
from /lib/libgobject-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
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_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib/libgdk-x11-2.0.so.0
#27 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#28 ??
from /lib/libglib-2.0.so.0
#29 g_main_loop_run
from /lib/libglib-2.0.so.0
#30 bonobo_main
from /usr/lib/libbonobo-2.so.0
#31 main
#0 __kernel_vsyscall



----------- .xsession-errors (8 sec old) ---------------------
(evolution:4348): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xacdd6c0'
(evolution:4348): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xacdd7e0'
(evolution:4348): libebook-WARNING **: invalid escape, passing it through
(evolution:4348): libebook-WARNING **: invalid escape, passing it through
(evolution:4348): libebook-WARNING **: invalid escape, passing it through
(evolution:4348): libebook-WARNING **: invalid escape, passing it through
(evolution:4348): libebook-WARNING **: invalid escape, passing it through
(evolution:4348): libebook-WARNING **: invalid escape, passing it through
--------------------------------------------------

Comment 1 Susana 2007-10-09 19:31:34 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 469574 ***