GNOME Bugzilla – Bug 486567
crash in Volume Control: enabling volume
Last modified: 2007-10-14 19:19:42 UTC
Version: 2.18.0 What were you doing when the application crashed? enabling volume 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:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 278691840 vsize: 278691840 resident: 15007744 share: 10473472 rss: 15007744 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192371329 rtime: 106 utime: 96 stime: 10 cutime:1 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912499049968 (LWP 3994)] (no debugging symbols found) 0x000000345ee0d865 in waitpid () from /lib64/libpthread.so.0
+ Trace 170140
Thread 1 (Thread 46912499049968 (LWP 3994))
----------- .xsession-errors (261 sec old) --------------------- sdpd is stopped dc_client dc_client is stopped dc_client dc_client is stopped dc_client dc_client is stopped (gnome-terminal:3002): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (nautilus:2783): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is (gnome-terminal:3833): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-terminal:3833): Vte-WARNING **: No handler for control sequence `device-control-string' defined. --------------------------------------------------
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 ***