'Reconnect' doesn't work
Hi!
I configured my SSH tabs to stay open after a server disconnects, so I can still read what has been written to the console while rebooting before the disconnect. When a server gets back online, I want to "Reconnect" using the right mouse button menu available on the tab title ("Close", "Reconnect", "Settings..."). That doesn't seem to work. Instead, after clicking "Reconnect" a requester pops up, stating:
NullReferenceException - Object reference not set to an instance of an object.
at Devolutions.Protocols.XtermSsh.OnDisconnected()
at Gtk.Application.InvokeCB.Invoke()
at GLib.Timeout.TimeoutProxy.Handler()
System: Ubuntu 22.04
GUI based on X11 (Wayland doesn't work with Teams Screen Sharing)
Remote Desktop Manager installed as DEB package.
Not a major bug though, but perhaps you might want to take note of it anyway.
All Comments (4)
Hi Hartwig,
I tried to reproduce your issue without any success by doing the following steps:
- Disable "Close on disconnect or error" in my SSH settings
- Open the connection
- Reboot the server
- When back online, click "Reconnect"
Is it similar to what you are doing, or am I missing something?
Simon Duguay Létourneau
Hi Simon,
thanks for looking after this issue. What you did to reproduce this problem seems to be absolutely correct. There's not so much 'special' about my configuration for this server connection. The only thing I could think of, to be somewhat different from what you did is, that my settings have been imported from a Windows 10 workstation that I used before recently switching to Ubuntu Linux 22.04 as my main work environment. Files->Export->Export All (.rdm)...
The settings themselves are pretty standard:
Properties -> SSH-Shell -> Advanced -> Internet Protocol: Default
Interactive authentication in terminal: Default
Verbose level: 0
NO: Close on disconnect or error
YES: Enable TCP keepalives
YES: Send keepalive pings: 60
No: Always accept fingerprint
No: Use SSH authentication agent forwarding
No: Disable Nagle's algorithm
No: Enable logging
Unfortunately it's not possible to reboot the same server (or any of the servers I imported from Windows) again at this time, but I was trying to reproduce this problem myself by creating a new virtual machine I could play with. I configured a new connection within Remote Desktop Manager from scratch, just the same way as I configured the servers I imported from Windows. Surprisingly, to that machine I can reconnect without a problem, so I'm not able to reproduce the problem with a newly created connection either.
Perhaps importing the whole tree of connections, settings and keys from an environment on a different operating system might be causing some defaults or settings to be inherited somewhat different?
On occasion I'll try to export and re-import my whole setup as .rdm file on my Ubuntu machine. Perhaps exporting and re-importing the setup on the same operating system will smooth away some rough edges. However, other than that we shouldn't spend too much more time on this problem, as it seems to be a very niche problem. In an ideal world, I wouldn't have to reboot any servers anyway. 😉
Kind regards,
Hartwig Schieck
Hi Hartwig,
I noticed that the "Close on disconnect or error" setting we have, has been replaced by "Disconnect action" in Windows. It may be a setting imported from your Windows workstation causing the issue. If it is the only issue, it should be easy to fix.
I will give it another look tomorrow by importing my settings from Windows. As you said, it seems to be an edge case, so if it is not as quick as I think to fix, I will open a low-priority ticket for later.
If this issue begins to prevent you from working or irritates you, I will raise the priority.
Simon Duguay Létourneau
Hi Simon,
thank you very much, but there's absolutely no need to give this small hiccup any more attention as it deserves. I just wanted to bring this issue to your attention, but it's fine when it gets fixed when there is time. Nothing depends on it and it breaks nothing.
Kind regards,
Hartwig Schieck