Issue with SSH Terminal Prompt in RDM after update

Issue with SSH Terminal Prompt in RDM after update

avatar
vasilzgurev

Hello,

I use RDM daily on my workstation and notebook (Dell Latitude 5450), each running Fedora 41.

After updating RDM on both devices to the latest release (2025.1.0.11), I'm unable to see the terminal prompt on my notebook when I establish an SSH connection.

I have tried different terminal emulators (Gnome Terminal, Terminator, xterm) and switched between X11 and Wayland display servers, but without success.

The workstation does not experience this issue.

Here are some details about the notebook. Please note that there was no such issue with the previous RDM release.

Could you please help me identify the cause of this issue?

Thank you!

All Comments (7)

avatar
robrinker

I just experienced the same issue on my Ubuntu 22.04 when upgrading to RDM 2025.1.0. It appears the new version may have a font issue. You can work around the issue until it is resolved by going into the properties of your SSH session > SSH Terminal > Terminal > Display tab then changing Font from "Override" back to "Default".

Certainly not ideal as the default font is way too tiny on my monitor. Hopefully this is resolved soon.

Edit: Downgrading to my prior version resolved the issue.

avatar
Nicolas Parr

Hi there,

in the newest version (2025.1.0.11), we made changes to how fonts are calculated and saved due to issues that could occur when saving larger fonts where it would try to round values in a very inaccurate way. While we made a conscious effort to sort this out in a way that wouldn't affect already saved terminal font sizes, it's possible that we overlooked something and that some specific settings could cause issues with this new method... Good news is that simply editing the font and re-selecting the desired size should sort that out.

When selecting "Default", it will use the font set in Preferences > Session Type > Terminal > Terminal Font. When selecting "Override", it will use the font set in the connection instead of using the application's default.

We are very sorry for the inconvenience. Please, if this issue persists even after setting it again, write back so we can investigate further and sort this out.

Best regards.

Nicolas Parr