Bug 363365 - button "open" clicked from active remote sftp file tries to open nonexistent directory.
Summary: button "open" clicked from active remote sftp file tries to open nonexistent ...
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-21 11:54 UTC by f.paligin
Modified: 2017-01-11 14:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description f.paligin 2016-05-21 11:54:26 UTC
If there is a file opened in kate from a remote sftp server and I press the "open" button while that file is active, the kate is trying to open a nonexistent directory named as that file. 

Reproducible: Always

Steps to Reproduce:
1. Connect using dolphin to the remote sftp server. For example localhost:22/var/
2. Open the file using kate. "For example megafile.php"
3. In kate press the button "File" and choose "Open"

Actual Results:  
The file choosing window appears, but kate tries to chdir to the directory  localhost:22/var/megafile.php/ , not the directory  localhost:22/var/ and reports that derectory  localhost:22/var/megafile.php/ does'nt exist

Expected Results:  
Kate opens the file choosing window and chdirs to localhost:22/var

Ubuntu 16.04 with latest updates.
Comment 1 Matt Lewis 2016-06-10 18:26:47 UTC
Also, if you have a remote document open and try to open another one from the same place you get the same message. I can then click on the actual directory in the file browser and open something from that directory.

sftp: host > path > to > file > actual > directory > currentlyopenedfile.txt

The dialog should just come up showing the stuff in path/to/file/actual/directory.
Comment 2 Alex Richardson 2017-01-11 14:06:39 UTC
This should be fixed in the latest kate versions (it works for me on openSUSE Tumbleweed). Should have been fixed by 5420b5752a30c294486fbaf967187c8a6f64fe42 in frameworkintegration.git