GNOME Bugzilla – Bug 520184
crash in Volume Control:
Last modified: 2008-03-04 21:00:10 UTC
Version: 2.18.0 What were you doing when the application crashed? 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: 106459136 vsize: 106459136 resident: 16195584 share: 12390400 rss: 16195584 rss_rlim: 18446744073709551615 CPU usage: start_time: 1204589766 rtime: 87 utime: 77 stime: 10 cutime:8 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) 0x00002ac80830ead5 in waitpid () from /lib/libpthread.so.0
+ Trace 191199
----------- .xsession-errors --------------------- MNG error 11: Function is invalid at this point; chunk vpAg; subcode 0:0 MNG error 11: Function is invalid at this point; chunk vpAg; subcode 0:0 MNG error 11: Function is invalid at this point; chunk vpAg; subcode 0:0 MNG error 11: Function is invalid at this point; chunk vpAg; subcode 0:0 MNG error 11: Function is invalid at this point; chunk vpAg; subcode 0:0 MNG error 11: Function is invalid at this point; chunk vpAg; subcode 0:0 MNG error 11: Function is invalid at this point; chunk vpAg; subcode 0:0 MNG error 11: Function is invalid at this point; chunk vpAg; subcode 0:0 (gnome-volume-control:10232): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed 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 --------------------------------------------------
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 ***