GNOME Bugzilla – Bug 494147
crash in Volume Control: Estaba intentando abrir ...
Last modified: 2008-01-19 19:27:59 UTC
Version: 2.18.0 What were you doing when the application crashed? Estaba intentando abrir el control de volumen desde gnome, se quedo esperando respuesta y se colgo, luego de eso me entrego el error. 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 27074560 vsize: 27074560 resident: 11792384 share: 8978432 rss: 11792384 rss_rlim: 4294967295 CPU usage: start_time: 1194355949 rtime: 21 utime: 18 stime: 3 cutime:4 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (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 -1208883488 (LWP 7359)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175714
Thread 1 (Thread -1208883488 (LWP 7359))
----------- .xsession-errors (2955 sec old) --------------------- (system-config-language:2667): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (system-config-language:2667): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (system-config-language:2667): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (system-config-language:2667): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid ...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 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 441641 ***