GNOME Bugzilla – Bug 513169
crash in Volume Control: I rebooted my laptop, an...
Last modified: 2008-01-30 18:08:40 UTC
What were you doing when the application crashed? I rebooted my laptop, and for some reason the application stopped working. I wasn't doing anything special. Regards, Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: Lush Memory status: size: 34615296 vsize: 34615296 resident: 13090816 share: 9867264 rss: 13090816 rss_rlim: 4294967295 CPU usage: start_time: 1201708750 rtime: 28 utime: 22 stime: 6 cutime:3 cstime: 0 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 0xb6e7a6b0 (LWP 4733)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187410
Thread 1 (Thread 0xb6e7a6b0 (LWP 4733))
----------- .xsession-errors (176 sec old) --------------------- (epiphany-browser:4107): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany-browser:4107): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany-browser:4107): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany-browser:4107): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany-browser:4107): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed /usr/lib/iceweasel/firefox-bin: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000057 ( - Adobe ) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000057 ( - Adobe ) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 513018 ***