GNOME Bugzilla – Bug 456377
crash in Tasks: trying to configure evol...
Last modified: 2007-08-01 13:22:45 UTC
What were you doing when the application crashed? trying to configure evolution to connect to my pop mail server. 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 129564672 vsize: 129564672 resident: 50540544 share: 21729280 rss: 50540544 rss_rlim: 4294967295 CPU usage: start_time: 1184284227 rtime: 8711 utime: 8151 stime: 560 cutime:2 cstime: 6 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 -1209043232 (LWP 3518)] [New Thread -1291445360 (LWP 5250)] [New Thread -1280955504 (LWP 5248)] [New Thread -1334797424 (LWP 3601)] (no debugging symbols found) 0x007e5402 in __kernel_vsyscall ()
+ Trace 147618
Thread 1 (Thread -1209043232 (LWP 3518))
----------- .xsession-errors (84 sec old) --------------------- Configured devices: lo eth0 Currently active devices: lo eth0 network Configured devices: lo eth0 Currently active devices: lo eth0 (evolution:3518): 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:3518): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x94bd000' (evolution:3518): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x94bd120' --------------------------------------------------
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 455180 ***