As per the upstream bug report, this was fixed in 4.22.7 and 4.23.4. One user does complain in https://bugzilla.samba.org/show_bug.cgi?id=15926#c18 that 4.23.5 still has the issue though.
The debian/changelog has entries mentioning that specific bug being addressed in 2:4.23.4+dfsg-1. So I wonder if this is still valid in Resolute or Stonking. Would you be able to check if you are affected in Resolute or Stonking (samba 4.23.6)? The same comment linked above also includes a potential reproducer for the bug. We need to verify the reproducer. If valid, it could be used to patch questing. There are several commits mentioning this bug in the 4.22 and 4.23 upstream stable branches, so we also need to identify what is needed to fix the issue here. Next steps: - For now, we should acknowledge questing is affected and there is a potential fix available upstream. We should get a reproducer and test the upstream fix. - Upstream reports the version in resolute and stonking is fixed, but there is a comment in the upstream bug mentioning it is not. This should also be verified. I am not targeting any specific releases yet since we are not sure of all the ones that are affected (questing only or questing, resolute and stonking). ** Bug watch added: Samba Bugzilla #15926 https://bugzilla.samba.org/show_bug.cgi?id=15926 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2132958 Title: Samba 4.22 breaks MacOS timemachine compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/2132958/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
