[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply at kde.org]

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

--- Comment #42 from madcatx at atlas.cz ---
I've done a bit more thorough investigation to see how the access permissions
on UDSEntry actually propagate. Here is what I can tell so far:

Current behavior:
When browsing a Windows network in Dolphin, you can:
 - Rightclick a Workgroup, Server or Share. You will get a context menu with
the "Create new" item greyed out.
 - Rightclick anywhere in the empty space, this should give you the same menu
with the "Create new" item available.
 - When things break, the "Create new" item will be greyed out even when you
rightclick into the empty space with a Share's root open in Dolphin. This is a
result of Dolphin thinking that the location is not writable. Any other means
of writing into that location (drag-n-drop, CTRL+C - CTRL+V, ...) will not work
either. This is the problem we are trying to solve here.

Behavior with my patch:
 - Rightclicking a Share shall give you a menu with the "Create new" item
accessible. Creating a file in the Share this way or dropping a file onto the
Share should work.
 - If you open the Share and try to write into it, it will still be broken.

What you can test:
 1) Apply the patch and navigate to the list of Shares on your server in
Dolphin.
 2) Rightclick one of your "unwritable" shares, go to "Create new->Text file"
and check if you can write into the share this way. Alternatively you can drop
a file onto the Share. If you do it like this you should have write access.
 - If your Share requires a valid username/pass combo, *enter the Share first*,
wait until you are asked for the login credentials, authenticate yourself, go
one level up and only then try to write into the share. Yes, really.

These findings are valid for a Fedora 25 client (kio-extras 16.12 with no Red
Hat clever patches) and CentOS 7 samba 4.4 server with user accounts checked
against Windows AD.

Bottomline: smb_kio will benefit from my patch but it does not really fix the
issue at hand as it seems to be a Dolphin bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.