RDM Crashes when amending seemingly any Connection or Credential type
RDM Crashes when amending seemingly any Connection or Credential type
For example, when you right click an RDP Remote Session Connection and change any option available to you in this interface, as soon as you click the "Save" buttion the app crashes completely (stops running, no residual processes) without saving the changes made.
I have tried this with sqlite, Devolution online, and xml datasources.
I share the datasource with the windows app (which allows me to make the changes without issue regardless of which type of datasource is in use at the time)
I think it might be that the windows app is adding some extra formating to the Connection or one of the options set in the RDP Connection in the Windows app is causing th Linux Client to crash.
To test this theory I created some RDP connections using the Linux client and whilst it was slow to save the newley created connection, I was able to amend the connection and save changes as well. I then opened the properties of those connections in the windows app, amde some changed to the Descrtiption field and saved them. Came back to the linux client and removed the text from the description field and was able to save the connections.
The same thing happesn for SSH Connection Types and all Credentisl types.
Logic suggests that this could be a formatting issue shared across all connection types the windows client applies that the linux client just doesn't like.
Has anyone come across this issue before?
Perhaps someone knows that x property options being set causes this issue (unlikely I think as a basic connection or credential type with nothing but a name set has the issue as well)?
RDP Version (Linux installed via caoticAUR): 2022.2.2.5
RDP Version (Windows running on Windows 11): 2022.2.18.0
OS: Garuda Linux running Kernel: 5.19.7-zen2-1-zen (KDE Plasma 5.25.5)
All Comments (6)
Hi,
I modify my entries in a shared data source across all desktop versions of RDM and have not encountered your issue before.
Came back to the linux client and removed the text from the description field and was able to save the connections.
It seems simply modifying the entry in RDM Windows isn't enough to cause RDM Linux to crash.
This might mean that only some information isn't compatible with Linux. Is there a common settings across your entries you usually fill that you might have left out in your example entry?
If you can easily reproduce the crash with a particular entry, you could export it, remove any sensitive information and send us the file. Hopefully, once we import the entry we can have the same issue you do,
Regards
Jonathan Lafontaine
OK So I figured out what causing the crash,.
99% of all the folders I have in my datasource inherit VPN configurations from the folder above. When I disable that inheritance I can them change any setting on a connection with out the app crashing.
All the VPN configurations were created on the Windows Client to utilise one of two Windows VPN configs. I'd imagine that the Linux app is not able to handle this config because its Windows specific, is that correct? I've not yet looked in to the Linux Apps VPN capabilities and am unsure what ti can and can't do.
Awesome investigative work, that helps a ton.
VPN support is somewhat limited in RDM Linux as VPN integration is not as straight forward as it is on Windows.
Each VPN solution management is impacted by your choice of distribution and network manager.
For that reason, the only VPN supported in RDM Linux is Custom VPN where you can manually specify how to manage your VPN through command lines.
However, when an entry is editable, it should be 100% compatible with other RDM variants. It's our aim that editing an entry should not lead to data loss and even less so a crash.
I'll open a high priority ticket to look into your issue.
Jonathan Lafontaine
To help try to pinpoint exactly what is crashing RDM, could you run RDM from a terminal using the remotedesktopmanager command?
If you get a stacktrace printed when crashing, I would be very interested in seeing it.
Jonathan Lafontaine
Unfortunately, running the cient from the command line whilst it crashes did not provide much info:
╭─cjenner@chris in ~ ╰─λ remotedesktopmanager (RemoteDesktopManager:6029): Gtk-CRITICAL **: 18:06:35.777: gtk_widget_grab_default: assertion 'gtk_widget_get _can_default (widget)' failed fish: Job 1, 'remotedesktopmanager' terminated by signal SIGSEGV (Address boundary error)
Is there a command variant that might output more?
Your crash doesn't seem to come from managed code so we probably won't get a stack.
That being said, looks like GTK is going out of bound so there might be more information in /var/log/syslog
Other info that might be useful
- Distribution and version
- Desktop environment
- X vs Wayland
Jonathan Lafontaine