GNOME Bugzilla – Bug 578881
crash in Volume Control: Removing volume control ...
Last modified: 2009-04-14 13:03:43 UTC
What were you doing when the application crashed? Removing volume control from panel Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.24.3 2009-03-28 (Gentoo) BugBuddy Version: 2.24.2 System: Linux 2.6.26-tuxonice #4 SMP Sun Feb 22 21:09:09 EET 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Gion Memory status: size: 53137408 vsize: 53137408 resident: 15974400 share: 12443648 rss: 15974400 rss_rlim: 18446744073709551615 CPU usage: start_time: 1239657585 rtime: 21 utime: 16 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/mixer_applet2' [Thread debugging using libthread_db enabled] [New Thread 0xb69fca80 (LWP 11572)] 0xb7f49424 in __kernel_vsyscall ()
+ Trace 214438
Thread 1 (Thread 0xb69fca80 (LWP 11572))
----------- .xsession-errors (17 sec old) --------------------- UTILS: mydebug.id = 239423 PREFERENCES: imported debug.id = 239423 STARTUP: main(); loading preferences STARTUP: main(); importing version STAPORTAGELIB: portage version = 2.2_rc28 !!! pordbapi.getfetchlist() is deprecated, use getFetchMap() instead. Bonobo-Activation-Message: Make registration id from 'OAFIID:GNOME_Terminal_Factory' ':0.0' Bonobo-Activation-Message: Registering iid 'OAFIID:GNOME_Terminal_Factory' with display ':0.0' Bonobo-Activation-Message: About to register 'OAFIID:GNOME_Terminal_Factory': 0x980e198 Bonobo-Activation-Message: Registration environment for 'DISPLAY' = ':0.0' Bonobo-Activation-Message: registration of 'OAFIID:GNOME_Terminal_Factory' returns (success) Bonobo-Activation-Message: Successfully registered `OAFIID:GNOME_Terminal_Factory' (gnome-terminal:29605): Vte-WARNING **: DECSET/DECRESET mode 1034 not recognized, ignoring. --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 546735 ***