GNOME Bugzilla – Bug 512957
crash in Volume Control:
Last modified: 2008-01-30 10:45:37 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 34910208 vsize: 34910208 resident: 13811712 share: 9764864 rss: 13811712 rss_rlim: 4294967295 CPU usage: start_time: 1201651233 rtime: 32 utime: 24 stime: 8 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6eea6b0 (LWP 2590)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187283
Thread 1 (Thread 0xb6eea6b0 (LWP 2590))
----------- .xsession-errors (11 sec old) --------------------- (epiphany-browser:2576): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany-browser:2576): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany-browser:2576): libgnomevfs-WARNING **: Failed to create service browser: Bad state ** (gnome-cups-icon:2521): WARNING **: No se pudo iniciar el icono de la bandeja del sistema porque no se pudo contactar con el servidor CUPS. (epiphany-browser:2576): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany-browser:2576): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed --------------------------------------------------
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 512924 ***