Bug 362834 - F4 doesn't open terminal in the current directory at least on MTP and SMB
Summary: F4 doesn't open terminal in the current directory at least on MTP and SMB
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: panels: terminal (show other bugs)
Version: 16.12.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
: 374697 (view as bug list)
Depends on: 75324
Blocks:
  Show dependency tree / graph
 
Reported: 2016-05-09 04:51 UTC by Konstantin Kharlamov
Modified: 2020-04-07 17:54 UTC (History)
5 users (show)

See Also:
Latest Commit: https://cgit.kde.org/dolphin.git/commit/?id=5351db95c6460b568052f23399e0ea9b4a02d9b4
Version Fixed In: 20.08.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin Kharlamov 2016-05-09 04:51:30 UTC 
When Dolphin is in MTP or SMB directory, F4 and Shift+F4 should open terminal in the current dir, but opens instead in a pseudo-random place, e.g. in home dir.

Reproducible: Always

Steps to Reproduce:
1. Go inside MTP or SMB directory
2. Press F4 (alternatively Shift+F4)

Actual Results:  
Terminal is opened in pseudo-random place, usually home dir.

Expected Results:  
Terminal should have opened inside the directory that Dolphin is currently in.

Probably, this bug relies on https://bugs.kde.org/show_bug.cgi?id=75324
Comment 1 Viorel-Cătălin Răpițeanu 2016-09-01 23:34:53 UTC 
This feature would be great if it would get implemented.
The same behaviour is seen for sftp as well.
Comment 2 Elvis Angelaccio 2017-01-07 16:07:27 UTC 
*** Bug 374697 has been marked as a duplicate of this bug. ***
Comment 3 Julian Steinmann 2019-02-24 09:39:50 UTC 
This unexpected behavior does still exist with Dolphin 18.12.2. Confirmed.
Comment 4 Nate Graham 2020-04-07 17:54:24 UTC 
Fixed with https://cgit.kde.org/dolphin.git/commit/?id=5351db95c6460b568052f23399e0ea9b4a02d9b4 when using kio-fuse!