GNOME Bugzilla – Bug 502469
crash in Volume Control:
Last modified: 2007-12-17 12:51:18 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: 111411200 vsize: 111411200 resident: 21344256 share: 12963840 rss: 21344256 rss_rlim: 18446744073709551615 CPU usage: start_time: 1197113847 rtime: 202 utime: 183 stime: 19 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) 0x00002b4f80187ad5 in waitpid () from /lib/libpthread.so.0
+ Trace 181212
----------- .xsession-errors --------------------- Resource id: 0x2c01fb4 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c01fb4 (gnome-volume-control:10197): 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: 0x3600003 (emerald:10090): Wnck-WARNING **: Unhandled action type (nil) (emerald:10090): Wnck-WARNING **: Unhandled action type (nil) --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!