GNOME Bugzilla – Bug 424988
crash in Tasks: closing evo
Last modified: 2007-04-10 17:05:58 UTC
What were you doing when the application crashed? closing evo Distribution: Fedora release 6.92 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-0.27.rc5.mm3.fc7 #1 SMP Sat Mar 31 19:08:52 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10299903 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Bluecurve Memory status: size: 582422528 vsize: 582422528 resident: 46706688 share: 20389888 rss: 46706688 rss_rlim: 18446744073709551615 CPU usage: start_time: 1175375931 rtime: 687 utime: 610 stime: 77 cutime:3 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47514967105264 (LWP 9975)] [New Thread 1115969856 (LWP 9999)] 0x000000007060d83f in ?? ()
+ Trace 123922
----------- .xsession-errors (881 sec old) --------------------- (evolution:9643): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b6532aba070(0x14f58a0) (evolution:9643): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b6532aba070(0x14f58a0) (evolution:9643): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b6532aba070(0x14f58a0) (evolution:9643): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b6532aba070(0x14f58a0) (evolution:9643): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b6532aba070(0x14f58a0) (evolution:9643): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b6532aba070(0x14f58a0) (evolution:9643): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 (evolution:9643): e-data-server-ui-WARNING **: Le fichier de clés n'a pas de clé « 2366D5283B29F20D » (evolution:9643): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 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. Thanks in advance!
I already have a ton of debuginfo packages on the system, which one am I missing? # rpm -qa|grep debuginfo|sort alsa-lib-debuginfo-1.0.14-0.3.rc3.fc7 at-spi-debuginfo-1.18.0-2.fc7 bash-debuginfo-3.2-9.fc7 cairo-debuginfo-1.4.2-1.fc7 dbus-debuginfo-1.0.2-2.fc7 dbus-glib-debuginfo-0.71-4.fc7 evolution-data-server-debuginfo-1.10.0-4.fc7 evolution-debuginfo-2.10.0-5.fc7 GConf2-debuginfo-2.18.0.1-2.fc7 glib2-debuginfo-2.12.11-1.fc7 glibc-debuginfo-2.5.90-20 glib-debuginfo-1.2.10-26.fc7 gnome-keyring-debuginfo-0.8-1.fc7 gnome-pilot-debuginfo-2.0.15-3.fc7 gnome-spell-debuginfo-1.0.7-4.fc7 gnutls-debuginfo-1.4.5-1 gstreamer-debuginfo-0.10.12-1.fc7 gstreamer-plugins-base-debuginfo-0.10.12-2.fc7 gtk2-debuginfo-2.10.11-3.fc7 hal-debuginfo-0.5.9-0.git20070401.1.fc7 kernel-debuginfo-2.6.21-0.27.rc5.mm3.fc7 libart_lgpl-debuginfo-2.3.19-2.fc7 libbonobo-debuginfo-2.18.0-1.fc7 libbonoboui-debuginfo-2.18.0-1.fc7 libglade-debuginfo-0.17-19.fc6 libgnomecanvas-debuginfo-2.14.0-5.fc7 libgnome-debuginfo-2.18.0-2.fc7 libgnomeui-debuginfo-2.18.1-1.fc7 libICE-debuginfo-1.0.3-1.fc7 libnotify-debuginfo-0.4.4-2.fc7 libpng-debuginfo-1.2.16-1.fc7 libSM-debuginfo-1.0.2-1 libsoup-debuginfo-2.2.100-1.fc7 libX11-debuginfo-1.0.3-7.fc7 libxml-debuginfo-1.8.17-15.fc6 lm_sensors-debuginfo-2.10.3-0.2.20070225svn4333.fc7 NetworkManager-debuginfo-0.6.5-0.6.svn2474.fc7 nspr-debuginfo-4.6.6-1 nss-debuginfo-3.11.5-2.fc7 openldap-debuginfo-2.3.34-0.fc7 ORBit2-debuginfo-2.14.7-2.fc7 ORBit-debuginfo-0.5.17-20.fc7 pango-debuginfo-1.16.1-1.fc7 perl-debuginfo-5.8.8-15.fc7 pilot-link-debuginfo-0.12.1-5.fc7 scrollkeeper-debuginfo-0.3.14-10.fc7 spamassassin-debuginfo-3.2.0-0.2.pre2.fc7 totem-debuginfo-2.18.0-1.fc7 zlib-debuginfo-1.2.3-10.fc7
Given that stacktrace, it's hard to tell. If you can reproduce it while running Evolution under gdb (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details about how to do this), that might help getting a better trace if you've already got debug packages installed.
Starting program: /usr/bin/evolution GTK Accessibility Module initialized Bonobo accessibility support initialized CalDAV Eplugin starting up ... (evolution:4894): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution:4894): e-utils-WARNING **: Plugin 'Greffon de pourriel Spamassassin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' 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:4894): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 [New LWP 4917] [LWP 4917 exited] camel-Message: -- [New LWP 4894] Program received signal SIGSEGV, Segmentation fault. 0x00000000f2b8b490 in ?? () (gdb) * Undefined command: "". Try "help". (gdb) Undefined command: "". Try "help". (gdb) thread apply all bt
+ Trace 124467
Thread 2 (LWP 4894)
Given the state of the stack, I would suggest running it inside valgrind
Created attachment 86018 [details] First valgring log Ok, here is my first valgrind attempt. Evo didn't crash this time so it's probably insufficient but: — may there are some hints in there? — can you confirm I'm doing the right thing? If this kind of log is useful I'll retry it till I capture a crash
Yes this is the kind of log we need, but I don't see much useful things in this one. A log when evolution crashes should be more interesting. Thanks for your help.
Nothing I tried (valgrind,gdb,debuginfo packages) produced a good trace with this package Fortunately today the Fedora Devel package was updated and it did produce a good trace 5 minutes later, so I'm going to close this bug as duplicate. *** This bug has been marked as a duplicate of 428288 ***