GNOME Bugzilla – Bug 469125
crash in Tasks:
Last modified: 2007-10-02 03:19:21 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.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: OSX Memory status: size: 132382720 vsize: 132382720 resident: 51277824 share: 36982784 rss: 51277824 rss_rlim: 4294967295 CPU usage: start_time: 1187763416 rtime: 768 utime: 680 stime: 88 cutime:4 cstime: 20 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208514848 (LWP 3385)] [New Thread -1290765424 (LWP 3430)] [New Thread -1258902640 (LWP 3426)] 0x0030c402 in __kernel_vsyscall ()
+ Trace 157054
Thread 1 (Thread -1208514848 (LWP 3385))
----------- .xsession-errors (178 sec old) --------------------- xendomains Checking for xendomains:[FAILED] xendomains Checking for xendomains:[FAILED] yum-updatesd yum-updatesd (pid 2265) is running... yum-updatesd yum-updatesd (pid 2265) is running... (evolution:3385): 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:3385): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x907c008' (evolution:3385): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x907c128' --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
(In reply to comment #1) > Thanks for taking the time to report this bug. > Unfortunately, that stack trace is missing some elements that will help a lot > to solve the problem, so it will be hard for the developers to fix that crash. > Can you get us a stack trace with debugging symbols? Please see > http://live.gnome.org/GettingTraces for more information on how to do so and > reopen this bug or report a new one. Thanks in advance! > Could you tell me which debuginfo packages I need to install? I installed several packages earlier today, thinking I had the right ones. Thanks.
atleast evolution, evolution-data-server, gtkhtml, gtk, glib,
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 438139 ***