GNOME Bugzilla – Bug 508280
crash in Volume Control: closing it
Last modified: 2008-01-19 14:02:50 UTC
Version: 2.18.0 What were you doing when the application crashed? closing it Distribution: Debian 4.0 Gnome Release: 2.18.1 2007-04-27 (gnuLinEx) BugBuddy Version: 2.18.1 System: Linux 2.6.21.3 #1 Wed Jun 6 12:01:24 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Flat-Blue Memory status: size: 21430272 vsize: 21430272 resident: 12685312 share: 9584640 rss: 12685312 rss_rlim: 4294967295 CPU usage: start_time: 1199881418 rtime: 103 utime: 87 stime: 16 cutime:3 cstime: 1 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/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225279264 (LWP 8347)] (no debugging symbols found) 0xb73e320e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 184660
Thread 1 (Thread -1225279264 (LWP 8347))
----------- .xsession-errors (422338 sec old) --------------------- /usr/bin/compiz.real (core) - Warn: pixmap 0x2003e6e can't be bound to texture /usr/bin/compiz.real (core) - Info: Couldn't bind redirected window 0x1 to texture /usr/bin/compiz.real (core) - Warn: pixmap 0x2003e6e can't be bound to texture /usr/bin/compiz.real (core) - Info: Couldn't bind redirected window 0x1 to texture /usr/bin/compiz.real (core) - Warn: pixmap 0x2003e6e can't be bound to texture /usr/bin/compiz.real (core) - Info: Couldn't bind redirected window 0x1 to texture /usr/bin/compiz.real (core) - Warn: pixmap 0x2003e6e can't be bound to texture /usr/bin/compiz.real (core) - Info: Couldn't bind redirected window 0x1 to texture ...Too much output, ignoring rest... --------------------------------------------------
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 ***