GNOME Bugzilla – Bug 488975
crash in Volume Control: Volume control is crashi...
Last modified: 2007-10-27 18:15:38 UTC
What were you doing when the application crashed? Volume control is crashing on bootup. When it offers to reload, it comes up and works properly. 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: 38486016 vsize: 38486016 resident: 17842176 share: 15122432 rss: 17842176 rss_rlim: 4294967295 CPU usage: start_time: 1193054849 rtime: 12 utime: 9 stime: 3 cutime:4 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 -1208317616 (LWP 3572)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 171918
Thread 1 (Thread -1208317616 (LWP 3572))
----------- .xsession-errors (25 sec old) --------------------- localuser:damoursda being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3359 (gnome-panel:3477): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x8abb958 (gnome-panel:3477): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x8abb958 seahorse nautilus module initialized ** (nm-applet:3507): CRITICAL **: network_device_is_wired: assertion `dev != NULL' failed ** (nm-applet:3507): CRITICAL **: network_device_is_wireless: assertion `dev != NULL' failed ** (nm-applet:3507): CRITICAL **: nma_get_connected_icon: assertion `dev != NULL' 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 463147 ***