GNOME Bugzilla – Bug 481509
crash in Volume Control: This bug are always when...
Last modified: 2007-10-03 09:58:29 UTC
Version: 2.18.0 What were you doing when the application crashed? This bug are always when I close the program. I use Mandriva Spring and kde. Program save parametrs. Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Free Icon Theme: gnome Memory status: size: 46493696 vsize: 46493696 resident: 13807616 share: 10407936 rss: 13807616 rss_rlim: 4294967295 CPU usage: start_time: 1191045900 rtime: 262 utime: 232 stime: 30 cutime:3 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/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226876032 (LWP 7881)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 166341
Thread 1 (Thread -1226876032 (LWP 7881))
----------- .xsession-errors (10 sec old) --------------------- Major opcode: 56 Minor opcode: 0 Resource id: 0x0 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 56 Minor opcode: 0 Resource id: 0x0 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 56 Minor opcode: 0 Resource id: 0x0 (gnome-volume-control:7673): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed (gnome-volume-control:7881): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed --------------------------------------------------
I try to run, turn on, turn off and close this program on IceWm and everything works good.
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 ***