[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2020-03-19 Thread Sebastien Bacher
the fix is in the current pulseaudio version in focal now ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.

[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2020-01-20 Thread Daniel van Vugt
Great, thanks. ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Nick Moriarty (nick-moriarty) ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Triaged ** Tags added: fixed-in-14.0 fixed-upstream -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2020-01-20 Thread Nick Moriarty
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

[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2019-07-26 Thread Daniel van Vugt
** Tags removed: trusty -- 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

[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2017-05-21 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** Tags added: trusty xenial ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a

[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2017-05-19 Thread Ubuntu Foundations Team Bug Bot
The attachment "pulse.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray,

[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2017-05-19 Thread Nick Moriarty
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

[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2017-05-14 Thread Daniel van Vugt
Thanks Nick. Happy to keep this bug open. Please just let us know specifically what current Ubuntu version(s) it is still a problem on. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.

[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2017-05-12 Thread Nick Moriarty
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-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2017-05-12 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more.