GNOME Bugzilla – Bug 496015
crash in Volume Control: Exited the volume contro...
Last modified: 2007-12-19 14:03:56 UTC
Version: 2.18.0 What were you doing when the application crashed? Exited the volume controll Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 38522880 vsize: 38522880 resident: 13619200 share: 10039296 rss: 13619200 rss_rlim: 4294967295 CPU usage: start_time: 1194829063 rtime: 102 utime: 93 stime: 9 cutime:4 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) [Thread debugging using libthread_db enabled] [New Thread -1208608528 (LWP 3301)] (no debugging symbols found) 0x00d3f402 in __kernel_vsyscall ()
+ Trace 177117
Thread 1 (Thread -1208608528 (LWP 3301))
----------- .xsession-errors (20 sec old) --------------------- Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". ~ScimInputContextPlugin() ICE default IO error handler doing an exit(), pid = 3077, errno = 0 Message: fmt 5, channels: 2 --------------------------------------------------
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 ***