That's fixed in the current version in vivid, that might be something we
want to backport to trusty, if somebody is interested it would be useful
to have a testcase description (see
https://wiki.ubuntu.com/StableReleaseUpdates)
** Changed in: samba (Ubuntu)
Status: Triaged => Fix Released
It has been 5 months! When will Ubuntu fix this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323220
Title:
samba-4.1.6 Lock order violation and file lost
To manage notifications about this b
** Package changed: samba4 (Ubuntu) => samba (Ubuntu)
** Changed in: samba (Ubuntu)
Status: New => Triaged
** Changed in: samba (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: samba
Status: Unknown => Fix Released
** Changed in: samba
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323220
Title:
samba-4.1.6 Lock order v
** Bug watch added: Samba Bugzilla #10564
https://bugzilla.samba.org/show_bug.cgi?id=10564
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=10564
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs
