Esd sound disturbed since ALSA upgrade to 1.0.9

[Debian Bug Importer]

Automatically imported from Debian bug report #313378 http://bugs.debian.org/313378

[Thomas Hood (jdthood-aglu)]

> did@geru-itea:/$ lsmod | grep snd
> snd_intel8x0m 18500 4
> snd_intel8x0 33216 2
> snd_ac97_codec 78360 2 snd_intel8x0m,snd_intel8x0
> [...]

First please figure out why you have the snd_intel8x0m module loaded.
It is supposed to be blacklisted, so neither hotplug nor discover should
be loading it.

Once you have figured that out, please reboot without loading
snd_intel8x0m and see if sound now works properly.
--
Thomas Hood <email address hidden>

[Daniel (dfranganillo)]

Hi, ive a similar problem here. After last Alsa update sound has become choppy.
I have no loaded modules except nvidia.
My system is a PIII-450 with an es1370 that worked without sound
problems yesterday.
Also, esd (my sound daemon) seems to need more CPU than before (3% at most now).

[Didrik Pinte (dpinte-itae)]

Le mardi 07 juin 2005 à 11:23 +0200, Thomas Hood a écrit :
> > did@geru-itea:/$ lsmod | grep snd
> > snd_intel8x0m 18500 4
> > snd_intel8x0 33216 2
> > snd_ac97_codec 78360 2 snd_intel8x0m,snd_intel8x0
> > [...]
>
>
> First please figure out why you have the snd_intel8x0m module loaded.
> It is supposed to be blacklisted, so neither hotplug nor discover should
> be loading it.

snd_intel8x0m is needed by my slmodem.

>
> Once you have figured that out, please reboot without loading
> snd_intel8x0m and see if sound now works properly.

I've added snd_intel_8x0m to my /etc/hotplug/blacklist then rebooted the
computer. Here are the modules loaded :

did@geru-itea:~$ lsmod | grep snd
snd_intel8x0 33216 2
snd_ac97_codec 78360 1 snd_intel8x0
snd_pcm_oss 53344 0
snd_mixer_oss 19872 2 snd_pcm_oss
snd_pcm 92712 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 24644 1 snd_pcm
snd 55300 8
snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 9664 2 snd
snd_page_alloc 10020 2 snd_intel8x0,snd_pcm

Sound is still noisy, so snd_intex8x0m is not the culprit ;-)

Didrik

[Thomas Hood (jdthood-aglu)]

On Tue, 2005-06-07 at 12:49 +0200, Daniel Franganillo wrote:
> After last Alsa update sound has become choppy.

Guys, please file this bug report in the upstream BTS:

    https://bugtrack.alsa-project.org/alsa-bug

Cheers
--
Thomas Hood <email address hidden>

[Austin Chu (eefi)]

I have run into the same problem (I'm on a ThinkPad T42). An interesting
thing I noticed was that sound was only disturbed when sound was being
output by ESD (GNOME system events, Gaim events with ESD selected for
sound method, Rhythmbox with esdsink for GStreamer sink). When sound was
being output straight to ALSA (Gaim events with Automatic selected and
ESD put in standby mode, Rhythmbox with alsasink for GStreamer sink),
everything played perfectly.

On another note, why did you close this bug report? The bug still exists
in the package in the Debian archive. Once a bug is filed upstream, this
bug may be marked forwarded to upstream, but it seems incorrect to say
this bug has been resolved unless it really has been fixed in Debian. In
addition, by leaving the bug open, as it should be, people who have
found a similar problem can find more information in the expected place
(the list of currently-known bugs).

[Jordi Mallach (jordi)]

# Automatically generated email from bts, devscripts version 2.8.14
reopen 312299

[Jordi Mallach (jordi)]

Hi,

On Wed, Jun 08, 2005 at 12:41:31AM -0400, EspeonEefi wrote:
> I have run into the same problem (I'm on a ThinkPad T42). An interesting
> thing I noticed was that sound was only disturbed when sound was being
> output by ESD (GNOME system events, Gaim events with ESD selected for
> sound method, Rhythmbox with esdsink for GStreamer sink). When sound was
> being output straight to ALSA (Gaim events with Automatic selected and
> ESD put in standby mode, Rhythmbox with alsasink for GStreamer sink),
> everything played perfectly.

Interesting. I recall the Ubuntu guys fixing something like this
recently. I wonder if you can fetch esound, esound-common and
libesd-alsa0 from ubuntu
(http://packages.ubuntu.com/breezy/sound/esound) and try.

> On another note, why did you close this bug report? The bug still exists
> in the package in the Debian archive. Once a bug is filed upstream, this
> bug may be marked forwarded to upstream, but it seems incorrect to say
> this bug has been resolved unless it really has been fixed in Debian. In
> addition, by leaving the bug open, as it should be, people who have
> found a similar problem can find more information in the expected place
> (the list of currently-known bugs).

I have reopened it. Depending on your input, it might be reassigned to
esound though.

--
Jordi Mallach Pérez -- Debian developer http://www.debian.org/
<email address hidden> <email address hidden> http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/

[Thomas Hood (jdthood-aglu)]

On Wed, 2005-06-08 at 00:41 -0400, EspeonEefi wrote:
> On another note, why did you close this bug report? The bug still exists
> in the package in the Debian archive. Once a bug is filed upstream, this
> bug may be marked forwarded to upstream, but it seems incorrect to say
> this bug has been resolved unless it really has been fixed in Debian. In
> addition, by leaving the bug open, as it should be, people who have
> found a similar problem can find more information in the expected place
> (the list of currently-known bugs).

There are hundreds of upstream bugs. They don't need to be tracked in
Debian too. Tracking bugs is work.
--
Thomas Hood <email address hidden>

[Thomas Hood (jdthood-aglu)]

> reopen 312299

I expect you to take care of this bug then. Open a bug in the upstream
BTS and mark this report (#312229) as "forwarded". When upstream adds a
comment to the upstream report, forward it to the submitter of this
report. When the submitter of this report answers, forward the answer
upstream. When upstream releases a new version, check to see whether or
not the bug is fixed. None of this will actually fix the bug, but it
will satisfy everyone's bureaucratic impulses.

--
Thomas Hood <email address hidden>

[Didrik Pinte (dpinte-itae)]

Guys,

I've opened a bug in the alsa-base BTS.

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1170

I think we should wait until the test with the Ubuntu packages are done
before tagging this bug has forwarded upstream, no ?

Didrik

[Arjan Oosting (arjanoosting)]

Hi,

My sound is also distorted after the last upgrade of ALSA. I tried the
ubuntu packages of esound (0.2.35-2ubuntu2), but the sound keeps
distorted.

lsmod | grep snd
snd_ens1370 20000 1
snd_rawmidi 26400 1 snd_ens1370
snd_seq_device 8716 1 snd_rawmidi
snd_pcm_oss 55904 0
snd_pcm 98120 2 snd_ens1370,snd_pcm_oss
snd_timer 27268 1 snd_pcm
snd_page_alloc 9988 2 snd_ens1370,snd_pcm
gameport 4800 1 snd_ens1370
snd_ak4531_codec 8192 1 snd_ens1370
snd 56356 9
snd_ens1370,snd_rawmidi,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_ak4531_codec
soundcore 10336 1 snd

Greetings Arjan Oosting

[Didrik Pinte (dpinte-itae)]

I've made the following test :

Using Blackbox, i've listen to mp3 file using beep-media-player outputting directly to ALSA. That work fine.

--> As said before, the bug is clearly not on the ALSA side but a ESD one !

Didrik

[Matt Zimmerman (mdz)]

On Wed, Jun 08, 2005 at 10:02:25AM +0200, Jordi Mallach wrote:

> On Wed, Jun 08, 2005 at 12:41:31AM -0400, EspeonEefi wrote:
> > I have run into the same problem (I'm on a ThinkPad T42). An interesting
> > thing I noticed was that sound was only disturbed when sound was being
> > output by ESD (GNOME system events, Gaim events with ESD selected for
> > sound method, Rhythmbox with esdsink for GStreamer sink). When sound was
> > being output straight to ALSA (Gaim events with Automatic selected and
> > ESD put in standby mode, Rhythmbox with alsasink for GStreamer sink),
> > everything played perfectly.
>
> Interesting. I recall the Ubuntu guys fixing something like this
> recently. I wonder if you can fetch esound, esound-common and
> libesd-alsa0 from ubuntu
> (http://packages.ubuntu.com/breezy/sound/esound) and try.

Something similar has surfaced for me in Breezy recently; I assumed it had
to do with the dmix experiment. We also switched from libesd0 to
libesd-alsa0 recently. esd first tries to open the device at 44.1kHz;
normally that fails on my system, and so it continues on to try 48kHz, which
succeeds. Now, it seems that 44.1kHz succeeds, but the audio stream is
actually played at 48kHz by the hardware, or something along those lines.

Are we talking about the same problem?

--
 - mdz

[Daniel (dfranganillo)]

Also tested with and without esound's output. Mplayers sounds fine
using ALSA or OSS plugins, also Rhythmbox with ossink or alsasink,
even xmms works fine with ALSA. So, it seems to be a problem with
esd?
--
Tritt - Me and my sussie -

[Thomas Hood (jdthood-aglu)]

reassign 312299 libasound2
severity 312299 important
thanks

The malfunction that people seem to have traced to esd and libesd-alsa0
was possibly triggered by upgrade of libasound to the 1.0.9 version.

Didrik Pinte: You filed #312299 against alsa-base on the assumption that
the bug was in the intel8x0 driver; however, you upgraded libasound2 at
the same time and so the change in the latter package could have caused
the problems you see. Can you confirm this? Try going back to the
1.0.8 driver.

I would normally suspect that esd or libesd-alsa0 was the culprit, but
this time we have a report (#312577) saying that artsd also has problems
with alsa-lib 1.0.9. Therefore I am reassigning this report to the
libasound2 package for now.
--
Thomas Hood <email address hidden>

[Thomas Hood (jdthood-aglu)]

clone 312299 -1
reassign -1 libesd-alsa0
forwarded 312299 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1170
thanks

Takashi Iwai says in ALSA bug report log #1170 that there _is_ a bug in
esound so I clone this bug over there.

--
Thomas Hood <email address hidden>

[Thomas Hood (jdthood-aglu)]

This is just to let you know that I reassigned a clone, #313378, of bug
report #312299, to libesd-alsa0. One of the ALSA developers wrote in
(https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1170):

> esound doesn't check the return value of snd_pcm_writei().
> That's why it doesn't work with plug:dmix properly.
--
Thomas Hood <email address hidden>

[Thomas Hood (jdthood-aglu)]

There is[0] a new upstream version (0.2.36) of esound whose change
log[1] contains entries suggesting that the new version may fix the
esd/alsa problems that have been reported (#283814, #313378).

If someone should be so adventurous as to test the new upstream version
of esd then I ask them to let me know whether or not the problem is
actually solved.

[0]ftp://ftp.gnome.org/pub/GNOME/sources/esound/0.2/
[1]ftp://ftp.gnome.org/pub/GNOME/sources/esound/0.2/esound-0.2.36.changes
--
Thomas Hood <email address hidden>

[Glenn (glenn-strong-cs)]

I have just installed the upstream 0.2.36 release and the problem I
was having (identical to the one described here) appears to have gone
away.

--
Glenn Strong

[Thomas Hood (jdthood-aglu)]

retitle 313378 Esd sound disturbed since ALSA upgrade to 1.0.9
tags 313378 fixed-upstream
thanks

On Wed, 2005-06-15 at 13:27 +0100, Glenn Strong wrote:
> I have just installed the upstream 0.2.36 release and the problem I
> was having (identical to the one described here) appears to have gone
> away.

Good to hear! Thanks for testing.
--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #313378 http://bugs.debian.org/313378

[Debian Bug Importer (debzilla)]

Message-Id: <20050607083409.BD7A9B2FEB@geru-scaldit2>
Date: Tue, 07 Jun 2005 10:34:09 +0200
From: Didrik Pinte <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: alsa-base: intel8x0 sounds disturbed since upgrade to alsa-driver 1.0.9a-1

Package: alsa-base
Version: 1.0.9a-1
Severity: normal

Hi,

Since the upgrade to alsa 1.0.9-1 in Sid, my sounds became disturbed,
noisy and not clear.

Nothing has changed to my configuration except today's upgrade from
apt-get (alsa-driver, alsa-lib, alsa-oss and alsa-utils).

Here are the modules loaded :
did@geru-itea:/$ lsmod | grep snd
snd_intel8x0m 18500 4
snd_intel8x0 33216 2
snd_ac97_codec 78360 2 snd_intel8x0m,snd_intel8x0
snd_pcm_oss 53344 0
snd_mixer_oss 19872 3 snd_pcm_oss
snd_pcm 92712 6
snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 24644 1 snd_pcm
snd 55300 13
snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 9664 3 snd
snd_page_alloc 10020 3 snd_intel8x0m,snd_intel8x0,snd_pcm

I have also tried to reboot the computer to be sure all the modules are
reloaded but that did not change anything.

Do you have any idea on how to solve the problem ?

Many thanks in advance

Didrik Pinte

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-686
Locale: LANG=fr_BE@euro, LC_CTYPE=fr_BE@euro (charmap=ISO-8859-15)

Versions of packages alsa-base depends on:
ii alsa-utils 1.0.9a-1 ALSA utilities
ii debconf [debconf-2.0] 1.4.50 Debian configuration management sy
ii debianutils 2.13.2 Miscellaneous utilities specific t
ii linux-sound-base 1.0.9a-1 base package for ALSA and OSS soun
ii lsof 4.74.dfsg.3-2 List open files.
ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo
ii modutils 2.4.27.0-3 Linux module utilities

-- debconf information:
  alsa-common/card-list:
  alsa-base/alsactl_store_on_shutdown: always autosave

[Debian Bug Importer (debzilla)]

Message-Id: <1118136188.14754.3.camel@thanatos>
Date: Tue, 07 Jun 2005 11:23:08 +0200
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: snd_intel8x0m the culprit?

> did@geru-itea:/$ lsmod | grep snd
> snd_intel8x0m 18500 4
> snd_intel8x0 33216 2
> snd_ac97_codec 78360 2 snd_intel8x0m,snd_intel8x0
> [...]

First please figure out why you have the snd_intel8x0m module loaded.
It is supposed to be blacklisted, so neither hotplug nor discover should
be loading it.

Once you have figured that out, please reboot without loading
snd_intel8x0m and see if sound now works properly.
--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 7 Jun 2005 12:49:20 +0200
From: Daniel Franganillo <email address hidden>
To: <email address hidden>
Subject: Similar problem

Hi, ive a similar problem here. After last Alsa update sound has become cho=
ppy.=20
I have no loaded modules except nvidia.
My system is a PIII-450 with an es1370 that worked without sound
problems yesterday.
Also, esd (my sound daemon) seems to need more CPU than before (3% at most =
now).

[Debian Bug Importer (debzilla)]

Message-Id: <1118142020.8158.1.camel@geru-itea>
Date: Tue, 07 Jun 2005 13:00:20 +0200
From: Didrik Pinte <email address hidden>
To: <email address hidden>
Subject: Re: Bug#312299: snd_intel8x0m the culprit?

--=-GbHWJ9cXjr5xyYXlcTlk
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Le mardi 07 juin 2005 =E0 11:23 +0200, Thomas Hood a =E9crit :=20
> > did@geru-itea:/$ lsmod | grep snd
> > snd_intel8x0m 18500 4
> > snd_intel8x0 33216 2
> > snd_ac97_codec 78360 2 snd_intel8x0m,snd_intel8x0
> > [...]
>=20
>=20
> First please figure out why you have the snd_intel8x0m module loaded.
> It is supposed to be blacklisted, so neither hotplug nor discover should
> be loading it.

snd_intel8x0m is needed by my slmodem.

>=20
> Once you have figured that out, please reboot without loading
> snd_intel8x0m and see if sound now works properly.

I've added snd_intel_8x0m to my /etc/hotplug/blacklist then rebooted the
computer. Here are the modules loaded :=20

did@geru-itea:~$ lsmod | grep snd
snd_intel8x0 33216 2
snd_ac97_codec 78360 1 snd_intel8x0
snd_pcm_oss 53344 0
snd_mixer_oss 19872 2 snd_pcm_oss
snd_pcm 92712 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 24644 1 snd_pcm
snd 55300 8
snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 9664 2 snd
snd_page_alloc 10020 2 snd_intel8x0,snd_pcm

Sound is still noisy, so snd_intex8x0m is not the culprit ;-)

Didrik

--=-GbHWJ9cXjr5xyYXlcTlk
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCpX5D9Rlh4Zs4yBMRAnF3AJoDPfr/iD83XrMjKR2QwFf+O9tftgCggh8E
e0livljt2PkpykX7uXk3NJo=
=egzv
-----END PGP SIGNATURE-----

--=-GbHWJ9cXjr5xyYXlcTlk--

[Debian Bug Importer (debzilla)]

Message-Id: <1118174367.8922.14.camel@thanatos>
Date: Tue, 07 Jun 2005 21:59:26 +0200
From: Thomas Hood <email address hidden>
To: <email address hidden>,
 Daniel Franganillo <email address hidden>
Subject: Re: [Pkg-alsa-devel] Bug#312299: Similar problem

On Tue, 2005-06-07 at 12:49 +0200, Daniel Franganillo wrote:
> After last Alsa update sound has become choppy.

Guys, please file this bug report in the upstream BTS:

    https://bugtrack.alsa-project.org/alsa-bug

Cheers
--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 08 Jun 2005 00:41:31 -0400
From: EspeonEefi <email address hidden>
To: <email address hidden>
Subject: ESD only?

I have run into the same problem (I'm on a ThinkPad T42). An interesting
thing I noticed was that sound was only disturbed when sound was being
output by ESD (GNOME system events, Gaim events with ESD selected for
sound method, Rhythmbox with esdsink for GStreamer sink). When sound was
being output straight to ALSA (Gaim events with Automatic selected and
ESD put in standby mode, Rhythmbox with alsasink for GStreamer sink),
everything played perfectly.

On another note, why did you close this bug report? The bug still exists
in the package in the Debian archive. Once a bug is filed upstream, this
bug may be marked forwarded to upstream, but it seems incorrect to say
this bug has been resolved unless it really has been fixed in Debian. In
addition, by leaving the bug open, as it should be, people who have
found a similar problem can find more information in the expected place
(the list of currently-known bugs).

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 8 Jun 2005 09:51:36 +0200
From: Jordi Mallach <email address hidden>
To: <email address hidden>
Subject: reopening 312299

# Automatically generated email from bts, devscripts version 2.8.14
reopen 312299

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 8 Jun 2005 10:02:25 +0200
From: Jordi Mallach <email address hidden>
To: EspeonEefi <email address hidden>, <email address hidden>
Subject: Re: [Pkg-alsa-devel] Bug#312299: ESD only?

--/04w6evG8XlLl3ft
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Wed, Jun 08, 2005 at 12:41:31AM -0400, EspeonEefi wrote:
> I have run into the same problem (I'm on a ThinkPad T42). An interesting
> thing I noticed was that sound was only disturbed when sound was being
> output by ESD (GNOME system events, Gaim events with ESD selected for
> sound method, Rhythmbox with esdsink for GStreamer sink). When sound was
> being output straight to ALSA (Gaim events with Automatic selected and
> ESD put in standby mode, Rhythmbox with alsasink for GStreamer sink),
> everything played perfectly.

Interesting. I recall the Ubuntu guys fixing something like this
recently. I wonder if you can fetch esound, esound-common and
libesd-alsa0 from ubuntu
(http://packages.ubuntu.com/breezy/sound/esound) and try.

> On another note, why did you close this bug report? The bug still exists
> in the package in the Debian archive. Once a bug is filed upstream, this
> bug may be marked forwarded to upstream, but it seems incorrect to say
> this bug has been resolved unless it really has been fixed in Debian. In
> addition, by leaving the bug open, as it should be, people who have
> found a similar problem can find more information in the expected place
> (the list of currently-known bugs).

I have reopened it. Depending on your input, it might be reassigned to
esound though.

--=20
Jordi Mallach P=E9rez -- Debian developer http://www.debian.org/
<email address hidden> <email address hidden> http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/

--/04w6evG8XlLl3ft
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCpqYQJYSUupF6Il4RAngJAJ0VZSKRtsNMhkhj9kNtrbiECsReUQCg806C
jyOcCm0sSo52YTthawm1s0U=
=l4Me
-----END PGP SIGNATURE-----

--/04w6evG8XlLl3ft--

[Debian Bug Importer (debzilla)]

Message-Id: <1118221044.7136.9.camel@thanatos>
Date: Wed, 08 Jun 2005 10:57:24 +0200
From: Thomas Hood <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Re: [Pkg-alsa-devel] Processed: reopening 312299

> reopen 312299

I expect you to take care of this bug then. Open a bug in the upstream
BTS and mark this report (#312229) as "forwarded". When upstream adds a
comment to the upstream report, forward it to the submitter of this
report. When the submitter of this report answers, forward the answer
upstream. When upstream releases a new version, check to see whether or
not the bug is fixed. None of this will actually fix the bug, but it
will satisfy everyone's bureaucratic impulses.

--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-Id: <1118220629.7136.1.camel@thanatos>
Date: Wed, 08 Jun 2005 10:50:29 +0200
From: Thomas Hood <email address hidden>
To: EspeonEefi <email address hidden>,
 <email address hidden>
Subject: Re: [Pkg-alsa-devel] Bug#312299: ESD only?

On Wed, 2005-06-08 at 00:41 -0400, EspeonEefi wrote:
> On another note, why did you close this bug report? The bug still exists
> in the package in the Debian archive. Once a bug is filed upstream, this
> bug may be marked forwarded to upstream, but it seems incorrect to say
> this bug has been resolved unless it really has been fixed in Debian. In
> addition, by leaving the bug open, as it should be, people who have
> found a similar problem can find more information in the expected place
> (the list of currently-known bugs).

There are hundreds of upstream bugs. They don't need to be tracked in
Debian too. Tracking bugs is work.
--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-Id: <1118221994.16726.5.camel@geru-itea>
Date: Wed, 08 Jun 2005 11:13:14 +0200
From: Didrik Pinte <email address hidden>
To: <email address hidden>
Subject: forwarded upstream

--=-Vv1BNC5hWnyoEDN3ObFY
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Guys,

I've opened a bug in the alsa-base BTS.=20

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3D1170=20

I think we should wait until the test with the Ubuntu packages are done
before tagging this bug has forwarded upstream, no ?

Didrik

--=-Vv1BNC5hWnyoEDN3ObFY
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCpraq9Rlh4Zs4yBMRArp4AJ4qwBzjZnUS1WPQ7wfFYonjfquUsACfVXXm
STMeUgvqZmoHhgd2dAsrwUY=
=XvFb
-----END PGP SIGNATURE-----

--=-Vv1BNC5hWnyoEDN3ObFY--

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 08 Jun 2005 12:24:25 +0200
From: Arjan Oosting <email address hidden>
To: <email address hidden>
Subject: Same problem with my Soundblaster PCI 128

Hi,

My sound is also distorted after the last upgrade of ALSA. I tried the
ubuntu packages of esound (0.2.35-2ubuntu2), but the sound keeps
distorted.

lsmod | grep snd
snd_ens1370 20000 1
snd_rawmidi 26400 1 snd_ens1370
snd_seq_device 8716 1 snd_rawmidi
snd_pcm_oss 55904 0
snd_pcm 98120 2 snd_ens1370,snd_pcm_oss
snd_timer 27268 1 snd_pcm
snd_page_alloc 9988 2 snd_ens1370,snd_pcm
gameport 4800 1 snd_ens1370
snd_ak4531_codec 8192 1 snd_ens1370
snd 56356 9
snd_ens1370,snd_rawmidi,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_ak4531_codec
soundcore 10336 1 snd

Greetings Arjan Oosting

[Debian Bug Importer (debzilla)]

Message-Id: <1118235390.19634.1.camel@geru-itea>
Date: Wed, 08 Jun 2005 14:56:29 +0200
From: Didrik Pinte <email address hidden>
To: <email address hidden>
Subject: esd bug

--=-7VHqd1DMTW1Zs11MBw9x
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I've made the following test :

Using Blackbox, i've listen to mp3 file using beep-media-player outputting =
directly to ALSA. That work fine.

--> As said before, the bug is clearly not on the ALSA side but a ESD one !

Didrik

--=-7VHqd1DMTW1Zs11MBw9x
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCpur99Rlh4Zs4yBMRAh6zAJ0ThMxpstiJP7k3WziIp7DWoDraBACfft4U
Kq1ecku6W828qBvRPXkgvyo=
=U21+
-----END PGP SIGNATURE-----

--=-7VHqd1DMTW1Zs11MBw9x--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 8 Jun 2005 10:04:33 -0700
From: Matt Zimmerman <email address hidden>
To: Jordi Mallach <email address hidden>, <email address hidden>
Subject: Re: Bug#312299: [Pkg-alsa-devel] Bug#312299: ESD only?

On Wed, Jun 08, 2005 at 10:02:25AM +0200, Jordi Mallach wrote:

> On Wed, Jun 08, 2005 at 12:41:31AM -0400, EspeonEefi wrote:
> > I have run into the same problem (I'm on a ThinkPad T42). An interesting
> > thing I noticed was that sound was only disturbed when sound was being
> > output by ESD (GNOME system events, Gaim events with ESD selected for
> > sound method, Rhythmbox with esdsink for GStreamer sink). When sound was
> > being output straight to ALSA (Gaim events with Automatic selected and
> > ESD put in standby mode, Rhythmbox with alsasink for GStreamer sink),
> > everything played perfectly.
>
> Interesting. I recall the Ubuntu guys fixing something like this
> recently. I wonder if you can fetch esound, esound-common and
> libesd-alsa0 from ubuntu
> (http://packages.ubuntu.com/breezy/sound/esound) and try.

Something similar has surfaced for me in Breezy recently; I assumed it had
to do with the dmix experiment. We also switched from libesd0 to
libesd-alsa0 recently. esd first tries to open the device at 44.1kHz;
normally that fails on my system, and so it continues on to try 48kHz, which
succeeds. Now, it seems that 44.1kHz succeeds, but the audio stream is
actually played at 48kHz by the hardware, or something along those lines.

Are we talking about the same problem?

--
 - mdz

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 8 Jun 2005 22:05:30 +0200
From: Daniel Franganillo <email address hidden>
To: <email address hidden>
Subject:

Also tested with and without esound's output. Mplayers sounds fine
using ALSA or OSS plugins, also Rhythmbox with ossink or alsasink,
even xmms works fine with ALSA. So, it seems to be a problem with
esd?
--=20
Tritt - Me and my sussie -

[Debian Bug Importer (debzilla)]

Message-Id: <1118653134.7066.23.camel@thanatos>
Date: Mon, 13 Jun 2005 10:58:53 +0200
From: Thomas Hood <email address hidden>
To: <email address hidden>
Cc: EspeonEefi <email address hidden>, Daniel Franganillo <email address hidden>,
 Arjan Oosting <email address hidden>,
 Matt Zimmerman <email address hidden>, Andreas Pakulat <email address hidden>
Subject: Possibly an alsa-lib bug

reassign 312299 libasound2
severity 312299 important
thanks

The malfunction that people seem to have traced to esd and libesd-alsa0
was possibly triggered by upgrade of libasound to the 1.0.9 version.

Didrik Pinte: You filed #312299 against alsa-base on the assumption that
the bug was in the intel8x0 driver; however, you upgraded libasound2 at
the same time and so the change in the latter package could have caused
the problems you see. Can you confirm this? Try going back to the
1.0.8 driver.

I would normally suspect that esd or libesd-alsa0 was the culprit, but
this time we have a report (#312577) saying that artsd also has problems
with alsa-lib 1.0.9. Therefore I am reassigning this report to the
libasound2 package for now.
--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-Id: <1118655577.7066.36.camel@thanatos>
Date: Mon, 13 Jun 2005 11:39:37 +0200
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: Possibly an alsa-lib bug

reassign 312299 libasound2
severity 312299 important
thanks

The malfunction that people seem to have traced to esd and libesd-alsa0
was possibly triggered by upgrade of libasound to the 1.0.9 version.

Didrik Pinte: You filed #312299 against alsa-base on the assumption that
the bug was in the intel8x0 driver; however, you upgraded libasound2 at
the same time and so the change in the latter package could have caused
the problems you see. Can you confirm this? Try going back to the
1.0.8 driver.

I would normally suspect that esd or libesd-alsa0 was the culprit, but
this time we have a report (#312577) saying that artsd also has problems
with alsa-lib 1.0.9. Therefore I am reassigning this report to the
libasound2 package for now.
--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-Id: <1118660520.7066.46.camel@thanatos>
Date: Mon, 13 Jun 2005 13:02:00 +0200
From: Thomas Hood <email address hidden>
To: <email address hidden>
Cc: EspeonEefi <email address hidden>, Daniel Franganillo <email address hidden>,
 Arjan Oosting <email address hidden>,
 Matt Zimmerman <email address hidden>, Andreas Pakulat <email address hidden>
Subject: cloning to libesd-alsa0

clone 312299 -1
reassign -1 libesd-alsa0
forwarded 312299 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1170
thanks

Takashi Iwai says in ALSA bug report log #1170 that there _is_ a bug in
esound so I clone this bug over there.

--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-Id: <1118671238.7066.89.camel@thanatos>
Date: Mon, 13 Jun 2005 16:00:38 +0200
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: reassigned to libesd-alsa0

This is just to let you know that I reassigned a clone, #313378, of bug
report #312299, to libesd-alsa0. One of the ALSA developers wrote in
(https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1170):

> esound doesn't check the return value of snd_pcm_writei().
> That's why it doesn't work with plug:dmix properly.
--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-Id: <1118748985.25283.23.camel@thanatos>
Date: Tue, 14 Jun 2005 13:36:25 +0200
From: Thomas Hood <email address hidden>
To: <email address hidden>,
 <email address hidden>
Cc: Frankie Fisher <email address hidden>, Daniel Franganillo <email address hidden>,
 EspeonEefi <email address hidden>,
 Arjan Oosting <email address hidden>, Matt Zimmerman <email address hidden>
Subject: Possibly fixed upstream

There is[0] a new upstream version (0.2.36) of esound whose change
log[1] contains entries suggesting that the new version may fix the
esd/alsa problems that have been reported (#283814, #313378).

If someone should be so adventurous as to test the new upstream version
of esd then I ask them to let me know whether or not the problem is
actually solved.

[0]ftp://ftp.gnome.org/pub/GNOME/sources/esound/0.2/
[1]ftp://ftp.gnome.org/pub/GNOME/sources/esound/0.2/esound-0.2.36.changes
--
Thomas Hood <email address hidden>

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 15 Jun 2005 13:27:53 +0100
From: Glenn Strong <email address hidden>
To: <email address hidden>
Cc: Thomas Hood <email address hidden>
Subject: Upstream looks good

I have just installed the upstream 0.2.36 release and the problem I
was having (identical to the one described here) appears to have gone
away.

--
Glenn Strong

[Debian Bug Importer (debzilla)]

Message-Id: <1118838721.7065.47.camel@thanatos>
Date: Wed, 15 Jun 2005 14:32:00 +0200
From: Thomas Hood <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: Upstream looks good

retitle 313378 Esd sound disturbed since ALSA upgrade to 1.0.9
tags 313378 fixed-upstream
thanks

On Wed, 2005-06-15 at 13:27 +0100, Glenn Strong wrote:
> I have just installed the upstream 0.2.36 release and the problem I
> was having (identical to the one described here) appears to have gone
> away.

Good to hear! Thanks for testing.
--
Thomas Hood <email address hidden>

[Matt Zimmerman (mdz)]

Imported and passing to Martin for monitoring, in concert with AudioInfrastructure

[Martin Pitt (pitti)]

Hi!

Indeed I tried to apply various patches to the esound Ubuntu package,
but none of them helped so far. The bug is really in esound, it does
not work well with the new ALSA library, which enables dmix by
default.

Indeed direct gstreamer -> ALSA output (or applications outputting
directly to ALSA), and polypaudio work just fine, so this really seems
to be an esound problem.

We already thought of switching to polypaudio completely. It has some
nice features, but still needs a bit of stabilization. I coordinated
this with Otavio Salvador, who recently uploaded polypaudio to Debian
experimental (sitting in NEW ATM, I suppose). However, if the new
esound upstream version fixes the dmix problem, that would be much
appreciated.

Thanks,

Martin

--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org

[Martin Pitt (pitti)]

Hi!

FYI, I tested 0.2.36 as well and it works just fine with ALSA 1.0.9. I
updated and uploaded the Breezy package, you can grab it from
archive.ubuntu.com if you want to.

The packaging is a mess (lots of changes in the package diff.gz), but
I did not want to diverge from Debian so much, so I left it as messy
as it was before (maybe a bit more, though). A proper cleanup would
require a patch system and the submission of bug fixes upstream.

Thanks and have a nice day,

Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org

[Martin Pitt (pitti)]

esound (0.2.36-0ubuntu1) breezy; urgency=low
.
  * New upstream release. Now should work much better with the current ALSA
    library (#11903)

[Ryan Murray (rmurray)]

# Automatically generated email from bts, devscripts version 2.8.14
tags 313378 pending
tags 313563 pending
tags 314294 pending
tags 279108 pending

[Ryan Murray (rmurray)]

Source: esound
Source-Version: 0.2.36-1

We believe that the bug you reported is fixed in the latest version of
esound, which is due to be installed in the Debian FTP archive:

esound-clients_0.2.36-1_i386.deb
  to pool/main/e/esound/esound-clients_0.2.36-1_i386.deb
esound-common_0.2.36-1_all.deb
  to pool/main/e/esound/esound-common_0.2.36-1_all.deb
esound_0.2.36-1.diff.gz
  to pool/main/e/esound/esound_0.2.36-1.diff.gz
esound_0.2.36-1.dsc
  to pool/main/e/esound/esound_0.2.36-1.dsc
esound_0.2.36-1_i386.deb
  to pool/main/e/esound/esound_0.2.36-1_i386.deb
esound_0.2.36.orig.tar.gz
  to pool/main/e/esound/esound_0.2.36.orig.tar.gz
libesd-alsa0_0.2.36-1_i386.deb
  to pool/main/e/esound/libesd-alsa0_0.2.36-1_i386.deb
libesd0-dev_0.2.36-1_i386.deb
  to pool/main/e/esound/libesd0-dev_0.2.36-1_i386.deb
libesd0_0.2.36-1_i386.deb
  to pool/main/e/esound/libesd0_0.2.36-1_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ryan Murray <email address hidden> (supplier of updated esound package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 25 Jun 2005 16:13:24 -0700
Source: esound
Binary: libesd0 libesd-alsa0 libesd0-dev esound-clients esound esound-common
Architecture: source i386 all
Version: 0.2.36-1
Distribution: unstable
Urgency: medium
Maintainer: Ryan Murray <email address hidden>
Changed-By: Ryan Murray <email address hidden>
Description:
 esound - Enlightened Sound Daemon - Support binaries
 esound-clients - Enlightened Sound Daemon - clients
 esound-common - Enlightened Sound Daemon - Common files
 libesd-alsa0 - Enlightened Sound Daemon (ALSA) - Shared libraries
 libesd0 - Enlightened Sound Daemon - Shared libraries
 libesd0-dev - Enlightened Sound Daemon - Development files
Closes: 220058 277860 279108 283235 283814 312087 313378 313563 314294
Changes:
 esound (0.2.36-1) unstable; urgency=medium
 .
   * New upstream release (closes: #313378, #313563, #314294, #283814)
   * Revert changes in unsanctioned NMU.
   * Increase shlib to 0.2.35, when esd_default_options was introduced.
     (closes: #279108)
   * Remove all non dh maintainer scripts -- they're no longer needed.
   * Remove obsolete (potato or earlier) dependencies.
   * Remove html documentation. It's horribly incomplete, and the
     manpages are updated more frequently. (closes: #283235)
   * Add amd64 to alsa list (closes: #277860)
   * Bump DH_COMPAT to 4
   * Reject clients that we can't mix for (closes: #312087)
   * Move libesddsp to /usr/lib/esound (closes: #220058)
   * Some buffer size and delay timing tweaks.
Files:
 f412e5e471174515a5310a14219271c2 733 sound optional esound_0.2.36-1.dsc
 f2ba3597ef584f4eed7a8aa0ce875c2d 485811 sound optional esound_0.2.36.orig.tar.gz
 6a14911260c...

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 17 Jun 2005 09:40:46 +0200
From: Martin Pitt <email address hidden>
To: <email address hidden>
Subject: Ubuntu status

--+nBD6E3TurpgldQp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi!

Indeed I tried to apply various patches to the esound Ubuntu package,
but none of them helped so far. The bug is really in esound, it does
not work well with the new ALSA library, which enables dmix by
default.

Indeed direct gstreamer -> ALSA output (or applications outputting
directly to ALSA), and polypaudio work just fine, so this really seems
to be an esound problem.

We already thought of switching to polypaudio completely. It has some
nice features, but still needs a bit of stabilization. I coordinated
this with Otavio Salvador, who recently uploaded polypaudio to Debian
experimental (sitting in NEW ATM, I suppose). However, if the new
esound upstream version fixes the dmix problem, that would be much
appreciated.

Thanks,

Martin

--=20
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org

--+nBD6E3TurpgldQp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCsn5+DecnbV4Fd/IRAoxcAJ9sSpXxtOgGxF/LavvomB10IOdZjQCgrdEb
3eG0A9JIhch9TLJdZY9GpIg=
=jhrI
-----END PGP SIGNATURE-----

--+nBD6E3TurpgldQp--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 22 Jun 2005 13:49:15 +0200
From: Martin Pitt <email address hidden>
To: <email address hidden>
Subject: Ubuntu package

--gBBFr7Ir9EOA20Yy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi!

FYI, I tested 0.2.36 as well and it works just fine with ALSA 1.0.9. I
updated and uploaded the Breezy package, you can grab it from
archive.ubuntu.com if you want to.

The packaging is a mess (lots of changes in the package diff.gz), but
I did not want to diverge from Debian so much, so I left it as messy
as it was before (maybe a bit more, though). A proper cleanup would
require a patch system and the submission of bug fixes upstream.

Thanks and have a nice day,

Martin
--=20
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org

--gBBFr7Ir9EOA20Yy
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCuVA7DecnbV4Fd/IRAnB/AJ9uPG1LUokbjbCK7AgM7KC0yG1ZsgCg5PsD
mAuuAGB26n2M7xjPkcbb28Y=
=pRSc
-----END PGP SIGNATURE-----

--gBBFr7Ir9EOA20Yy--

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Thu, 23 Jun 2005 01:34:26 -0700
From: Ryan Murray <email address hidden>
To: <email address hidden>
Subject: tagging 313378, tagging 313563, tagging 314294, tagging 279108

# Automatically generated email from bts, devscripts version 2.8.14
tags 313378 pending
tags 313563 pending
tags 314294 pending
tags 279108 pending

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sat, 25 Jun 2005 19:32:21 -0400
From: Ryan Murray <email address hidden>
To: <email address hidden>
Subject: Bug#313378: fixed in esound 0.2.36-1

Source: esound
Source-Version: 0.2.36-1

We believe that the bug you reported is fixed in the latest version of
esound, which is due to be installed in the Debian FTP archive:

esound-clients_0.2.36-1_i386.deb
  to pool/main/e/esound/esound-clients_0.2.36-1_i386.deb
esound-common_0.2.36-1_all.deb
  to pool/main/e/esound/esound-common_0.2.36-1_all.deb
esound_0.2.36-1.diff.gz
  to pool/main/e/esound/esound_0.2.36-1.diff.gz
esound_0.2.36-1.dsc
  to pool/main/e/esound/esound_0.2.36-1.dsc
esound_0.2.36-1_i386.deb
  to pool/main/e/esound/esound_0.2.36-1_i386.deb
esound_0.2.36.orig.tar.gz
  to pool/main/e/esound/esound_0.2.36.orig.tar.gz
libesd-alsa0_0.2.36-1_i386.deb
  to pool/main/e/esound/libesd-alsa0_0.2.36-1_i386.deb
libesd0-dev_0.2.36-1_i386.deb
  to pool/main/e/esound/libesd0-dev_0.2.36-1_i386.deb
libesd0_0.2.36-1_i386.deb
  to pool/main/e/esound/libesd0_0.2.36-1_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ryan Murray <email address hidden> (supplier of updated esound package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 25 Jun 2005 16:13:24 -0700
Source: esound
Binary: libesd0 libesd-alsa0 libesd0-dev esound-clients esound esound-common
Architecture: source i386 all
Version: 0.2.36-1
Distribution: unstable
Urgency: medium
Maintainer: Ryan Murray <email address hidden>
Changed-By: Ryan Murray <email address hidden>
Description:
 esound - Enlightened Sound Daemon - Support binaries
 esound-clients - Enlightened Sound Daemon - clients
 esound-common - Enlightened Sound Daemon - Common files
 libesd-alsa0 - Enlightened Sound Daemon (ALSA) - Shared libraries
 libesd0 - Enlightened Sound Daemon - Shared libraries
 libesd0-dev - Enlightened Sound Daemon - Development files
Closes: 220058 277860 279108 283235 283814 312087 313378 313563 314294
Changes:
 esound (0.2.36-1) unstable; urgency=medium
 .
   * New upstream release (closes: #313378, #313563, #314294, #283814)
   * Revert changes in unsanctioned NMU.
   * Increase shlib to 0.2.35, when esd_default_options was introduced.
     (closes: #279108)
   * Remove all non dh maintainer scripts -- they're no longer needed.
   * Remove obsolete (potato or earlier) dependencies.
   * Remove html documentation. It's horribly incomplete, and the
     manpages are updated more frequently. (closes: #283235)
   * Add amd64 to alsa list (closes: #277860)
   * Bump DH_COMPAT to 4
   * Reject clients that we can't mix for (closes: #312087)
   * Move libesddsp to /usr/lib/esound (closes: #220058)
   * Some buff...