GNOME Bugzilla – Bug 491005
crash in Volume Control:
Last modified: 2007-10-28 12:35:13 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 37867520 vsize: 37867520 resident: 18599936 share: 15769600 rss: 18599936 rss_rlim: 4294967295 CPU usage: start_time: 1193564190 rtime: 114 utime: 95 stime: 19 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/mixer_applet2' (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 -1209108144 (LWP 2962)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173392
Thread 1 (Thread -1209108144 (LWP 2962))
----------- .xsession-errors (1279 sec old) --------------------- localuser:krkrao being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2783 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Evince Doc) 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 0x3600003 (Evince Doc) 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 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 463147 ***