Bug 77895 - esound compat module leaves empty directory on exit when per user sockets are used
Summary: esound compat module leaves empty directory on exit when per user sockets are...
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: modules (show other bugs)
Version: unspecified
Hardware: Other All
: medium minor
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-24 14:03 UTC by Felipe Sateler
Modified: 2018-07-30 10:13 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Felipe Sateler 2014-04-24 14:03:11 UTC
Forwarded from debian bug #561780

The esound compat module does not remove the socket path when compiled with per-user sockets. This leaves the system with empty /tmp/.esd-$UID/ folders.

The fix is simply to remove on line 505 the "&& !defined(USE_PER_USER_ESOUND_SOCKET)"

Thanks
Comment 1 Tanu Kaskinen 2014-04-25 10:30:01 UTC
I sent a patch to the mailing list: http://thread.gmane.org/gmane.comp.audio.pulseaudio.general/20209

I didn't commit the patch right away, because apparently there's some reason behind the USE_PER_USER_ESOUND_SOCKET check, so I wanted to give other people a chance to comment on the patch first.

In the Debian bug there was a claim that if the directory already exists when pulseaudio starts, then pulseaudio startup would fail. That sounds unlikely (I'm sure there was some problem with the esound socket, but just the existence of the directory shouldn't be a problem).
Comment 2 GitLab Migration User 2018-07-30 10:13:18 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/277.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.