Re: libesd0 v libesd-alsa0
Le mercredi 20 décembre 2006 à 13:29 +, Sam Morris a écrit : > > In all cases, as esound is buggy and unmaintained in Debian, it is > > deactivated by default at least in all GNOME software. The default for > > gstreamer, vlc, xine and others is to use direct ALSA output, which, as > > you explained, has software mixing enabled by default. > > This doesn't seem to be the case. I noticed this problem because I have > had to help a couple of newbies on IRC get their sound working over the > last couple of days. In both cases the culprit was esd which was holding > open the sound device. Installing libesd-alsa0 and killing esd made > everything work again. > > Perhaps it was something they did to their systems themselves after > installing Etch? ESD shouldn't be started unless you check the appropriate box in the GNOME sound preferences. -- Josselin Mouette/\./\ "Do you have any more insane proposals for me?"
Re: libesd0 v libesd-alsa0
On Wed, 20 Dec 2006 13:55:03 +0100, Josselin Mouette wrote: > Le mercredi 20 décembre 2006 à 11:33 +, Sam Morris a écrit : >> On Wed, 20 Dec 2006 10:15:47 +0300, Vladimir Kozlov wrote: >> > Somehow I had libesd0 installed while I have alsa as well, and this >> > prevents alsa from working properly - I had to do alsaconf after each >> > reboot. >> > Shouldn't the libesd-alsa0 be automatically installed with alsa instead >> > the libesd0? >> > >> > Please CC me as I'm not in the debian-devel list. >> >> It is a shame that libesd0 is instaled by default instead of libesd-alsa0 >> but AFAIK it's too late in the release cycle to do anything about it. :( >> >> I think the best way would be to change the shlibs information for >> libesd0 so that packages that use it end up depending on "libesd-alsa0 | >> libesd0". However that would require a rebuild of all depending packages. >> >> Perhaps the installer could be hacked to install libesd-alsa0 by default >> or something. It would be great if we didn't have to go through _another_ >> release where users will have to put up with programs hogging their sound >> cards, especially since alsa-lib now has software mixing configured by >> default. > > Last time I tried, libesd-alsa0 was corrupting sound in a horrible way. > > In all cases, as esound is buggy and unmaintained in Debian, it is > deactivated by default at least in all GNOME software. The default for > gstreamer, vlc, xine and others is to use direct ALSA output, which, as > you explained, has software mixing enabled by default. This doesn't seem to be the case. I noticed this problem because I have had to help a couple of newbies on IRC get their sound working over the last couple of days. In both cases the culprit was esd which was holding open the sound device. Installing libesd-alsa0 and killing esd made everything work again. Perhaps it was something they did to their systems themselves after installing Etch? -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libesd0 v libesd-alsa0
Le mercredi 20 décembre 2006 à 11:33 +, Sam Morris a écrit : > On Wed, 20 Dec 2006 10:15:47 +0300, Vladimir Kozlov wrote: > > Somehow I had libesd0 installed while I have alsa as well, and this > > prevents alsa from working properly - I had to do alsaconf after each > > reboot. > > Shouldn't the libesd-alsa0 be automatically installed with alsa instead > > the libesd0? > > > > Please CC me as I'm not in the debian-devel list. > > It is a shame that libesd0 is instaled by default instead of libesd-alsa0 > but AFAIK it's too late in the release cycle to do anything about it. :( > > I think the best way would be to change the shlibs information for > libesd0 so that packages that use it end up depending on "libesd-alsa0 | > libesd0". However that would require a rebuild of all depending packages. > > Perhaps the installer could be hacked to install libesd-alsa0 by default > or something. It would be great if we didn't have to go through _another_ > release where users will have to put up with programs hogging their sound > cards, especially since alsa-lib now has software mixing configured by > default. Last time I tried, libesd-alsa0 was corrupting sound in a horrible way. In all cases, as esound is buggy and unmaintained in Debian, it is deactivated by default at least in all GNOME software. The default for gstreamer, vlc, xine and others is to use direct ALSA output, which, as you explained, has software mixing enabled by default. -- Josselin Mouette/\./\ "Do you have any more insane proposals for me?"
Re: libesd0 v libesd-alsa0
On Wed, 20 Dec 2006 10:15:47 +0300, Vladimir Kozlov wrote: > Somehow I had libesd0 installed while I have alsa as well, and this > prevents alsa from working properly - I had to do alsaconf after each > reboot. > Shouldn't the libesd-alsa0 be automatically installed with alsa instead > the libesd0? > > Please CC me as I'm not in the debian-devel list. It is a shame that libesd0 is instaled by default instead of libesd-alsa0 but AFAIK it's too late in the release cycle to do anything about it. :( I think the best way would be to change the shlibs information for libesd0 so that packages that use it end up depending on "libesd-alsa0 | libesd0". However that would require a rebuild of all depending packages. Perhaps the installer could be hacked to install libesd-alsa0 by default or something. It would be great if we didn't have to go through _another_ release where users will have to put up with programs hogging their sound cards, especially since alsa-lib now has software mixing configured by default. -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libesd0 v libesd-alsa0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Sorry if this is not the right list to ask such a questions. Somehow I had libesd0 installed while I have alsa as well, and this prevents alsa from working properly - I had to do alsaconf after each reboot. Shouldn't the libesd-alsa0 be automatically installed with alsa instead the libesd0? Please CC me as I'm not in the debian-devel list. Kind regards, Vladimir. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFiOMj2LrwehIvHEQRAiukAJ0cPDEZ9a20AWVAmaDODfhsLsIuZQCfXxq1 kTvZgS95YacNKz5/jHkN3WU= =Tayp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libesd-alsa0
On Wed, Sep 19, 2001 at 05:29:13PM +0200, Christian Marillat wrote: > In the excuses file a see a lot of : > Unsatisfiable Depends: libesd-alsa0 (>= 0.2.22-4) Actually, you see a lot of them for ia64 and m68k. libesd-alsa0 doesn't exist on ia64 or m68k. On the upside, most/all of them are |'ed with something else, so it's not an issue. The unsatisifable deps lines are just hints to make working out problems easier. > Which is exactly the problem with libesd-alsa ? There isn't one. Cheers, aj -- Anthony Towns <[EMAIL PROTECTED]> <http://azure.humbug.org.au/~aj/> I don't speak for anyone save myself. GPG signed mail preferred. ``Freedom itself was attacked this morning by faceless cowards. And freedom will be defended.'' Condolences to all involved.
libesd-alsa0
Hi, In the excuses file a see a lot of : Unsatisfiable Depends: libesd-alsa0 (>= 0.2.22-4) Which is exactly the problem with libesd-alsa ? I don't see any serious/grave/critical bug report. Christian
