[pulseaudio-discuss] xubuntu 13.10 pulseaudio /run/user

[David Henningsson]

2013-10-20 14:47, duportail skrev:
> Op 19-10-2013 17:41, duportail schreef:
>> Xubuntu 13.10 with standaard pulseaudio
>> If I login a user, the directory /run/user/1001 is created and sound 
>> is ok.
>> When I login a different user i get some errors and no sound:
>> Toegang geweigerd(dutch) = access denied.
>> Should the /run/user/1001 directory be deleted after logout or should 
>> the second user create an other directory?
>> Is thsi pulseaudio error or xubuntu?
>> error: (computer name=pulse)
>> Oct 19 17:33:04 pulse pulseaudio[4142]: [autospawn] core-util.c: 
>> Failed to create secure directory (/run/user/1001/pulse): Toegang 
>> geweigerd
>> Oct 19 17:33:04 pulse pulseaudio[4142]: [autospawn] lock-autospawn.c: 
>> Kan geen toegang tot autospawn-lock krijgen.
>> Oct 19 17:33:04 pulse pulseaudio[4142]: [pulseaudio] main.c: Failed 
>> to acquire autospawn lock
>> Oct 19 17:33:04 pulse pulseaudio[4147]: [autospawn] core-util.c: 
>> Failed to create secure directory (/run/user/1001/pulse): Toegang 
>> geweigerd
>> Oct 19 17:33:04 pulse pulseaudio[4147]: [autospawn] lock-autospawn.c: 
>> Kan geen toegang tot autospawn-lock krijgen.
>> Oct 19 17:33:04 pulse pulseaudio[4147]: [pulseaudio] main.c: Failed 
>> to acquire autospawn lock
>> Oct 19 17:33:04 pulse dbus[541]: [system] Activating service 
>> name='org.blueman.Mechanism' (using servicehelper)
>> Oct 19 17:33:04 pulse pulseaudio[4162]: [autospawn] core-util.c: 
>> Failed to create secure directory (/run/user/1001/pulse): Toegang 
>> geweigerd
>> Oct 19 17:33:04 pulse pulseaudio[4162]: [autospawn] lock-autospawn.c: 
>> Kan geen toegang tot autospawn-lock krijgen.
>> Oct 19 17:33:04 pulse pulseaudio[4162]: [pulseaudio] main.c: Failed 
>> to acquire autospawn lock
>> Oct 19 17:33:04 pulse blueman-mechanism: Starting blueman-mechanism
>> Oct 19 17:33:04 pulse dbus[541]: [system] Successfully activated 
>> service 'org.blueman.Mechanism'
>> Oct 19 17:33:05 pulse blueman-mechanism: loading RfKill
>> Oct 19 17:33:05 pulse blueman-mechanism: loading Ppp
>> Oct 19 17:33:05 pulse blueman-mechanism: loading Config
>> Oct 19 17:33:05 pulse blueman-mechanism: loading Network
>> Oct 19 17:33:09 pulse avahi-daemon[848]: Received response from host 
>> fe80::220:6bff:fe65:a6ef with invalid source port 1027 on interface 
>> 'eth0.1'
>> Oct 19 17:33:09 pulse avahi-daemon[848]: Received response from host 
>> fe80::220:6bff:fe65:a6ef with invalid source port 1036 on interface 
>> 'eth0.1'
>> Oct 19 17:33:35 pulse blueman-mechanism: Exiting
>>
>>
>> _______________________________________________
>> pulseaudio-discuss mailing list
>> pulseaudio-discuss at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
>>
> Ok, got the error: the systemd pam module in /etc/pam.d/common-session 
> does not create a secure run dir in /run/user for every logged in user.
> So pulse is complaining about access .
> Deleted the systemd line in /etc/pam.d/common-session makes all work 
> well.
> Maybe it's because this is on multi-user (multiseat) computers.
> _______________________________________________

Thanks a lot for sharing this workaround - do you think it is the same 
bug as https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1197395 ?

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic