GNOME Bugzilla – Bug 480913
crash in Volume Control: I dont know...
Last modified: 2007-10-06 09:37:33 UTC
What were you doing when the application crashed? I dont know... 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 42205184 vsize: 42205184 resident: 19181568 share: 16359424 rss: 19181568 rss_rlim: 4294967295 CPU usage: start_time: 1190893880 rtime: 327 utime: 258 stime: 69 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 -1208735408 (LWP 3060)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 165885
Thread 1 (Thread -1208735408 (LWP 3060))
----------- .xsession-errors --------------------- localuser:ipenk being added to access control list SESSION_MANAGER=local/utm.my:/tmp/.ICE-unix/2835 ** (gnome-session:2835): WARNING **: Host name lookup failure on localhost. compiz: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed. error getting update info: failure: repodata/primary.sqlite.bz2 from livna: [Errno 256] No more mirrors to try. wine: could not load L"Z:\\home\\ipenk\\Desktop\\tremulous-1.1.0-installer.x86.run": Bad EXE format for wine: could not load L"Z:\\home\\ipenk\\Desktop\\tremulous-1.1.0-installer.x86.run": Bad EXE format for ALSA lib conf.c:3949:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL default:0 --------------------------------------------------
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 ***