Sebastian

Hi,

you can close this issue. It has been resolved with the RDM 2026.3.x Train.

Thanks for your help!

BR

Sebastian

Hi,

i can't speak for Stephan but for me all gui related issues have been resolved with RDM 2026.3.0.5. Really great release @Maxim Robert

BR

Sebastian

Hi all,

depending on what Gnome version you are running the following worked for me:

Gnome >50:

gsettings set org.gnome.mutter experimental-features "[]"

Default: org.gnome.mutter experimental-features "['scale-monitor-framebuffer', 'xwayland-native-scaling']"

Gnome = 50 (Fedora 44):

gsettings set org.gnome.mutter.wayland xwayland-scaling-factor 1 (Default: 0).

After a reboot the GUI was working for me just fine without scaling issues. Seems to be an issue with Avalonia and XWayland. Hoping the native Wayland integration with Avalonia 12.1 will fix this...

BR

Great news that Avalonia 12.1 is now supporting Wayland natively. Please implement this soon in RDM.

Hi #2,

when closing the app it finally happend. Got the error message again.

Please find below the CLI Output and the applog attached.

(RemoteDesktopManager:25783): GLib-GObject-CRITICAL **: 15:16:07.648: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(RemoteDesktopManager:25783): Gtk-WARNING **: 15:16:21.314: Attempting to add a widget with type GtkStatusbar to a GtkEventBox, but as a GtkBin subclass a GtkEventBox can only contain one widget at a time; it already contains a widget of type GtkStatusbar free(): corrupted unsorted chunks

Hi,

thanks for getting back to me. I tried to recreate the issue today but since I've started RDM via CLI i haven't experienced the issue (...).

I'll keep at it this week trying to recreate the issue and provide the requested log.

Just wanted to give you a short feedback that your reply wasn't overlooked.

BR

Sebastian

Just wanted to add the application log show the frequency and maybe some more details on the issue. In addition I found this error which might explain why i can't send the error report directly though the application:

[6/12/2026 4:11:26 PM - 2026.2.0.6 - 64-bit] Error silent: Could not find the top-level widget ID for RDMOSendErrorMessageWindow.

Good Morning,

i'm running RDM v 2026.2.0.6 64 Bit on Fedora 43 (Linux 7.0.12-101.fc43.x86_64) with Gnome 49. Ever since I've started using RDM under Linux I've had the problem that the application sometimes looses focus and becomes unusable. I usually have to close and restart the app.

I'm assuming this has something to do with the incomplete Wayland support that will hopefully remediated via the Avalonia Gui update. However, since the last two updates I've encounter the issue much more frequently and in addition got an error message displayed. Strangely the option to "send error report" doesn't seem to work for me.

Therefor, I though I share a screenshot as well as text of the error message for you to have a look and maybe it is possible with a small fix to resolve this issue under wayland. if it's a bigger issue don't bother. I'll wait for the Avalonia Gui then.

Error message in text:

NullReferenceException - Object reference not set to an instance of an object.

at Client.Windows.MainWindow.SaveLayout()

at Devolutions.RemoteDesktopManager.Managers.ActionManager.ForceClose(Boolean exit, Boolean saveOpenedConnections)

at Devolutions.RemoteDesktopManager.Managers.ActionManager.QuitApplication(Boolean saveOpenedConnections)

at Client.Windows.MainWindow.Window_DeleteEvent(Object sender, DeleteEventArgs a)

at System.RuntimeMethodHandle.InvokeMethod(ObjectHandleOnStack target, Void** arguments, ObjectHandleOnStack sig, BOOL isConstructor, ObjectHandleOnStack result)

at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)

The issue occurred early this morning, I just had one websession open to a remote system.

If you need any further information just let me know. The issue happens quite frequently so I can provide further logs if needed.

HI all,

just FYI - I'm having the same issue on Fedora 42 with Gnome 48. Strangely the scaling issue was fixed in my homeoffice with the 2026 release. However in the company it is still present. Monitors are the same so it shouldn't be the issue mentioned by Gabriel.

However since this has been bugging me a long time already I found the following workaround. Disabling the experimental features in Gnome helped me resolving the scaling issue (no other sideeffects noticed so far). I can the following command:

"

gsettings set org.gnome.mutter experimental-features "[]"

"

The default settings for this is:

gsettings get org.gnome.mutter experimental-features ['scale-monitor-framebuffer', 'xwayland-native-scaling']

you can restore the settings with

gsettings reset org.gnome.mutter experimental-features

Note sure if this is also working in KDE (i suspect not but I'm still new in the Linux environment).

BR

Hi Hubert,

thanks very much for the quick help and support on this! Really grateful for it!

Best Regards

Sebastian

Hi Hubert,

thanks for getting back to me so quickly!

I´ve tried it with the system time but now I get the following:

$DATE$-$TIME_TEXT_ISO$-$HOST$.log Output: 17.06.2025-074417-10.31.80.113

I assume this is due to the german language setting in my OS (company settings :/ ).

I would assume new variables for day and month with always two digits would make more sense than changing the old ones and confusing people with this change...

Thanks for your help on this!

BR

Sebastian

Good Morning,

came looking for the right way to format my SSH Logs and found this thread.

I´m looking for a way to name my logs as described by Hubert Mireault

2024-05-13-SSH Shell.log

However whatever I do i can´t replicate his output. Any chance you can give me a hint here?

So far I´ve tried:

$DATE_TEXT_ISO$-$TIME_TEXT_ISO$-$HOST$.log Output: 20250616-141213-10.31.80.113.log

$DATE$-$TIME_TEXT_ISO$-$HOST$.log Output: 6_16_2025-141608-10.31.80.113.log

I also tried:

$DATE_YEAR$-$DATE_MONTH$-$DATE_DAY$-$TIME_TEXT_ISO$-$HOST$.log Output: 2025-6-16-141838-10.31.80.113.log (Missing the leading "0" in the Month)

Since I have a couple of systems log into my logstorage and all of them are using the format YYYY-MM--DD-Time-Host I would like to do the same in RDM. What am I missing? I also tried switching the application language and the "use system data time format" checkbox in the usersettings. So far nothing helped.

Any points what to do here?

I´m using RDM on WIn11 in Version 2025.1.41.0 64-bit (JIT)

BR

Sebastian