Bug 107039 - Checking for accessibility of the home dir by comparing uids does not work with a network drive
Summary: Checking for accessibility of the home dir by comparing uids does not work wi...
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: All All
: medium major
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-26 07:14 UTC by linschn
Modified: 2018-07-30 10:17 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description linschn 2018-06-26 07:14:49 UTC 
Hi guys,

I just got bitten byt the way you verify whether the home folder is accessible:

https://github.com/pulseaudio/pulseaudio/blob/master/src/pulsecore/core-util.c#L1431

My home is a SSHFS and the local guid does not match the remote st_uid returned by stat() so pulseaudio won't start even though the home folder is perfectly accessible.

IMHO The best way to test if a home folder is accessible is to actually write and read from it, instead of trusting stat().

Happy to test the changes you may make.

Cheers,
Comment 1 Tanu Kaskinen 2018-06-27 11:03:35 UTC 
There have been problems in the past with root overwriting things in user directories when using sudo, which makes me think that it's best to not blindly write stuff to other users' directories.

SSHFS seems to support uid/gid mapping, would that solve your problem? See the idmap, uidfile, gidfile and nomap options: https://linux.die.net/man/1/sshfs
Comment 2 GitLab Migration User 2018-07-30 10:17:05 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/316.

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.