Created attachment 952383 [details] Output into journalctl -xef while logging into an openldap user. Description of problem: I'm running a lab of fedora desktops connecting to a file server using nfs and ldap for authentication. I'm currently testing f12alpha for use next year. The desktop logs in using ldap and I can create and delete files/folders. However, sound isn't working. Settings > Sound shows no devices. Looking at the output of journalctl -xef as I log in as an ldap user I see the following output (I'll attach the whole output as a file): Oct 31 14:50:41 localhost.localdomain rtkit-daemon[519]: Successfully made thread 3066 of process 3066 (/usr/bin/pulseaudio) owned by '10000' high priority at nice level -11. Oct 31 14:50:41 localhost.localdomain rtkit-daemon[519]: Supervising 4 threads of 2 processes of 2 users. Oct 31 14:50:41 localhost.localdomain pulseaudio[3066]: Home directory not accessible: Permission denied Oct 31 14:50:41 localhost.localdomain gnome-session[2981]: WARNING: App 'pulseaudio.desktop' exited with code 1 Oct 31 14:50:41 localhost.localdomain gnome-session[2981]: E: [pulseaudio] main.c: Daemon startup failed. If I try to run pulseaudio on the command line I get: E: [pulseaudio] core-utils.c: Home directory not accessible: Permission denied Version-Release number of selected component (if applicable): pulseaudio-5.0-10.fc21.x86_64 How reproducible: If I log in as a user on the actual system, pulseaudio starts fine, but when I try to log in user using openldap/nfs it fails Additional Information: We're currently using fedora 20 (up to date) and sound works fine.
You had me really confused by "f12alpha" until I saw the pulseaudio version. This is an old bug now, did you manage to solve it? I run a school lab like this using NFS and freeipa and it works fine. I was using F21, but now it's F22. Check if you are getting selinux errors. Since it has been working I assume you already have the_nfs_home_dirs selinux boolean turned on.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.