GNOME Bugzilla – Bug 345187
esound "hangs" after a short time - applications don't respond
Last modified: 2012-02-28 20:33:17 UTC
esound 0.2.36 on Gentoo Linux, x86 When I use an application which uses esound/esd to "make noise", the output stops after a short period of time (~40 seconds) and esd then consumes about 100% CPU. During that time, any "esd application" (ie. applications, which use esd) hangs/doesn't respond; after killing esd, those applications respond again. I'm using a "lousy" 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) on my notebook. Any ideas about how I could debug that, so that sound works? I just tried Ubuntu 6.0.6 and there sound output works just fine - so it's not a (pure) hardware issue but rather a misconfiguration on my side. What can be done about it?
alexander@blatt ~ $ uname -a Linux blatt 2.6.16-suspend2-r8.043.security-models #2 PREEMPT Fri Jun 9 21:09:15 CEST 2006 i686 Intel(R) Celeron(R) M processor 1.50GHz GNU/Linux I'm using ALSA from the kernel, a suspend2.net kernel which is patched with some Gentoo patches. Kernel module: snd_via82xx 24596 1 esd shows itsel as this in ps awux: 1000 11194 0.0 0.1 3056 1312 ? Ss 17:51 0:00 /usr/bin/esd -terminate -nobeeps -as 2 -spawnfd 15 alexander@blatt ~ $ esd --version Esound version 0.2.36
alexander@blatt ~ $ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.11rc2 (Wed Jan 04 08:57:20 2006 UTC). esound is compiled with the following Gentoo portage USE flags: [ebuild R ] media-sound/esound-0.2.36-r1 USE="alsa -debug -ipv6 -static -tcpd" 0 kB This translates to: ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --sysconfdir=/etc/esd --disable-ipv6 --disable-static --disable-debugging --enable-alsa --without-libwrap --build=i686-pc-linux-gnu
*** Bug 345204 has been marked as a duplicate of this bug. ***
Can you tell us what build flags you are using when compiling?
(In reply to comment #4) > Can you tell us what build flags you are using when compiling? > You mean the configure command line? (In reply to comment #2) > alexander@blatt ~ $ cat /proc/asound/version > Advanced Linux Sound Architecture Driver Version 1.0.11rc2 (Wed Jan 04 08:57:20 > 2006 UTC). > > esound is compiled with the following Gentoo portage USE flags: > > [ebuild R ] media-sound/esound-0.2.36-r1 USE="alsa -debug -ipv6 -static > -tcpd" 0 kB > > This translates to: > > ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man > --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc > --localstatedir=/var/lib --sysconfdir=/etc/esd --disable-ipv6 --disable-static > --disable-debugging --enable-alsa --without-libwrap --build=i686-pc-linux-gnu >
I was more thinking of the compiler flags. What level of optimization etc. -O2?
the hangs in the other applications should be fixed with the patch I attached to bug #542391
"esound" has not seen code changes for more than three years according to http://git.gnome.org/browse/esound/log/ , and it will not see further active development anymore according to its developers. Closing this report as WONTFIX - Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.