GNOME Bugzilla – Bug 453925
crash in Tasks:
Last modified: 2007-07-23 16:31:03 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 301383680 vsize: 301383680 resident: 43597824 share: 12636160 rss: 43597824 rss_rlim: 4294967295 CPU usage: start_time: 1183547833 rtime: 26951 utime: 24819 stime: 2132 cutime:471 cstime: 239 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 -1208797472 (LWP 31760)] [New Thread -1434457200 (LWP 5090)] [New Thread -1297101936 (LWP 31812)] [New Thread -1276122224 (LWP 31788)] [New Thread -1252992112 (LWP 31785)] [New Thread -1263879280 (LWP 31783)] (no debugging symbols found) 0x007ee402 in __kernel_vsyscall ()
+ Trace 145873
Thread 1 (Thread -1208797472 (LWP 31760))
----------- .xsession-errors (181246 sec old) --------------------- loadscreen: parser counter = 221 started music 1954151179 showing title screen... 1954151180 Loading tips of day title screen returned result locale could not be determined; defaulting to system locale locale could not be determined; defaulting to system locale found valid cache at '/home/gcraciun/.wesnoth/cache/game.cfg-cache-v1.2.5-CAMPAIGN_DESERT-EASY' using it scenario: '2_HarshSands' has snapshot: yes setting replay to end... ...Too much output, ignoring rest... --------------------------------------------------
*** Bug 453927 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 410733 *** *** This bug has been marked as a duplicate of 410733 ***
*** Bug 459447 has been marked as a duplicate of this bug. ***