When I execute the command (I have typed "Run all Konsole windows in a single process"): konsole --hold --new-tab -e 'ls' I see: /usr/bin/ls: no se puede acceder a 'konsole': No such file or directory I can exec nothing
(In reply to arnauj from comment #0) > When I execute the command (I have typed "Run all Konsole windows in a > single process"): > > konsole --hold --new-tab -e 'ls' > > I see: > /usr/bin/ls: no se puede acceder a 'konsole': No such file or directory > > I can exec nothing This seems the same as (duplicate?) bug 373440
(In reply to kde.bugs from comment #1) > This seems the same as (duplicate?) bug 373440 Not at all. Bug#373440 is about the "--new-tab" option not working. Yes, the problem reported here has been mentioned there too, but that doesn't mean it's a duplicate or even related. But, as I wrote in bug#373440, this problem here is fixed in 17.04, by the fix for bug#366793, i.e. https://cgit.kde.org/konsole.git/commit/?id=a779c8314a7d27bb4691c220f793540e6f84f6c9
(In reply to Wolfgang Bauer from comment #2) > (In reply to kde.bugs from comment #1) > > This seems the same as (duplicate?) bug 373440 > > Not at all. > Bug#373440 is about the "--new-tab" option not working. Ehm, to be more precise, Bug#373440 is about the "--new-tab" option opening a new window instead of a new tab. ;-) And actually I think we can close this here. I just tried it again, the problem is not reproducible any more in 17.04.0. I tried with 16.12.x in the past, adding https://cgit.kde.org/konsole.git/commit/?id=a779c8314a7d27bb4691c220f793540e6f84f6c9 fixed it, while I was able to reproduce it reliably without that patch.
(In reply to Wolfgang Bauer from comment #2) > Yes, the problem reported here has been mentioned there too, but that > doesn't mean it's a duplicate or even related. Ok, my bad, all clear now, thanks.