Summary: | Konsole doesn't always respect the --profile command-line option when run from a custom shortcut key. | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | rob <ryampolsky> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | REPORTED --- | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mint (Debian based) | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | 'launcher' script to launch or activate a konsole session based on a profile-set window title |
Description
rob
2018-05-07 19:15:02 UTC
I'm thinking perhaps something in rs2 profile that might be causing this. Can you attach it? Also, the version is rather old; are you able to upgrade? 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@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@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 Actually, y'know what. It does seem to be using the rs2 profile - in that the title bar shows up as "(rob) rs2 -- Konsole", which is what I count on for re-activating the window on the next custom shortcut keypress. So all that's not working is that the light yellow color scheme is not activated on launch. I use to visually identify the rs2 window after it's up. What I've been doing is launching rs2 with my Ctrl-Alt-2 shortcut and then selecting the rs2 profile from the Settings menu once it launches. After that I'm okay. So if you can't reproduce this problem in a later version of konsole, maybe it's not worth worrying about. For what it's worth, I just upgraded to Kubuntu 18.04 (Konsole version 17.12.3), and the behavior is the same. I don't know if this helps, but I just discovered that if I enter my launcher command as: konsole --profile rs2.profile the colors and the titlebar text take. But if I launch it as: konsole --profile rs2 the titlebar text takes, but not the colors. Weird, huh? The rs2.profile trick is a useful workaround, but it's a strange bug, no? |