GNOME Bugzilla – Bug 472724
crash in Volume Control: closing it
Last modified: 2007-09-02 11:35:52 UTC
Version: 2.18.0 What were you doing when the application crashed? closing it 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:35:01 EDT 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: 42733568 vsize: 42733568 resident: 13004800 share: 9940992 rss: 13004800 rss_rlim: 4294967295 CPU usage: start_time: 1188702419 rtime: 100 utime: 93 stime: 7 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208149776 (LWP 18839)] (no debugging symbols found) 0x00e7f402 in __kernel_vsyscall ()
+ Trace 159748
Thread 1 (Thread -1208149776 (LWP 18839))
----------- .xsession-errors (82 sec old) --------------------- localuser:darklight being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/18574 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name --------------------------------------------------
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 471133 ***