Bug 374296 - kate-16.12.0 - with plasma-5.8.5 "Ctrl-O" doesn't open the folder of the current opened file
Summary: kate-16.12.0 - with plasma-5.8.5 "Ctrl-O" doesn't open the folder of the curr...
Status: RESOLVED DUPLICATE of bug 374913
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 17.04.2
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
: 378636 378699 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-12-29 17:24 UTC by Toralf Förster
Modified: 2017-07-29 17:01 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster 2016-12-29 17:24:16 UTC 
instead always the home folder of the user is opened.
This is annoying if you edit files in a remote directory, accessed via fish://.

With plasma 5.8.4 there was no issue.
Comment 1 boogie 2017-02-01 10:36:00 UTC 
I have this BUG too and it is really annoying - open command on any file opened remotely via sftp://, fish://, ... did previously open the same location and now it opens home folder.

Open on local files works ok.

OpenSuse Tumbleweed + Plasma 5.8.5
Comment 2 Darren Lissimore 2017-06-12 00:28:14 UTC 
This is still occurring in full kate git checkout from 2 weeks ago. 
I did some tracing - the bug appears to be in the QFileDialog static function 
 getOpenFileUrls() .
I was testing with  fish open'ed files, and the correct fish url is passed in the dir param for getOpenFileUrls.  You can even force in the fish and file scheme - and it will still default to the users home directory.

May need to re-assign this from Kate to the which-ever Bug tracking component would cover base level Qt function issues.
Comment 3 Alexander Zhigalin 2017-06-12 06:44:04 UTC 
*** Bug 378699 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Cullmann 2017-07-23 09:07:04 UTC 
*** Bug 378636 has been marked as a duplicate of this bug. ***
Comment 5 Alexander Zhigalin 2017-07-29 16:22:05 UTC 

*** This bug has been marked as a duplicate of bug 374913 ***