Bug 447660 – 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 447660 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 444395

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-06-14 20:00 UTC by u.gabel-panfil
Modified:	2007-06-15 18:01 UTC

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

Description u.gabel-panfil 2007-06-14 20:00:19 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (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: 139116544 vsize: 139116544 resident: 57696256 share: 40218624 rss: 57696256 rss_rlim: 4294967295
CPU usage: start_time: 1181850792 rtime: 1247 utime: 1166 stime: 81 cutime:62 cstime: 23 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 -1208686880 (LWP 3049)]
[New Thread -1270629488 (LWP 3250)]
[New Thread -1228096624 (LWP 3188)]
[New Thread -1238586480 (LWP 3138)]
(no debugging symbols found)
0x00410402 in __kernel_vsyscall ()

+ Trace 141035

Thread 1 (Thread -1208686880 (LWP 3049))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libgobject-2.0.so.0
#6 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#7 g_param_spec_pool_list_owned
from /lib/libgobject-2.0.so.0
#8 ??
from /lib/libgobject-2.0.so.0
#9 ??
from /lib/libgobject-2.0.so.0
#10 g_type_class_unref
from /lib/libgobject-2.0.so.0
#11 g_type_free_instance
from /lib/libgobject-2.0.so.0
#12 g_object_unref
from /lib/libgobject-2.0.so.0
#13 ??
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#14 ??
from /usr/lib/libgnomevfs-2.so.0
#15 ??
#16 ??
#17 ??
#18 ??
from /usr/lib/libgnomevfs-2.so.0
#19 ??
#20 ??
from /lib/libpthread.so.0
#21 ??
#22 ??
from /usr/lib/libgnomevfs-2.so.0
#23 ??
#24 ??
#25 ??
#26 g_slice_alloc
from /lib/libglib-2.0.so.0
#0 __kernel_vsyscall



----------- .xsession-errors (38 sec old) ---------------------
BBDB spinning up...
(evolution:3049): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa5af008'
(evolution:3049): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa5af128'
(evolution:3049): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:3049): e-data-server-DEBUG: Loading categories from "/home/udo/.evolution/categories.xml"
(evolution:3049): e-data-server-DEBUG: Loaded 29 categories
(evolution:3049): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:3049): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa5af488'
(evolution:3049): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa5af5a8'
--------------------------------------------------

Comment 1 André Klapper 2007-06-15 18:01:13 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 444395 ***