GNOME Bugzilla – Bug 482457
crash in Volume Control: I was not getting 4.1 ou...
Last modified: 2007-10-03 09:59:27 UTC
Version: 2.18.0 What were you doing when the application crashed? I was not getting 4.1 output inmy speaker. So I was trying for any options in the volume controller Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 39067648 vsize: 39067648 resident: 12365824 share: 9154560 rss: 12365824 rss_rlim: 4294967295 CPU usage: start_time: 1191302739 rtime: 232 utime: 218 stime: 14 cutime:2 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 -1208796944 (LWP 3203)] (no debugging symbols found) 0x00213402 in __kernel_vsyscall ()
+ Trace 167027
Thread 1 (Thread -1208796944 (LWP 3203))
----------- .xsession-errors (366 sec old) --------------------- localuser:vinayak being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2771 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a00086 (Google Des) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
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 471133 ***