I'm seeing very confusing behaviour from konsole since recent updates under TumbleWeed (sorry can't isolate as a I applied a few together). konsole when launched from Plasma's menu seems to start running the last "command", which typically for me is mutt (I have kbiff configured with Mail Client setup as 'konsole --profile Email --title Kbiff_Mutt -e /usr/bin/mutt'). If I force a new konsole to launch (say from krunner with 'konsole --profile Shell') then the next time I launch from the menu-favourite or menu->system->konsole then I get a proper terminal, whereas if I've checked my mail from kbiff then the favourite and menu entry will launch konsole with mutt, and when I quit mutt's pager so the konsole instance closes. Reproducible: Always
I'm seeing this too with 16.08.1 when launching konsole from the revelation password manager as one of its "goto commands". Konsole will work just fine until I launch an ssh session from revelation (which runs konsole -e "ssh -l username hostname"), konsole opens the ssh session just fine but from then on every time I select konsole from the menu, or from the run bar, it launches the ssh command and not a shell. I have to restart plasma to get functionality back again. Interestingly there also appears to be an issue with the handling of the -e argument, the help details "Command to execute. This option will catch all following arguments, so use it as the last option." however this appears to no longer be the case: dan@dan.xigen.co.uk ~ $ konsole -e ssh -l username hostname.tld Unknown option 'l'. I had to add double quotes around the ssh part of the call, and when this was done konsole started exhibiting the behaviour detailed above.
Interestingly, after the above behaviour starts happening.. running konsole from an already open shell works just fine, it is just when launching from the menu or the run bar.
(In reply to Dan Haworth from comment #1) > Interestingly there also appears to be an issue with the handling of the -e > argument, the help details "Command to execute. This option will catch all > following arguments, so use it as the last option." however this appears to > no longer be the case: That's a known problem caused by the port to Qt's QCommandLineParser (which doesn's support such "rest of the line" parameters), see bug#366793. The original problem seems to be a duplicate of bug#371863 though, which is fixed in 16.12.0. (I'm about to submit the fix to Tumbleweed btw)
(In reply to Wolfgang Bauer from comment #3) > The original problem seems to be a duplicate of bug#371863 though, which is > fixed in 16.12.0. (I'm about to submit the fix to Tumbleweed btw) Closing as duplicate... *** This bug has been marked as a duplicate of bug 371863 ***
That's wonderful, and really helps my daily workflow. Thanks for all your efforts!
Thanks for the fix and pushing into tumbleweed.