Bug 26209 - Pulseaudio cannot start if user's home directory (specifically ~/.config) not readable by root.
Summary: Pulseaudio cannot start if user's home directory (specifically ~/.config) not...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-17 13:33 CET by Stephen Usher
Modified: 2021-09-06 22:53 CEST (History)
2 users (show)

See Also:
Source RPM: pulseaudio-12.2-5.mga7
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Stephen Usher 2020-02-17 13:33:08 CET 
Description of problem:

If a user's home directory is not readable by root, e.g. it is on a remote NFS mount where the root is squashed to nobody.nogroup, then the pulseaudio process is unable to start as it can't read/write to the user's ~/.config hierarchy.

This worked in mga6

Version-Release number of selected component (if applicable):

12.2-5.mga7

How reproducible:

Consistent 

Steps to Reproduce:
1. Login with a user on an NFS mount with the local machine untrusted and user's home directory protected 0700
2. Try to start pulseaudio
3.
Comment 1 Lewis Smith 2020-02-20 20:25:20 CET 
See also bug 26207, bug 26208.

Assigning globally, CC DavidG as main committer for 'pulseaudio'.

CC: (none) => geiger.david68210
Assignee: bugsquad => pkg-bugs

Comment 2 Aurelien Oudelet 2021-07-06 13:14:45 CEST 
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 3 Stephen Usher 2021-07-06 15:33:56 CEST 
This issue was solved by running nscd if using network authentication as changes in systemd meant that non-local authentication wasn't able to get the correct privileges.
Comment 4 Marja Van Waes 2021-09-06 22:53:42 CEST 
(In reply to Stephen Usher from comment #3)
> This issue was solved by running nscd if using network authentication as
> changes in systemd meant that non-local authentication wasn't able to get
> the correct privileges.

Thanks, closing

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.