Bug 372766 - Konsole stucks lastly opened directory when opening a new instance even explicitly set otherwise
Summary: Konsole stucks lastly opened directory when opening a new instance even expli...
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 16.08.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-21 23:50 UTC by Ongun Kanat
Modified: 2017-01-25 23:31 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 Ongun Kanat 2016-11-21 23:50:21 UTC
Konsole behaves strangely when a new instance is launched (via Krunner, command, or shortcut). It launches the new window working in the same working directory with previous windows. 

As I can see it does not launch another konsole instance, but says the existing process to launch a new window. I thought it shares the same code part as tab creation (didn't dig into code). So I changed the "Initial directory" to my home directory and also unchecked "Start in the same directory as current tab" in current profile settings dialog. Looks like it doesn't work for new windows and it launches the new window while PWD set where the previously open tab's PWD is.

The strange thing is that the new tabs are opened working in my home directory while new windows follow the previous tab.
Comment 1 Wolfgang Bauer 2016-11-22 13:25:01 UTC
Sounds like it may be related to bug#371863 which has been fixed already:
https://cgit.kde.org/konsole.git/commit/?id=4ec9b565800b9e9bdbf45dbb5983530fb95791e7

Could you maybe try that patch (or latest git master)?
It will be in 16.12.0 though.
Comment 2 Ongun Kanat 2016-11-23 00:41:51 UTC
Will take a look at it.
Comment 3 Ongun Kanat 2017-01-25 23:31:43 UTC
(In reply to Wolfgang Bauer from comment #1)
> Sounds like it may be related to bug#371863 which has been fixed already:
> https://cgit.kde.org/konsole.git/commit/
> ?id=4ec9b565800b9e9bdbf45dbb5983530fb95791e7
> 
> Could you maybe try that patch (or latest git master)?
> It will be in 16.12.0 though.

Looks like it solved the issue. Thanks