| Summary: | using fish://user@address results in wrong location | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] kio-extras | Reporter: | Guillermo Belli <gbelli> |
| Component: | FISH | Assignee: | Jörg Walter <trouble> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | mail, pascal, qbast, spectral |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Guillermo Belli
2008-11-06 23:34:05 UTC
I can confirm that the fish://host path is not changed to homedir in dolphin. However, I can't confirm the symptom of not being able to copy files. I can confirm this. When connecting with fish://user@server you are presented with the home directory. but when trying to copy files there (or create them) you get a message about permission denied. When you manually enter fish://user@server/home/user it does however work. this is with kde 4.1.3 (kde4:factory repository) in Opensuse 11 Works for me in 4.2-rc1 Yes, 4.2 RC1 fixed this. I don't think that this bug is fixed completely! When I open a fish-session "fish://user@host.domain:port" (typing it into the location bar) I get the correct path "fish://user@host.domain:port/home/user", but I cannot use Copy&Paste! The resulting error message complains: "Could not write to file fish://user@host.domain:port/file.txt" (without the "/home/user" part!), although the path in the location bar includes the complete remote directory path! But when I go to the location by browsing through folders, writing to this location works. And to make this even stranger: drag and drop, as well as the "Create New"->"Text File" command works flawlessly. Could you please recheck the problem? I'm using KDE 4.2.4. 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! (In reply to Bug Janitor Service from comment #7) > 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! (In reply to Justin Zobel from comment #6) > 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! (In reply to Justin Zobel from comment #6) > 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! Version: 22.12.0 (KDE Framework 5.101.0) Compiler: cc OS: Linux 6.1.1 (Manjaro) Hello, I had forgotten about this bug, but checked again and it's still present, at least partially. Loging into a remote machine via fish://user@address presents the user's home folder, but the location bar doesn't reflect this, it shows the root folder. Copying a file writes it to the user folder now instead of trying to write it to the root folder. Changing to a subfolder reflects the correct path in the location. 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! |