[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user
A fix for this has been merged upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/134
I believe this should make it into the 14.0 release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1152137
Title:
Pulseaudio won't start when home directory not owned by user
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
I have an NFS mounted home directory on a dedicated fileserver which is
shared with Windows PCs via SMB.
The home directory is not owned by me. ACLs are set on it to allow me
full control of the contents but prevent me from changing its permissions.
This means any files or directories created in the home directory are owned
by me even though the top level is not.
Pulseaudio checks the home directory is owned by the user at startup and
exits if it isn't. This stops it running on my system.
I have recompiled pulseaudio without this check and it works fine.
Please either remove or modify the following startup check:
pulseaudio-1.1/src/pulsecore/src/pulsecore/core-util.c line 1415:
if (st.st_uid != getuid()) {
pa_log_error("Home directory %s not ours.", h);
errno = EACCES;
goto finish;
}
A better check would be for pulseaudio to try and create the files/folders it
needs and fail if it cannot.
I am using Ubuntu 12.04 and pulseaudio 1:1.1-0ubuntu15.2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user
Hi,
This still affects both 14.04 and 16.04 (and probably affects the newer
non-LTS releases). We apply a patch downstream, which I've attached.
Regards
** Patch added: "pulse.patch"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+attachment/4879559/+files/pulse.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1152137
Title:
Pulseaudio won't start when home directory not owned by user
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
I have an NFS mounted home directory on a dedicated fileserver which is
shared with Windows PCs via SMB.
The home directory is not owned by me. ACLs are set on it to allow me
full control of the contents but prevent me from changing its permissions.
This means any files or directories created in the home directory are owned
by me even though the top level is not.
Pulseaudio checks the home directory is owned by the user at startup and
exits if it isn't. This stops it running on my system.
I have recompiled pulseaudio without this check and it works fine.
Please either remove or modify the following startup check:
pulseaudio-1.1/src/pulsecore/src/pulsecore/core-util.c line 1415:
if (st.st_uid != getuid()) {
pa_log_error("Home directory %s not ours.", h);
errno = EACCES;
goto finish;
}
A better check would be for pulseaudio to try and create the files/folders it
needs and fail if it cannot.
I am using Ubuntu 12.04 and pulseaudio 1:1.1-0ubuntu15.2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user
This problem is still present on more recent versions of Ubuntu. We
currently locally patch it to allow home directories to be owned by
either the relevant user, or root.
It would be great if this was patched upstream.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1152137
Title:
Pulseaudio won't start when home directory not owned by user
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
I have an NFS mounted home directory on a dedicated fileserver which is
shared with Windows PCs via SMB.
The home directory is not owned by me. ACLs are set on it to allow me
full control of the contents but prevent me from changing its permissions.
This means any files or directories created in the home directory are owned
by me even though the top level is not.
Pulseaudio checks the home directory is owned by the user at startup and
exits if it isn't. This stops it running on my system.
I have recompiled pulseaudio without this check and it works fine.
Please either remove or modify the following startup check:
pulseaudio-1.1/src/pulsecore/src/pulsecore/core-util.c line 1415:
if (st.st_uid != getuid()) {
pa_log_error("Home directory %s not ours.", h);
errno = EACCES;
goto finish;
}
A better check would be for pulseaudio to try and create the files/folders it
needs and fail if it cannot.
I am using Ubuntu 12.04 and pulseaudio 1:1.1-0ubuntu15.2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 654545] Re: mountall does not honor nobootwait flag on /var/* and /usr/* filesystems
Backport of relevant section in mountall.c for 2.36.4; this should make mountall respect nobootwait, even if the mountpoint is under /usr or /var. ** Patch added: Backport of relevant fix in 2.38 for 2.36.4 https://bugs.launchpad.net/ubuntu/precise/+source/mountall/+bug/654545/+attachment/4427083/+files/mountall.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/654545 Title: mountall does not honor nobootwait flag on /var/* and /usr/* filesystems Status in mountall package in Ubuntu: Fix Released Status in mountall source package in Precise: Confirmed Bug description: Binary package hint: mountall For very valid reasons, mountall always waits on /usr/* and /var/* remote filesystems. That said, /var/opt/* are valid FHS filesystems that are not vital to the system. In order to not get the boot stuck on such remote filesystems, we tried using the nobootwait flag, but it is ignored on /usr/* and /var/* remote filesystems. This is believed to be a bug, since this behaviour should be possible to be forced. In general, it would also be a good idea to make /var/opt/* filesystems default to TAG_NOWAIT since they are not vital to the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/654545/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473010] [NEW] Problems with NFS and iSCSI mounts under /usr and /var on 12.04
Public bug reported: The logic in mountall.c forces the system to wait for all mounts within /usr and /var before continuing the boot process. Sometimes, networked filesystems are mounted within these directories. Because the services that support networked filesystems aren't necessarily started when mountall runs, this can cause the boot process to hang. This has been fixed for Ubuntu 14.04 (mountall 2.53) by allowing the 'nobootwait' flag to be set even for filesystems within /usr and /var, allowing the administrator to specify which filesystems can be ignored. We only have problems with networked filesystems mounted under /usr and /var; elsewhere they are fine (as the system will skip waiting for them by default). I'd like to request a backport of the code from 2.53, which permits the use of 'nobootwait' on filesystems under /usr and /var, onto 2.36 for Ubuntu 12.04. ** Affects: mountall (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1473010 Title: Problems with NFS and iSCSI mounts under /usr and /var on 12.04 Status in mountall package in Ubuntu: New Bug description: The logic in mountall.c forces the system to wait for all mounts within /usr and /var before continuing the boot process. Sometimes, networked filesystems are mounted within these directories. Because the services that support networked filesystems aren't necessarily started when mountall runs, this can cause the boot process to hang. This has been fixed for Ubuntu 14.04 (mountall 2.53) by allowing the 'nobootwait' flag to be set even for filesystems within /usr and /var, allowing the administrator to specify which filesystems can be ignored. We only have problems with networked filesystems mounted under /usr and /var; elsewhere they are fine (as the system will skip waiting for them by default). I'd like to request a backport of the code from 2.53, which permits the use of 'nobootwait' on filesystems under /usr and /var, onto 2.36 for Ubuntu 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1473010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
