Bug 459254 – crash in Tasks: setting up my email in E...

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 459254 - crash in Tasks: setting up my email in E...


Summary:	crash in Tasks: setting up my email in E...


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-07-22 09:12 UTC by chablis
Modified:	2007-07-22 09:56 UTC

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

Description chablis 2007-07-22 09:12:06 UTC

Version: 2.10

What were you doing when the application crashed?
setting up my email in Evolution


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

Memory status: size: 154796032 vsize: 154796032 resident: 57913344 share: 45867008 rss: 57913344 rss_rlim: 4294967295
CPU usage: start_time: 1185094027 rtime: 806 utime: 726 stime: 80 cutime:3 cstime: 13 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 -1209014560 (LWP 2954)]
[New Thread -1315857520 (LWP 3067)]
[New Thread -1271305328 (LWP 3064)]
(no debugging symbols found)
0x0058b402 in __kernel_vsyscall ()

+ Trace 149761

Thread 1 (Thread -1209014560 (LWP 2954))

#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 (71 sec old) ---------------------
(evolution:2954): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(evolution:2954): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:2954): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:2954): 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?)
BBDB spinning up...
(evolution:2954): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8d77008'
(evolution:2954): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8d77128'
--------------------------------------------------

Comment 1 palfrey 2007-07-22 09:56:20 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 ***