Bug 461406 - Konsole switching to default profile after running ssh
Summary: Konsole switching to default profile after running ssh
Status: REPORTED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 22.08.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-04 09:56 UTC by Will
Modified: 2022-12-15 09:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Will 2022-11-04 09:56:07 UTC
SUMMARY
After typing "ssh example.com", Konsole switches the current profile back to the default.


STEPS TO REPRODUCE
1. Create a new Konsole profile besides the default. Change something visually obvious, e.g. the theme, so the bug is easier to spot.
2. SSH into another machine

OBSERVED RESULT

Konsole switches colour schemes, etc. back to the default profile.

EXPECTED RESULT

Konsole continues using the currently active profile.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 6.0.6
KDE Plasma Version:  5.26.2
KDE Frameworks Version:  5.99.0
Qt Version:  5.15.7

ADDITIONAL INFORMATION
I'm using Wayland with the open-source AMD graphics driver. I've got multiple monitors, both scaled to 125%. I'm not (to my knowledge) using sshmanager, and I haven't got "ssh" aliased to anything - it's plain old /usr/bin/ssh. The machine at the other end isn't doing anything weird, this worked fine on my other machine running Plasma.
Comment 1 Will 2022-11-12 12:51:52 UTC
I've found a workaround by deleting the contents of the file `~/.config/konsolesshconfig`.
Comment 2 Paul Black 2022-11-14 11:48:24 UTC
I'm seeing the same with Fedora 37. The workaround doesn't work for me.
Comment 3 Paul Black 2022-11-15 13:14:32 UTC
Actually, the workaround does work for me. My mistake was to delete the file entirely and not just the contents.
Comment 4 Erwan David 2022-12-15 09:48:38 UTC
I think the problem is that sshManager
1) automatically adds everything in the ~/.ssh/config with default profile (should be possible to disable this)
2) applies the settings even if the ssh is not launched through the plugin (should not be the default, principle of least astonishment) 

I have a profile which does a ssh command, thus switch backs to default profile...