Comment 14 for bug 1977491

Actually, as I mentioned, I can reproduce the bug on Kinetic in the same way it reproduces on Jammy.

If you use fruit:resouce = stream, you hit the bug and get a panic.
If you use fruit:resource = xattr, no bug.
And it doesn't matter what OS the client machine is using, which was the point of testing it using a Linux client too.

Further, I don't particularly get why you keep mentioning that macOS is "proprietary". Canonical is shipping Samba, which enables Ubuntu machines to be a File, Print, and AD/DC machine for *many* different OSes, many of them "proprietary". It is a reimplementation of "proprietary", yet now openly documented protocols: CIFS & SMB. As a fellow engineer, I'd say it's on Canonical to therefore ship said software making a best effort to insure it actually works. That, therefore, doesn't absolve Canonical or upstream from having a lab, test harness with requisite example hardware, and QA process to make a reasonable effort to see that the bits shipped work.

My Mac connects just fine to a "proprietary" Windows server over Microsoft and Apple's implementation of SMB. Which means Apple, implemented the openly documented SMB protocol, better than upstream and Canonical. And, if I reach out to either Microsoft or Apple, because my Linux box(es) can't connect to their OSes over SMB, they don't scoff because Linux is "open". They investigate, and fix the problem.

Not trying to be a dick, but there's an attitudinal problem here in many open source projects and distributions, that leads to nonsense resource allocation decisions, that in turn lead to crappy bugs like this that wouldn't ship, if the attitude didn't make people think there is an excuse for insufficient effort and care.

I'll contact upstream. But you guys have a bug, you're perhaps inheriting from them...perhaps not..., because nobody upstream or at Canonical is making a de minimis effort to properly QA the software to see that it's fit for stated purpose.