Pulseaudio doesn't launch when the home directory is owned by root
Missing data may cause bugs to languish.
Pulseaudio fails to launch if a user does not own his home directory. There are instances where this is a legitimate configuration, such as in an environment where home directories are mounted via NFS and permissions are granted by ACLs. The goal is to provide the user with full control over his home directory while preventing him from changing its top-level permissions.
A user on Launchpad opened a bug report for this several years ago: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137
Someone provided a small patch further down in that thread, and I tested it and confirmed that it does fix the problem: https://launchpadlibrarian.net/320348812/pulse.patch
Check to see if you have pa-info installed by running
If yes please run it
If no please download and run https://gitlab.freedesktop.org/pulseaudio/pulseaudio/blob/master/src/utils/pa-info
Attach the output to this bug report as pa-info.txt
Steps to reproduce
Ownership of the home directory is root:root with ACLs that allow the user to have full control of the contents within the directory.
What is the current bug behavior?
Pulseaudio does not launch with the desktop environment at login, and manually launching the command after the fact gives the following error:
E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied
What is the expected correct behavior?
Pulseaudio launches despite the home directory being owned by root.