GNOME Bugzilla – Bug 467392
crash in Tasks:
Last modified: 2007-09-24 19:04:31 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 130994176 vsize: 130994176 resident: 47575040 share: 39923712 rss: 47575040 rss_rlim: 4294967295 CPU usage: start_time: 1187285031 rtime: 69 utime: 60 stime: 9 cutime:1 cstime: 3 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 -1209108768 (LWP 3601)] [New Thread -1262642288 (LWP 3650)] [New Thread -1225188464 (LWP 3625)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 155723
Thread 1 (Thread -1209108768 (LWP 3601))
----------- .xsession-errors (36 sec old) --------------------- localuser:Johan being added to access control list /etc/profile.d/kver.sh: line 1: 2.6.22.1-41.fc6: command not found SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3377 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:3601): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3601): DEBUG: mailto URL program: evolution --------------------------------------------------
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!
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 364700 ***