GNOME Bugzilla – Bug 504781
crash in Volume Control: Trying to get sound from...
Last modified: 2008-01-19 14:01:29 UTC
Version: 2.18.0 What were you doing when the application crashed? Trying to get sound from my Audigy 2 with NO luck. Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.18.1 2007-05-04 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-sabayon #1 SMP Mon Sep 3 00:33:06 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Human-Graphite Icon Theme: Tango Memory status: size: 111210496 vsize: 111210496 resident: 21143552 share: 12673024 rss: 21143552 rss_rlim: 18446744073709551615 CPU usage: start_time: 1198177585 rtime: 181 utime: 163 stime: 18 cutime:8 cstime: 2 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) 0x00002af9b5869ad5 in waitpid () from /lib/libpthread.so.0
+ Trace 182495
----------- .xsession-errors --------------------- QPainter::killPStack: non-empty save/restore stack when end() was called QPainter::killPStack: non-empty save/restore stack when end() was called X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3404bb0 (gnome-volume-control:10298): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed QPainter::killPStack: non-empty save/restore stack when end() was called X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3400003 QPainter::killPStack: non-empty save/restore stack when end() was called QPainter::killPStack: non-empty save/restore stack when end() was called --------------------------------------------------
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 ***