[pulseaudio-discuss] Issue with access

Colin Guthrie gmane at colin.guthr.ie
Tue Jul 19 01:27:53 PDT 2011

'Twas brillig, and Fred Frigerio at 19/07/11 02:03 did gyre and gimble:
> On Mon, Jul 18, 2011 at 8:38 AM, Colin Guthrie <gmane at colin.guthr.ie> wrote:
>> 'Twas brillig, and Fred Frigerio at 18/07/11 12:38 did gyre and gimble:
>>> On Mon, Jul 18, 2011 at 4:53 AM, Colin Guthrie <gmane at colin.guthr.ie> wrote:
>>>> 'Twas brillig, and Fred Frigerio at 17/07/11 22:46 did gyre and gimble:
>>>>> I have a strange problem. I have been running pa for a long time under
>>>>> gentoo x86. However from a couple of days back it is not working
>>>>> anymore (it was after a round of updates but I can't pinpoint what
>>>>> might have done it)
>>>>> I can start pulseaudio -v without a problem. However I cannot connect
>>>>> to it afterwards and I get the following error in syslog.
>>>>> pulseaudio[18226]: pid.c: Daemon already running.
>>>>> Any help would be appreciated.
>>>>> This is what I get when starting pulseaudio -v
>>>>> I: alsa-util.c: Error opening PCM device hw:0: Device or resource busy
>>>> This implies some other application already has PA open.
>>>> Some debug is needed I think.
>>>> Can you attach (as .txt files) the output from:
>>>> ck-list-sessions
>>>> getfacl /dev/snd/*
>>>> sudo fuser -v /dev/snd/pcm*
>>>> ps aux | grep pulse
>>>> xprop -root | grep PULSE
>>> Here it goes. The output from the fuser command is empty (I did run it
>>> as root). Also I am running gnome (2.32).
>> That's cool. fuser output being empty is semi-expected (when it's not
>> empty, it can cause problems.
>> OK, so all this looks to be good so far. PA is running, but what is
>> interesting is that the PULSE_SERVER string is not present in your xprop
>> output....
>> Can you try this:
>> PULSE_LOG=99 pactl stat
> See attached. The interesting bit is that it is looking for a native
> file|pipe? that just isn't there. There is a pid file in that
> directory but that's it.

I think you forgot the attachment?

But the fact that it's trying to access the native socket and that
doesn't exist is telling....

It also explains why PA is running but you were allowed to start another PA.

So I'd suggest that *something* is going on with your filesystem that is
"interesting". I suspect that PA is starting, writing it's various
sockets and metadata files, and then having them removed from it by some
other process...

Can you do "ls -l ~/.pulse"?

Can you think of anything that would cause this. I suspect that it's
probably related to $TMPDIR getting cleaned out over vigorously.

>> As a guess, I suspect you are running padevchooser (little tray icon
>> thing) and it's messing up your connection. It's been deprecated for
>> years and we do not recommend it's usage, so you can always try killing
>> it and rebooting.
> I've lurked enough to know that it is a no no. I purged that one out
> of my system some time ago. I double checked and the executable is not
> there.

Good work :)

>> (also feel free to pop on IRC if this is easier than emails)
> We seem to be on different schedules. It's OK. Just the fact that you
> are helping me makes it alright.

No worries :)



Colin Guthrie

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

More information about the pulseaudio-discuss mailing list