Close open sessions with Ctrl+W: last session closed first then selected session
Close open sessions with Ctrl+W: last session closed first then selected session
Hello everybody!
Question: Bug or feature?
During the last versions I recognized the following issue (bug?).
If you open multiple sessions switch to one (via mouse or CTRL+SHIFT+TAB) and want to close the active/selected session with CTRL+W, the last session was closed instead of the active.
Repeat CTRL+W now the active/selected session was closed. Switch to a new session and close with CTRL+W this session was closed.
I can repeat this by open a new set of sessions, switch to a session and want to close the active session, the last one was closed first.
I'm running the Enterprise version on Windows: 2024.1.24.0 64-bit, waiting for the rollout of the latest version in my company, but the release notes doesn't list some kind of fix for this issue.
Anyone else with that issue?
Or did I missed some new settings?
Thank you!
Best regards,
Tobi
All Comments (5)
Hello Tobi,
Thank you for reaching out to us regarding this,
- Could you confirm which type of data source you are using?
I'm also wondering if you would be able to provide us with a recording of this behavior? I will send you a link via private message so that you can upload the recording securely.
Best regards,
Samuel Dery
Hi Samuel,
As data source we are using MSSQL.
I've uploaded two recordings, one for RDP and one for SSH.
Best regards,
Tobi
Hello Tobi,
Thank you for the recordings,
I see, that is indeed odd, could you confirm if you encounter the same behavior with a portable instance of RDM?
To do so, you will need to do the following:
1- Download the .zip file below:
https://remotedesktopmanager.com/home/thankyou/rdmbin
2- Create a new folder on your Desktop
3- Extract the content of the .zip file into the folder created at #2
4- Go to this folder once the .zip file has been extracted and run remotedesktopmanager.exe
5- Connect to your data source
Let me know,
Best regards,
Samuel Dery
Hi Samuel,
The version 2024.1.28.0 - Enterprise on MSSQL was rolled out in my company. Same behavior.
For another bug, I tested a portable version of 2024.1.25.0, and couldn't reproduce (quick) this issue with SSH/RDP.
- but as said, even with our main installation of RDM this behavior doesn't come up everytime
I'll try to reproduce it with the 2024.1.28.0 portable version and also try to reproduce it on another notebook in my team.
Best regards,
Tobi
Hello Tobi,
Thank you for your reply,
I see, no problem, since the issue does not seem to occur with the portable instance, I suspect the problem may be related to your local installation,
I will be waiting for your return regarding your additional tests
Best regards,
Samuel Dery