Bug 415355 - Konsole Profiles do not execute the command
Summary: Konsole Profiles do not execute the command
Status: RESOLVED DUPLICATE of bug 408217
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 19.04.2
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-19 14:25 UTC by Peter Tselios
Modified: 2019-12-20 10:05 UTC (History)
1 user (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 Peter Tselios 2019-12-19 14:25:47 UTC
SUMMARY
I use konsole for so many years now. Profiles gave me the option to open a new tab and to execute a command. This is how a Root console could be open. 
After my upgrade from Fedora 29 to Fedora 30, konsole was updated to 19.04.2 version. And in this version, commands are not executed. 
That means, I am stuck with bash (I cannot open any other shell), I cannot run a root shell automatically, I cannot ssh to a remote host etc. 

STEPS TO REPRODUCE
1. Open konsole
2. Create a profile that uses a simple command (eg su -) and a different to your current profile colour scheme (so as to understand that the profile is changed)
3. Save the profile
4. From the menu (or the shortcut), select this new profile. 

OBSERVED RESULT
Instead of opening a new tab, in your active tab the color scheme of the new profile will be applied. However, the command is *not* executed. 

EXPECTED RESULT
A new Tab should be opened and the command should be executed on it. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 30/5.15
(available in About System)
KDE Plasma Version: 5.15
KDE Frameworks Version: 5.64
Qt Version: 5.12

ADDITIONAL INFORMATION
I have access to a Leap 15.1 with Frameworks 5.55/Plasma 5.12/QT 5.9 and konsole 18.12.3. On this combination, profiles switching works as always.
Comment 1 Wolfgang Bauer 2019-12-20 10:05:22 UTC

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