Summary: | media-sound/pulseaudio-0.9.12 - module-protocol-stub.c: Failed to create socket directory '/tmp/.esd/socket': Permission denied | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matteo 'The Peach' Pescarin <peach> |
Component: | Current packages | Assignee: | Gentoo Sound Team <sound> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | brulzki, fadlouni, gentoobugzilla, nicolasbock, pacho, pva, razamatan, rose, sound, tove |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Matteo 'The Peach' Pescarin
2008-10-11 15:02:10 UTC
I think that a workaround could be providing a .nofail before loading the esound module: .nofail .ifexists module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif .fail o commenting out the whole loading (bad) The "Failed to create socket directory '/tmp/.esd/socket'" failure always occurs if pulseaudio was previously started as a different user. Workaround: do "rm -Rf /tmp/.esd" before starting pulsaudio (In reply to comment #2) > The "Failed to create socket directory '/tmp/.esd/socket'" failure always > occurs if pulseaudio was previously started as a different user. > Workaround: do "rm -Rf /tmp/.esd" before starting pulsaudio > Actually, it looks like the solution is to remove the --disable-per-user-esound-socket configure flag in the ebuild. Then, pulseaudio creates a socket based on the user id, like /tmp/.esd-1000/socket. Which would just make it not-working since our esound is compiled with a SINGLE socket rather than per-user sockets. Cool, that explains why it is disabled in all of the pulseaudio ebuilds then. Is there a recommended way for setting it up for multiple users on a single PC, when logged in on different VTs? I previously used a system wide instance of pulseaudio, but the pulseaudio wiki suggests starting it for each login session, which now looks like it won't work. Sincerely, I still use it as system wide, even though Lennart dislikes that idea. On the other hand, I think Lennart considers the main target the standard desktop usage, like Windows and OSX does. We _could_ synchronize both esound and pulseaudio to use per-user sockets like IIRC Ubuntu and Fedora do, but that would also require a rebuild of emul-linux-x86-soundlibs as well. I sincerely feel ESounD is legacy enough not to care about it, but I guess it might be good enough to put it in .nofail for now. I'll talk with Lennart as soon as I have some spare time. Diego, any updates on this bug? I'm all for completely disabling loading that module by default. Is there really a use for it on current systems? *** Bug 375993 has been marked as a duplicate of this bug. *** I am now using pulseaudio and got this issue just now, is there any thing we could do for fixing this? (.nofail, dropping esd module...) Thanks CCing Arun as he is shown as co-maintainer (and would like to see this handled soon as three of the machines I maintain have multiple users most of the times and all of them are affected by this :( ) Can this be solved finally? For now, I am living fine without loading esd plugin (and also enabling ACL support in kernel to let other users control volume when they login on different VTs) there's going to be pain when gnome-3 goes up for everyone and pulseaudio becomes more and more of a dependency on those installs... gentoo needs to address this issue. We dropped esd support altogether at some point. |