I have a zesty VM and /tmp is not even in a different mountpoint: it's
part of /. Did you partition your machine manually and mounted /tmp with
noexec?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Marking as incomplete because of comment #43
** Changed in: samba (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1584485
Title:
Reopened the artful (devel) task, as the patch was reverted in 2:4.5.8
+dfsg-2ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1584485
Title:
Upgrading samba to latest security
Revised fix-1584485.patch that includes a missing library in the static
build to fix bug #1677329. Patch submitted upstream to samba-technical
awaiting feedback.
** Patch added: "fix-1584485-take2.patch"
The patch was reverted in artful, and will be reverted for the other
affected releases because of the regression it introduced: bug #1677329,
bug #1644428
Feedback from upstream was requested: https://lists.samba.org/archive
/samba-technical/2017-June/121139.html
--
You received this bug
I can confirm the problem reported originally in this bug (all those
segfaults after the upgrade) only happen if you have winbind listed
first, ahead of files or compat.
Any particular reason why that order was chosen? There will for sure be
a "blip" in the winbind service during the upgrade, and