You are not logged in.

#1 2013-08-14 18:36:44

JohnnySSH
Member
Registered: 2013-05-04
Posts: 97

Pulse Audio issue with logout using Slim login manager

Hi,

I'm not sure if anyone knows how to get Pulseaudio and Slim working together?


The issue I'm having is that on a multiuser setup, Pulseaudio is still being 'owned' by the initial user.


The LXDM portion of the wiki has the best description solution for this:

https://wiki.archlinux.org/index.php/LXDM


After a user logs out, subsequent users have no access to PulseAudio. The reason is that PulseAudio stores server credentials as properties on the X11 root window, and since LXDM does not restart the X server, these properties are not cleaned up and prevent the sound server from starting up for the next users. To remove these properties on logout, add the following line to /etc/lxdm/PostLogout:

test -x /usr/bin/pax11publish && /usr/bin/pax11publish -r


The only issue is how does one apply this to Slim, or alternatively what other workaround can be done in order to get Pulseaudio working for everyone?


Many thanks.

Offline

#2 2013-08-14 18:53:53

Raynman
Member
Registered: 2011-10-22
Posts: 1,539

Re: Pulse Audio issue with logout using Slim login manager

Slim runs your .xinitrc. You probably have something like

exec ${SOME_DE_OR_WM}

at the end of that script. Try replacing it with

${SOME_DE_OR_WM}
test -x /usr/bin/pax11publish && /usr/bin/pax11publish -r

Offline

#3 2013-08-14 19:35:30

JohnnySSH
Member
Registered: 2013-05-04
Posts: 97

Re: Pulse Audio issue with logout using Slim login manager

Unfortunately that didn't work :-(

- Pulse is still tied in to the initial user

Last edited by JohnnySSH (2013-08-14 19:36:13)

Offline

#4 2013-08-15 12:16:32

JohnnySSH
Member
Registered: 2013-05-04
Posts: 97

Re: Pulse Audio issue with logout using Slim login manager

It's strange as the issue seems to be this:

E: [autospawn] core-util.c: Failed to create secure directory (/run/user/xxx/pulse): Permission denied
W: [autospawn] lock-autospawn.c: Cannot access autospawn lock.
E: [pulseaudio] main.c: Failed to acquire autospawn lock

I tried adding:

autospawn = yes

to client.conf under /etc/pulse yet Pulse doesn't seem to be able to launch multiple instances?


How come that Pulse is so difficult to configure for a multiuser environment?

Offline

Board footer

Powered by FluxBB