GNOME Bugzilla – Bug 476446
crash in Tasks: I have push on the butto...
Last modified: 2007-09-24 17:48:00 UTC
Version: 2.10 What were you doing when the application crashed? I have push on the button to receive my mail 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 106360832 vsize: 106360832 resident: 37150720 share: 29794304 rss: 37150720 rss_rlim: 4294967295 CPU usage: start_time: 1189662713 rtime: 94 utime: 83 stime: 11 cutime:2 cstime: 6 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 -1208551712 (LWP 2572)] [New Thread -1252332656 (LWP 2639)] [New Thread -1219998832 (LWP 2610)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 162540
Thread 1 (Thread -1208551712 (LWP 2572))
----------- .xsession-errors (8 sec old) --------------------- localuser:lepine being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2281 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:2572): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2572): 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 ***