Comment # 3 on bug 1018672 from Noel Power

I've managed to reproduce this using thunderbird (with kde desktop), but...
this seems nothing at all to do with samba but something rather to do with
thunderbird/kde (and integration with the filechooser) E.g. I *seem* to get the
exact same file chooser when using okular and am able to save a file to a user
share (from another leap) with no problem.

I've taken some network traces too just to see if I could spot something, the
failure case seems to just stop after doing some testing to see if the file
'target' exists on the share. The successful attempt (from okular) additionally
checks to see if the file 'target.part' file exists and then does the actual
file copyto 'target.part' and renames it afterwards. There are no (afaics)
unexpected responses from the samba side. I believe

so just to recap imho I think this needs to be investigated from the
thunderbird/kde file chooser side to see where (or what) is happening that it
thinks it cannot save to the samba share. It's entirely possible that
thunderbird's use of the kde file chooser triggers it to use the underlying
samba client library in a different way to other application that causes some
problem, from the server side though we don't see any unexpected error