RDM Closes when rightclick on RDP Session
Hi,
If right-click on a RDP Tab, the program closes without any further error messages.
My System:
Kubuntu 24.10
KDE Plasma 6.1.5
RDP is not in Sandbox Mode.
Here is the output from the Terminal:
(RemoteDesktopManager:1353595): Gtk-CRITICAL **: 11:06:38.305: gtk_widget_grab_default: assertion 'gtk_widget_get_can_default (widget)' failed
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.416: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.420: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.430: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.433: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.435: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.444: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.462: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.466: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.475: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.481: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
(RemoteDesktopManager:1353595): Gtk-WARNING **: 11:06:38.506: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton
[11:06:53:960] [1353595:0014a835] [INFO][Devolutions.Rdp.Credentials] - [Parse]: parsing "a*****", "t****.n**" (Mstsc) => "Username: "a*****" Domain: "t****.n**""
[11:06:53:962] [1353595:0014a835] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0
[11:06:53:962] [1353595:0014a835] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0
[11:06:53:962] [1353595:0014a835] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0
[11:06:53:305] [1353595:0014a835] [WARN][com.freerdp.core.nego] - [nego_enable_aad]: This build does not support AAD security, disabling.
[11:06:54:040] [1353595:0014a835] [WARN][com.freerdp.core.license] - [license_read_binary_blob_data]: license binary blob::type BB_ERROR_BLOB, length=0, skipping.
[11:06:54:091] [1353595:0014a835] [INFO][com.freerdp.gdi] - [gdi_init_ex]: Local framebuffer format PIXEL_FORMAT_BGRX32
[11:06:54:091] [1353595:0014a835] [INFO][com.freerdp.gdi] - [gdi_init_ex]: Remote framebuffer format PIXEL_FORMAT_BGRA32
[11:06:54:092] [1353595:0014adbe] [INFO][com.freerdp.channels.rdpdr.client] - [devman_load_device_service]: Loading device service drive [home] (static)
[11:06:54:092] [1353595:0014adbe] [INFO][com.freerdp.channels.rdpdr.client] - [devman_load_device_service]: Loading device service drive [home] (static)
[11:06:54:093] [1353595:0014a835] [INFO][com.freerdp.channels.rdpsnd.client] - [rdpsnd_load_device_plugin]: [static] Loaded alsa backend for rdpsnd
[11:06:54:093] [1353595:0014a835] [INFO][com.freerdp.channels.drdynvc.client] - [dvcman_load_addin]: Loading Dynamic Virtual Channel ainput
[11:06:54:093] [1353595:0014a835] [INFO][com.freerdp.channels.drdynvc.client] - [dvcman_load_addin]: Loading Dynamic Virtual Channel rdpsnd
[11:06:54:093] [1353595:0014a835] [INFO][com.freerdp.channels.drdynvc.client] - [dvcman_load_addin]: Loading Dynamic Virtual Channel rdpgfx
[11:06:54:094] [1353595:0014a835] [INFO][com.freerdp.channels.drdynvc.client] - [dvcman_load_addin]: Loading Dynamic Virtual Channel disp
[11:06:54:094] [1353595:0014a835] [WARN][com.winpr.thread] - [SetThreadPriority]: pthread_setschedprio(0) not implemented, requires POSIX 2008 or later
[11:06:55:457] [1353595:0014adc3] [INFO][com.freerdp.channels.rdpsnd.client] - [rdpsnd_load_device_plugin]: [dynamic] Loaded alsa backend for rdpsnd
[11:06:55:160] [1353595:0014adc3] [INFO][com.freerdp.channels.rdpsnd.client] - [rdpsnd_load_device_plugin]: [dynamic] Loaded alsa backend for rdpsnd
[11:06:56:346] [1353595:0014adbe] [INFO][com.freerdp.channels.rdpdr.client] - [device_announce]: registered [ drive] device #1: home (type=8 id=1)
[11:06:56:346] [1353595:0014adbe] [INFO][com.freerdp.channels.rdpdr.client] - [device_announce]: registered [ drive] device #2: home (type=8 id=2)
[11:06:56:408] [1353595:0014adc3] [WARN][com.freerdp.channels.drdynvc.client] - [check_open_close_receive]: {Microsoft::Windows::RDS::DisplayControl:18} OnOpen=(nil), OnClose=0x72d8a603f9a0
(RemoteDesktopManager:1353595): Gdk-CRITICAL **: 11:07:05.603: gdk_window_get_effective_parent: assertion 'GDK_IS_WINDOW (window)' failed
(RemoteDesktopManager:1353595): Gdk-CRITICAL **: 11:07:05.603: gdk_window_has_native: assertion 'GDK_IS_WINDOW (window)' failed
(RemoteDesktopManager:1353595): Gdk-WARNING **: 11:07:05.652: Tried to map a popup with a non-top most parent
Speicherzugriffsfehler (Speicherabzug geschrieben)
Any Ideas?
Kind regards
Alexander
All Comments (11)
System:
Fedora 40
Linux foo 6.12.7-100.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Dec 27 17:00:45 UTC 2024 x86_64 GNU/Linux
KDE Plasma
6.2.4
(Note: This was working last week without an issue under Fedora 39, unsure of version of Plasma.)
Similar experience when trying to right click on the tab to change settings once connected. The menu will open but within a second or two RDM entirely crashes with the following:
(RemoteDesktopManager:13659): Gdk-CRITICAL **: 10:06:45.544: gdk_window_get_effective_parent: assertion 'GDK_IS_WINDOW
(window)' failed
(RemoteDesktopManager:13659): Gdk-CRITICAL **: 10:06:45.544: gdk_window_has_native: assertion 'GDK_IS_WINDOW (window)'
failed
Segmentation fault (core dumped)
Hi there.
I'll start looking into this issue right away. I am the only member of our team able to reproduce it, but I am also the only one among us to use KDE Plasma as my DE (Arch Linux). So I assume this issue only occurs on KDE. I will update this thread when I figure out what causes this issue.
Regards.
Nicolas Parr
Not much detail to give here but I have been able to kind of "work around" this by having the window start undocked and not in full screen. Then I can manually right click and select the likes of smart sizing. So far that method has not crashed.
Hi again.
Just a little update: the cause of this issue has been found and will be resolved in the next release. We do not yet have a date in mind, but I will update this thread when we do. Sorry for the inconvenience.
Best regards.
Nicolas Parr
Awesome, thank you!
Hi, Thank you!
Hi again.
Just a little update: the cause of this issue has been found and will be resolved in the next release. We do not yet have a date in mind, but I will update this thread when we do. Sorry for the inconvenience.
Best regards.
I just want to add here that it is not KDE specific since I get the same issue while running in Gnome. I'd be interested to hear what the core issue is while we wait for the update. This bug has been the one things preventing me from going all in on Linux on my work laptop instead of Windows
Hi,
A fix for this issue has been released in the new version (2024.3.2.13).
Let us know if it works for you.
Regards,
Gabriel Dubois
I just want to add here that it is not KDE specific since I get the same issue while running in Gnome. I'd be interested to hear what the core issue is while we wait for the update. This bug has been the one things preventing me from going all in on Linux on my work laptop instead of Windows
While this is not something that any member of our team has been able to reproduce, I would assume that it's the same cause and the latest release should have fixed it. Please, let us know if the issue persists, send us some logs and we will investigate further.
Best regards
Nicolas Parr
I believe it's fixed. I have not seen the issue reoccur since I updated. Thank you guys
I can also confirm, that it is fixed.