GNOME Bugzilla – Bug 500585
crash in Volume Control: Just starting up. Note ...
Last modified: 2007-12-07 21:34:08 UTC
What were you doing when the application crashed? Just starting up. Note I have just upgraded to kernel 2.6.24-rc3. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.24-rc3 #1 SMP Thu Nov 29 23:09:55 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 42864640 vsize: 42864640 resident: 20389888 share: 17420288 rss: 20389888 rss_rlim: 4294967295 CPU usage: start_time: 1196384269 rtime: 770 utime: 566 stime: 204 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 -1208891056 (LWP 3099)] (no debugging symbols found) 0xb7f49410 in __kernel_vsyscall ()
+ Trace 180179
Thread 1 (Thread -1208891056 (LWP 3099))
----------- .xsession-errors (3982 sec old) --------------------- localuser:scott being added to access control list stty: standard input: Inappropriate ioctl for device SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3007 ** (gnome-session:3007): WARNING **: Host name lookup failure on localhost. ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 463147 ***