Summary: | SFTP kioslave does not behave as expected with the file opening dialog | ||
---|---|---|---|
Product: | [Unmaintained] kde-windows | Reporter: | Xavier Guerrin <xavier.kde> |
Component: | network and files | Assignee: | KDE-Windows <kde-windows> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | ahartmetz, bcooksley, emrecio, ps_ml |
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
URL: | http://edony.tuxfamily.org/~xav/img/kde-windows-kate-sftp-kioslave-issue.png | ||
Latest Commit: | http://commits.kde.org/kdelibs/0be22f55bae89b3afeb5e4ceefb88c4ce03c0341 | Version Fixed In: | |
Sentry Crash Report: |
Description
Xavier Guerrin
2013-05-26 16:53:11 UTC
One more thing which is weird: if you enter the same commandline in dolphin this works like a charm. If you use the file dialog (or in kate the overview) this will not work. Git commit 0be22f55bae89b3afeb5e4ceefb88c4ce03c0341 by Patrick Spendrin. Committed on 05/06/2013 at 00:50. Pushed by sengels into branch 'KDE/4.10'. fix sftp kioslave redirection problem. M +1 -1 kfile/kdiroperator.cpp http://commits.kde.org/kdelibs/0be22f55bae89b3afeb5e4ceefb88c4ce03c0341 Hello, Following Patrick's commit and update to KDE 4.10-3, file dialogs now work much better with the SFTP KIO/slave. Also, I was unable to make the sftp kioslave.exe process crash again. The only remaining bug is this: * Start an application (e.g. Kate) * Trigger the open file dialog * Enter sftp://user@hostname in the address bar -- on most hosts, it will redirect to the home adequate home directory, e.g. sftp://user@hostname/home/user/ * Click a file like you want to drag-and-drop it; this will display "user/filename.ext" in the "Name:" field instead of "filename.ext" * Validating or clicking normally on the file ends up showing the following error message: "The file or folder sftp://user@hostname/home/user/user/filename.ext does not exist." Same here. Looks like it's filling in the path in the address bar of kate, but it's doing the whole path with filename instead of just the dirname part of the path. Kate Version 5.0.0 Using KDE Frameworks 5.12.0 Oh, it's on Fedora 22 / Linux / i386 About the bug where it tries to open a file instead of the folder of the file, that bug is actually an application bug in Kate and KWrite. Bug 352490 about that has been fixed. If the remaining problems in this bug are just about that, this can be closed. But apparently there are other problems? Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. I downloaded the latest nightly build of Kate for Win64, installed it and launched it with QT_QPA_PLATFORMTHEME=kde to get rid of the native Windows open dialog. Alas, this only switched Kate to the Qt open dialog as opposed to the KDE one. My understanding is that the KDE open dialog is simply unsupported / not available under Windows. Please let me know if I am wrong. Additionally, running kate.exe sftp://user@host/some/file/path resulted in the following error message: Unable to create io-slave. Unknown protocol 'sftp'. Again, let me know if I missed something (maybe I should have installed a common package?). Assuming I did not miss anything: well, needless to say, this is underwhelming: 7 years later, the KDE for Windows project still feels like a useless portability proof-of-concept. I change this report to "REPORTED"; I would advise to double-check the current status of the "bring KIO/slaves to Windows" idea and adjust this report accordingly (e.g. RESOLVED/INTENTIONAL). Thanks for your time. The current builds of Kate produced by the Binary Factory don't include kio-extras, which is where kio_sftp lives. Building kio_sftp on Windows if memory serves is slightly problematic (although I may be wrong on that) Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! 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! |