SUMMARY Generally, I use Plasma, Krusader and Visual Code Studio to work on remote FTP servers modifying code. For quite some time now, I have noticed that, when opening a file from any FTP server from Krusader, the path to the same open file can be opened with two different methods, without the user being able to do anything about it. For example: /home/myname/.cache/kioexec/krun/5331_0/index.php /run/user/1000/doc/4578b2a5/index.php /run/user/1000/kio-fuse-rBQlcd/ftp/ftp_user@10.162.0.27/var/www/index.php The last one is the appropriate and transparently functioning route. From then on, accesses to the files in this path are of this type (....ftp/ftp_user/...) and it works fine, but why this erratic behaviour? It usually happens the first time I open a file in that path in that desktop session. STEPS TO REPRODUCE 1. Open a remote FTP file 2. Open again that or another remote FTP file on same server OBSERVED RESULT Erratic path assignation. Some times as a cached file, sometimes like a local file under "/run" and finally, as a "cloned" place under "/run/" but working as in remote server. EXPECTED RESULT To use always the path like "/run/user/ .... /ftp/ftp_user@10.162.0.27/var/www/index.php". SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220218 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.4-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION FTP user/passwords are managed by Plasma wallet, I don't need to repeat them each time. The path ".../kio-fuse-rBQlcd/...." is always different between each desktop session, despite the same FTP server being accessed. This makes it very difficult to work with applications such as Visual Code Studio, because it allows you to mark remote folders as safe, but because the name is different each time, you have to accept the services again in each desktop session in which you access the FTP server.
I would like to add to this, and to solve two related problems. My daily work is on remote FTP servers using Krusader and Visual Studio Code (VSC). At home session, kio-fuse (Krusader) creates a different reference kio-fuse-XXXXXXXX (where XXXXXXXX are letters) to the same FTP connection. While this is not a problem in principle, it is a problem when opening "Trusted Folders" in VSC. VSC allows folders to be assigned the "trusted" attribute, so that on subsequent accesses to that folder, it will trust its contents. By assigning kio-fuse different local references (kio-fuse-XXXXXXXX), VSC understands that it is a different folder and loses the trust it had with it. This would be avoided if the same reference (local path) was always assigned by kio-fuse to remote folders based, for example, on the HASH produced by "ftp://server/folder". Please, take it into account.
> /home/myname/.cache/kioexec/krun/5331_0/index.php Yeah, that's the kioexec fallback path which shouldn't be used in most cases. If you can get this reliably, please tell how. > /run/user/1000/doc/4578b2a5/index.php That's a location from the xdg-document-portal. Whether that is used is entirely up to the application. It might be used if e.g. an URL is passed somewhere. (In reply to Rafael Linux User from comment #1) > I would like to add to this, and to solve two related problems. > > My daily work is on remote FTP servers using Krusader and Visual Studio Code > (VSC). At home session, kio-fuse (Krusader) creates a different reference > kio-fuse-XXXXXXXX (where XXXXXXXX are letters) to the same FTP connection. > While this is not a problem in principle, it is a problem when opening > "Trusted Folders" in VSC. VSC allows folders to be assigned the "trusted" > attribute, so that on subsequent accesses to that folder, it will trust its > contents. > > By assigning kio-fuse different local references (kio-fuse-XXXXXXXX), VSC > understands that it is a different folder and loses the trust it had with > it. This would be avoided if the same reference (local path) was always > assigned by kio-fuse to remote folders based, for example, on the HASH > produced by "ftp://server/folder". > > Please, take it into account. That's https://bugs.kde.org/show_bug.cgi?id=432856 resp. https://invent.kde.org/system/kio-fuse/-/issues/18. The locations within kio-fuse's mount are deterministic and constant, only the temporary mountpoint changes.
> The locations within kio-fuse's mount are deterministic and constant, only > the temporary mountpoint changes. That's the point here. It should be constant mountpoints to avoid all these issues we are talkin about, including my other bug https://bugs.kde.org/show_bug.cgi?id=432856 If this problem is not corrected, it is really impossible to work "seriously" in web development.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
This issue is not solved, and no one ask me for more info. This way of "autoclose" bugs is like if no one matters a bug and simply is not even considered.