[konsole] [Bug 393968] Konsole doesn't always respect the --profile command-line option when run from a custom shortcut key.

[rob]

https://bugs.kde.org/show_bug.cgi?id=393968

--- Comment #2 from rob <ryampolsky at yahoo.com> ---







I apologize for the old version - it's what the latest Mint KDE system
includes, so there's that...

Below is a diff of the two profiles.  The only difference besides the title and
color scheme is that the jds profile had Command=/bin/bash, and the rs2 profile
had no Command setting (even though the profile manager showed /bin/bash).

I changed modified the rs2 profile and then changed it back to get the Command
setting fixed, but it doesn't change anything.  Note that my launcher script
overrides the command anyway by running ssh in the konsole session like so:

               konsole --profile rs2 -e ssh rob at rs2&

Anyway, I've also tried a few other things.  I copied jds.profile to
rs2.profile, and that does not work - so it's not something in the .profile
file itself.  Then I edited my launchrs2.sh script to use the jds profile, and
that does work (although, of course, with the jds profile, which I don't want). 

So still, for some reason, the rs2 profile does not work from the command line
when the launchrs2.sh script is run via a custom shortcut key.  But again, it
*does* work when the same launchrs2.sh script is run from the command line
within konsole.  Pretty strange, right?

here's the diff of the original profiles - though I think I've eliminated this
as the problem.

rob at ry-desktop ~/.local/share/konsole $ diff jds.profile rs2.profile
2c2
< ColorScheme=light blue
---
> ColorScheme=BlackOnLightYellow
5,7c5,6
< Command=/bin/bash
< LocalTabTitleFormat=jds: %n
< Name=jds
---
> LocalTabTitleFormat=rs2: %n
> Name=rs2

-- 
You are receiving this mail because:
You are the assignee for the bug.