GNOME Bugzilla – Bug 560173
crash in Volume Control: Changed the GTK theme.
Last modified: 2008-11-10 16:32:24 UTC
What were you doing when the application crashed? Changed the GTK theme. Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.22.3 2008-08-29 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.27-gentoo #2 SMP Wed Oct 22 00:57:43 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: SnowIsh-1.0_PNG Memory status: size: 66646016 vsize: 66646016 resident: 29147136 share: 13643776 rss: 29147136 rss_rlim: 4294967295 CPU usage: start_time: 1226269246 rtime: 1682 utime: 1263 stime: 419 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/mixer_applet2' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb5d36700 (LWP 13216)] [New Thread 0xb4c19b90 (LWP 13220)] 0xb7efd424 in __kernel_vsyscall ()
+ Trace 209582
Thread 1 (Thread 0xb5d36700 (LWP 13216))
----------- .xsession-errors (24318 sec old) --------------------- Öffne Videofilter: [scale] VDec: Verwende BGR 15-bit als Ausgabefarbraum (Nummer 2). Film-Aspekt ist undefiniert - keine Vorskalierung durchgeführt. SwScaler: reducing / aligning filtersize 1 -> 4 SwScaler: reducing / aligning filtersize 1 -> 4 SwScaler: reducing / aligning filtersize 1 -> 1 SwScaler: reducing / aligning filtersize 9 -> 8 [swscaler @ 0x89ae620]BICUBIC scaler, from rgb555 to yuv420p using MMX2 [swscaler @ 0x89ae620]using 4-tap MMX scaler for horizontal luminance scaling [swscaler @ 0x89ae620]using 4-tap MMX scaler for horizontal chrominance scaling [swscaler @ 0x89ae620]using 1-tap MMX "scaler" for vertical scaling (YV12 like) [swscaler @ 0x89ae620]800x600 -> 800x600 VO: [xv] 800x600 => 800x600 Planar YV12 A: 0.0 V: 0.0 A-V: 0.048 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 0.1 V: 0.5 A-V: -0.364 ct: 0.000 2/ 2 ??% ??% ??,?% 0 0 A: 0.2 V: 0.5 A-V: -0.278 ct: 0.0 ...Too much output, ignoring rest... --------------------------------------------------
*** This bug has been marked as a duplicate of 364396 ***