Le mercredi 25 mars 2009 à 19:34 +0100, Peter Verbaan a écrit :
> Package: libesd-alsa0
> Version: 0.2.41-2
> Severity: normal
>
> Hi,
>
> On Wed, Mar 25, 2009 at 18:50h (+0100), Julien Valroff wrote:
> > Le lundi 23 mars 2009 à 18:43 +0100, Josselin Mouette a écrit :
> > > reassign 516081 pulsea
be a problem of
> incorrect path to the socket, maybe accessed directly by another GNOME
> component?
Well, I was/am running pulseaudio, and upgrading from pulseaudio 0.9.10-3 to
version 0.9.14-2 solved the problem for me.
So I guess yours is a different problem.
What socket does esd use?
Sub
Le lundi 23 mars 2009 à 18:43 +0100, Josselin Mouette a écrit :
> reassign 516081 pulseaudio
> thanks
>
> Le dimanche 22 février 2009 à 19:29 +0100, Peter Verbaan a écrit :
> > Package: libesd-alsa0
> > Followup-For: Bug #516081
> >
> > Hi,
> >
> > This looks similar to ticket 121 in the PulseAu
reassign 516081 pulseaudio
thanks
Le dimanche 22 février 2009 à 19:29 +0100, Peter Verbaan a écrit :
> Package: libesd-alsa0
> Followup-For: Bug #516081
>
> Hi,
>
> This looks similar to ticket 121 in the PulseAudio tracker
> (http://www.pulseaudio.org/ticket/121 ).
> Indeed, with version 2.41-2
Package: libesd-alsa0
Followup-For: Bug #516081
Hi,
This looks similar to ticket 121 in the PulseAudio tracker
(http://www.pulseaudio.org/ticket/121 ).
Indeed, with version 2.41-2 of libesd-alsa0,
the socket is created in /tmp/.esd-`id -u`,
while in version 2.36-3 the socket is created in /tmp/.e
5 matches
Mail list logo