GNOME Bugzilla – Bug 425654
crash in Tasks:
Last modified: 2007-04-10 17:03:48 UTC
What were you doing when the application crashed? 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: 702726144 vsize: 702726144 resident: 53415936 share: 23056384 rss: 53415936 rss_rlim: 18446744073709551615 CPU usage: start_time: 1175551379 rtime: 1528 utime: 1330 stime: 198 cutime:8 cstime: 10 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 47221539640784 (LWP 3561)] [New Thread 1099184448 (LWP 3885)] [New Thread 1098918208 (LWP 3883)] 0x000000009dd1583f in ?? ()
+ Trace 124458
----------- .xsession-errors --------------------- (evolution:3561): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2af2a3190070(0x188d190) (evolution:3561): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2af2a3190070(0x188d190) (evolution:3561): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2af2a3190070(0x188d190) (evolution:3561): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 (evolution:3561): e-data-server-ui-WARNING **: Le fichier de clés n'a pas de clé « 2366D5283B29F20D » (evolution:3561): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Cannot access memory at address 0xd1cbf20 Cannot access memory at address 0xd1cbf20 --------------------------------------------------
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug. You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!
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 ***