GNOME Bugzilla – Bug 488452
crash in Volume Control:
Last modified: 2007-10-23 18:27:43 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 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve-Tangerine Icon Theme: NoiaWarm Memory status: size: 284827648 vsize: 284827648 resident: 22077440 share: 17489920 rss: 22077440 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192834490 rtime: 11 utime: 7 stime: 4 cutime:1 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912508994624 (LWP 3998)] (no debugging symbols found) 0x000000301720d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 171564
Thread 1 (Thread 46912508994624 (LWP 3998))
----------- .xsession-errors (19 sec old) --------------------- SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3626 Initializing nautilus-image-converter extension Initializing nautilus-flac-converter extension seahorse nautilus module initialized Initializing gnome-mount extension Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension Window manager warning: Lost connection to the display ':0.0'; most likely the X server was shut down or you killed/destroyed the window manager. ** Message: drive = 0 ** Message: volume = 0 error getting update info: Cannot find a valid baseurl for repo: fedora ** Message: <info> You are now connected to the wireless network 'linksys'. --------------------------------------------------
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 ***