2023.1.5 does not connect xrdp sessions with embedded display
2023.1.5 does not connect xrdp sessions with embedded display
Edit: I just realized that I posted in the wrong forum. could you move this to the Mac support forum? It seems I cannot delete to move the post.
Hi,
After updating to 2023.1.5, I cannot connect xrdp sessions with "embedded display option".
When I try to connect the embedded tab closes without any message or error.
It works with external display option. It was working perfectly in the previous RDP versions.
Moreover, the embedded display also works with Windows RDP sessions.
My environment:
client: RDP 2023.1.5 on M1 MacbookPro
server: xrdp 0.9.7 on Linux(Pop-OS 22.04)
Application log:
[3/19/2023 8:19:03 PM - 2023.1.5.0 64-bit]ERROR Devolutions.FreeRDP.Wrapper.RdpIpcException: NSInvalidReceivePortException: connection went invalid while waiting for a reply
at Devolutions.RemoteConnections.RDPProxyImplementation.Connect () [0x00016] in <19d9edcca77b45f3944ab1eefb07374b>:0
at Devolutions.RemoteConnections.SandboxedRDPSession.Connect () [0x0000b] in <19d9edcca77b45f3944ab1eefb07374b>:0
at Devolutions.RemoteDesktopManager.EmbeddedFreeRDPAPIView.Background_Connect (System.Object sender, System.ComponentModel.DoWorkEventArgs e) [0x0007a] in <ea62e9f482d64f0f81eca9727334dccb>:0
------------------------ extended stack ------------------------
at Devolutions.RemoteDesktopManager.Managers.LogManager.LogError (System.Exception e) [0x00000] in <3b6313c33ddd42b8a1eca0fa8797798c>:0
at Devolutions.RemoteDesktopManager.EmbeddedFreeRDPAPIView.HandleIpcExceptionAndClose (Devolutions.FreeRDP.Wrapper.RdpIpcException ex, System.String message) [0x00000] in <ea62e9f482d64f0f81eca9727334dccb>:0
at Devolutions.RemoteDesktopManager.EmbeddedFreeRDPAPIView.Background_Connect (System.Object sender, System.ComponentModel.DoWorkEventArgs e) [0x00000] in <ea62e9f482d64f0f81eca9727334dccb>:0
at System.ComponentModel.BackgroundWorker.OnDoWork (System.ComponentModel.DoWorkEventArgs e) [0x00000] in <381a4f5c7c4942ca9815982241f9fcae>:0
at System.ComponentModel.BackgroundWorker.WorkerThreadStart (System.Object argument) [0x00000] in <381a4f5c7c4942ca9815982241f9fcae>:0
at System.ComponentModel.BackgroundWorker.<RunWorkerAsync>b__27_0 (System.Object arg) [0x00000] in <381a4f5c7c4942ca9815982241f9fcae>:0
at System.Threading.Tasks.Task.InnerInvoke () [0x00000] in <55335301af774faf8fc40779afb6f275>:0
at System.Threading.Tasks.Task.Execute () [0x00000] in <55335301af774faf8fc40779afb6f275>:0
at System.Threading.Tasks.Task.ExecutionContextCallback (System.Object obj) [0x00000] in <55335301af774faf8fc40779afb6f275>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <55335301af774faf8fc40779afb6f275>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <55335301af774faf8fc40779afb6f275>:0
at System.Threading.Tasks.Task.ExecuteWithThreadLocal (System.Threading.Tasks.Task& currentTaskSlot) [0x00000] in <55335301af774faf8fc40779afb6f275>:0
at System.Threading.Tasks.Task.ExecuteEntry (System.Boolean bPreventDoubleExecution) [0x00000] in <55335301af774faf8fc40779afb6f275>:0
at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00000] in <55335301af774faf8fc40779afb6f275>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00000] in <55335301af774faf8fc40779afb6f275>:0
at ObjCRuntime.Runtime.ThreadPoolDispatcher (System.Func`1[TResult] callback) [0x00000] in <e0c67c5d592a4e828fea9d1c14e1d521>:0
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <55335301af774faf8fc40779afb6f275>:0
Best,
Chungmok
All Comments (4)
Hello
I moved your post to the macOS section of the forum.
I don't currently have a lab environment set up for xrdp to try and reproduce your issue, so while I work on that it could help if you can generate a session log: https://docs.devolutions.net/kb/remote-desktop-manager/how-to-articles/macos-rdm/rdm-mac-enable-send-rdp-logs.
You can send the log to me by PM.
I apologize for the inconvenience. Please let me know if you have further questions or if something isn't clear.
Thanks and kind regards,
Richard Markievicz
Hello
Thanks for sending the logs and extra debug information I asked for.
After taking a second look at your session log and trying this on my side today, I see that the issue relates to the fact you are using RDP security. There was an unfortunate regression on RDP security in our lasted update to FreeRDP.
The good news is that we already had a ticket open for the problem, and I submitted a fix to the RDM Mac team at the end of last week. This should be fixed in the next release. I've noted this forum thread in the ticket so you should get notified once that's available.
In the meantime, using the legacy RDP engine or a different security type could be considered workarounds.
Once again I apologize for the inconvenience. Please let me know if you have further questions or if something isn't clear!
Kind regards,
Richard Markievicz
Hello again
RDM Mac 2023.1.7.0 has been released and contains a fix for this specific issue. Please don't hesitate to post back if you still experience problems after the update, or if you have further issues or questions.
Once again, I apologize for the inconvenience.
Thanks and kind regards,
Richard Markievicz
Hi Richard,
I just installed the new update, and it Is working great!
I was really impressed with how you guys are quick to respond to the issues.
Thanks for the great software and more for the kind answers and fix!
Best,
Chungmok