[kio-extras] [Bug 414482] Dolphin can't create on network resources

[Harald Sitter]

https://bugs.kde.org/show_bug.cgi?id=414482

Harald Sitter <sitter at kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |CONFIRMED
     Ever confirmed|0                           |1

--- Comment #16 from Harald Sitter <sitter at kde.org> ---
We've done some extra debugging on IRC.

The permissions seen on the screenshot look entirely correct. Furthermore
simply calling mkdir in smbclient actually works. So, the directory is
technically writable.

As it turns out we detect the permissions as readonly though.

I believe this is because IS_DOS_READONLY is true
https://github.com/samba-team/samba/blob/8b04590e4d8f817ad6d194bb9d622c18734e3011/source3/libsmb/libsmb_stat.c#L58
or rather I expect it must be because that code doesn't really have any other
way to create a readonly mode set.

Fortunately this is indeed easy to reproduce by simply sharing the **Desktop**
of a windows10 system. I does however seem to not make a difference if one
shares it via the wizard (which would share Users as far as I can tell) or the
Desktop dir directly under a Desktop share. I further suspect that the
readonlyness on our end may have to do with the default state that the Desktop
dir is marked partially readonly in the ntfs attributes by default.

So, the problem could either be in libsmbc collapsing readonly states
incorrectly, or the server saying something is readonly when it isn't. The
latter would make this a rather awkward problem to solve as the only recourse
would likely be to ignore mode flags entirely. Which isn't the biggest loss I
guess since the mode set is so very minimal anyway. It does however also mean
that we'd not correctly detect when something is truly readonly.

It may be that the new api mentioned in bug #402988 helps us get a better graps
of the readonly state though.

This needs a bunch more of what goes on between libsmbc and the server.

-- 
You are receiving this mail because:
You are on the CC list for the bug.