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 appropri
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.
>&
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&#x
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 inst
-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-als
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
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
7 matches
Mail list logo
