GNOME Bugzilla – Bug 461659
crash in Multimedia Systems Selector: probaba el sonido
Last modified: 2007-09-09 09:29:05 UTC
Version: 2.18.0 What were you doing when the application crashed? probaba el sonido 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.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:21:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Crux Memory status: size: 71405568 vsize: 71405568 resident: 15228928 share: 11022336 rss: 15228928 rss_rlim: 4294967295 CPU usage: start_time: 1185762966 rtime: 23 utime: 17 stime: 6 cutime:4 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gstreamer-properties' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208461600 (LWP 3926)] [New Thread -1221772400 (LWP 3937)] (no debugging symbols found) 0x00d08402 in __kernel_vsyscall ()
+ Trace 151495
Thread 1 (Thread -1208461600 (LWP 3926))
----------- .xsession-errors (1288 sec old) --------------------- QGArray::at: Absolute index 16923 out of range QGArray::at: Absolute index 16924 out of range QGArray::at: Absolute index 16925 out of range QGArray::at: Absolute index 16926 out of range QGArray::at: Absolute index 16927 out of range QGArray::at: Absolute index 16928 out of range QGArray::at: Absolute index 16929 out of range QGArray::at: Absolute index 16930 out of range QGArray::at: Absolute index 16931 out of range QGArray::at: Absolute index 16932 out of range QGArray::at: Absolute index 16933 out of range QGArray::at: Absolute index 16934 out of range QGArray::at: Absolute index 16935 out of range QGArray::at: Absolute index 16936 out of ran ...Too much output, ignoring rest... --------------------------------------------------
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 413801 ***