Bug 454883

Summary: In fish portocol, directories with names that end in .d cannot be descended into.
Product: [Applications] dolphin Reporter: Emmett Culley <lst_manage>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: REPORTED ---    
Severity: major CC: dolphin-bugs-null
Priority: NOR    
Version First Reported In: 21.12.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Emmett Culley 2022-06-05 15:06:40 UTC 
SUMMARY
Today I attempted to adjust a webserver configuration using dolphin to connect to fish://root@server/etc.  Connection worked as usual and I found I was looking at a listing of the /etc directory.  All good and expected.

Then I clicked on httpd which switched to listing the /etc/httpd directory.  I then clicked on conf.d and got this message at the top of dolphin:

"The file fish://server/etc/httpd/conf.d could not be loaded, as it was not possible to read from it.
Check if you have read access to this file."

And in a pop up dialog I saw this:

"Could not read file fish://server/etc/httpd/conf.d."

On closer inspection I saw that there was no > next to the directory conf.d, which usually means it is not a directory, but the permissions showed drwxr-xr-w. 

So I logged into that server via ssh and was able to enter /etc/httpd/conf.d without a problem, and from there edit or view any of the apache config files.

Then I tried renaming the conf.d directory to conf_d from the dolphin fish connection.  Then I was able click on conf_d to descend into that directory and edit any of the apache config files there.

I tried renaming the directory to conf.d and after that was able to descend into that directory from that dolphin session.  Closing dolphin, opening it again and connectin to that server via fish again, I was again not able to get into the/etc/httpd/conf.d directory.

Turns out this happens no matter which server I connect, some of which are Rocky Linux, most are CentOS Stream 8, and two are CentOS 7.  All do the same.  That is, any directory named *.d cannot be decended into via fish on dolpin.

I just upgraded to Fedora 36, and this was not a problem before the upgrade.  I use dolphin multiple times a day to connect to the servers I manage, and this is the first time I saw this.


STEPS TO REPRODUCE
1. Connect to remote machine via fish
2. navigate to /etc/httpd
3. click on conf.d

OBSERVED RESULT
Error message and pop up as described above

EXPECTED RESULT
Descent into conf.d directory

SOFTWARE/OS VERSIONS
Fedora: 36
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
I did not see this until updated to Fedora 36

This seem to be related to bug 171473, except is is very old.
Comment 1 Emmett Culley 2022-06-05 15:13:03 UTC 
I just discovered that if I type the directory name (conf.d) in the location bar, dolphin will descend into it and give me access to the files in that directory.  That'll do for a work around.
Comment 2 Emmett Culley 2022-06-05 15:28:53 UTC 
 I spoke too soon.  It turns out that when I open the conf.d directory via the location bar I am not able to drag a file or directory into the conf.d directory.  I see "Access denied to ." at the top of the listing, but I am not prompted to copy/move.  The file is not copied/moved into the conf.d directory.

However, if I first rename the directory to conf_d, all works as expected.  Enter fish://root@server/etc/conf_d in the location bar, the drag a file into that directory,  I am prompted for copy or move, and the file is copied when I select Copy.

Note that I am able to rename conf.d to conf_d from dolphin.  As noted before, once I have renamed the directory, I can rename it back to conf.d and I am still able to access that directory normally from that dolphin session.
Comment 3 Emmett Culley 2022-06-19 13:31:23 UTC 
This seems to be fixed after a recent update of dolphin to 22.04.1