GNOME Bugzilla – Bug 426369
crash in Tasks: closing evo
Last modified: 2007-04-10 17:05:31 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.28.rc5.mm4.fc7 #1 SMP Tue Apr 3 13:59:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10299903 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 652943360 vsize: 652943360 resident: 47898624 share: 20619264 rss: 47898624 rss_rlim: 18446744073709551615 CPU usage: start_time: 1175720268 rtime: 951 utime: 859 stime: 92 cutime:16 cstime: 13 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 47623203762304 (LWP 20684)] [New Thread 1099184448 (LWP 20795)] 0x000000009aa0d83f in ?? ()
+ Trace 125045
----------- .xsession-errors --------------------- CalDAV Eplugin starting up ... (evolution:20684): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution:20684): 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:20684): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 camel-Message: -- GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Cannot access memory at address 0x882f6050 Cannot access memory at address 0x882f6050 --------------------------------------------------
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!
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 ***