shawniverson

Yes, this is how we are working around the issue currently. Git sync picks it up afterwards.

Upload is done.

In this case the status is modified, since I made a change in an existing file.

I cannot send the zip using any method. The size is over 100mb. The forum limits to 25mb, and email limits to 35mb.

1. Files are still listed on commit page after refreshing, as though the commit never happened.

2. External Git is enabled

3. One file

I'll send the zip file shortly.

Hello @Michel Audi ,

Should I open a case with Devolutions to submit the zip file? I don't want to attach it here in the public forum.

After upgrading to Powershell Universal 2026.3.0, we couldn't commit any changes to git in the Admin panel. Adding a commit message and clicking the button does nothing, and immediately following the attempt, all UI elements become unresponsive, such as items on the scope pane, so you cannot navigate away without refreshing the whole page.

Upgrading to 2026.3.3 did not resolve the problem. Running on Windows. Problem persists in all browsers (Firefox, Chrome, Edge).

Followup to this report. We determined that the problem is not a bug. Another platform was calling the endpoint over and over recursively and overwhelming the endpoint service. We fixed the problem with the other platform and everything is back to normal.

Our Powershell Universal has been upgraded from 2026.2.3 from 2026.1.2. After upgrade, our API endpoints started encountering gateway timeouts. It seems that executing commands as simple as "Get-PSUSchedule -Integrated" in a custom API Endpoint hang or take excessively long to execute. The same command executed in the same environment in script or locally on the server takes about 20 seconds to execute. I increased the API endpoint timeout to 300s here and it still timed out.

2026-08-11 09:14:17.262 -04:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/1.1 GET <redacted> - null null

2026-08-11 09:14:17.265 -04:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint 'GET:<redacted>'

2026-08-11 09:14:17.287 -04:00 [INF][] GET /logicmonitorcheck <redacted>026-08-11 09:19:21.245 -04:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint 'GET:<redacted>'

2026-08-11 09:19:21.245 -04:00 [ERR][Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware] An unhandled exception has occurred while executing the request.

Grpc.Core.RpcException: Status(StatusCode="Cancelled", Detail="Call canceled by the client.", DebugException="System.OperationCanceledException: The operation was canceled.")

---> System.OperationCanceledException: The operation was canceled.

--- End of inner exception stack trace ---

at ProtoBuf.Grpc.Internal.Reshape.UnaryTaskAsyncImpl[TRequest,TResponse](AsyncUnaryCall`1 call, MetadataContext metadata, CancellationToken cancellationToken)

at PowerShellUniversal.Api.ApiGrpc.ExecuteAsync(ApiRequest request, CancellationToken cancellationToken) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal.Api\ApiGrpc.cs:line 193

at PowerShellUniversal.Api.ApiService.ExecuteEndpointAsync(HttpContext httpContext, Endpoint endpoint, Dictionary`2 variables) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal.Api\ApiService.cs:line 792

at PowerShellUniversal.Api.ApiService.ExecuteAsync(HttpContext httpContext, Endpoint endpoint) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal.Api\ApiService.cs:line 504

at Universal.Server.Routing.ApiEndpointSource.HandleAsync(HttpContext context, Endpoint endpoint) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Routing\ApiEndpointSource.cs:line 77

at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|7_0(Endpoint endpoint, Task requestTask, ILogger logger)

at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)

at PowerShellUniversal.FeatureMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Middleware\FeatureMiddleware.cs:line 42

at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext()

--- End of stack trace from previous location ---

at PowerShellUniversal.DisallowedModeMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Middleware\ModeMiddleware.cs:line 25

at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext()

--- End of stack trace from previous location ---

at PowerShellUniversal.CspMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Middleware\CspMiddleware.cs:line 28

at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext()

--- End of stack trace from previous location ---

at Universal.Server.Middleware.RoutingMiddleware.Invoke(HttpContext httpContext, IPolicyEvaluator policyEvaluator) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Middleware\RoutingMiddleware.cs:line 165

at PowerShellUniversal.PSUMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Middleware\PowerShellMiddleware.cs:line 15

at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext()

--- End of stack trace from previous location ---

at Universal.Server.Middleware.RegexApiMiddleware.Invoke(HttpContext httpContext, IApiService apiService) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Middleware\RegexApiMiddleware.cs:line 19

at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)

at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)

at Universal.Server.Middleware.WindowsAuthMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Middleware\WindowsAuthMiddleware.cs:line 58

at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext()

--- End of stack trace from previous location ---

at Universal.Server.Middleware.SwaggerAuthenticationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Middleware\SwaggerAuthMiddleware.cs:line 51

at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext()

--- End of stack trace from previous location ---

at Universal.Server.Middleware.McpAuthenticationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Middleware\McpAuthenticationMiddleware.cs:line 30

at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext()

--- End of stack trace from previous location ---

at StackExchange.Profiling.MiniProfilerMiddleware.Invoke(HttpContext context) in C:\projects\dotnet\src\MiniProfiler.AspNetCore\MiniProfilerMiddleware.cs:line 112

at AspNetCoreRateLimit.RateLimitMiddleware`1.Invoke(HttpContext context) in D:\a\powershell-universal\powershell-universal\src\AspNetCoreRateLimit\Middleware\RateLimitMiddleware.cs:line 109

at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)

at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)

at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.<Invoke>g__Awaited|10_0(ExceptionHandlerMiddlewareImpl middleware, HttpContext context, Task task)

2026-08-11 09:19:21.246 -04:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/1.1 GET <redacted> - 500 null text/plain 299970.7853ms

No crashes or corrupt clipboard text so far!

This is great news! You were able to find the issue? I will update it and give it a try!

@Carl Marien File uploaded

Hello @Carl Marien, I have another recording of RDM locking up during a clipboard operation (Ctrl+X cut of text). I can upload it to you as well.

I was able to capture the clipboard corruption in action, but I couldn't get it to crash during that time. I think it depends on what is being copied and how the corruption ends up before RDM hangs and crashes. I uploaded the video.

Hello,

I never received a private message, and I am in a spot where I think I can reproduce the issue repeatedly. I'll get a screen recording going to demonstrate the problem.

I have new information regarding this issue.

I frequently copy text from web browser web pages within RDP sessions and the local machine.

It appears that this issue may be related specifically to copy paste of text inside of browsers. More specifically, text that includes formatting metadata. After suspecting this, I had it happen in Firefox on a Windows Server RDP session when I copied a table. I copied text and my local KDE clipboard showed this gibberish:

敖獲潩㩮⸰ഹ匊慴瑲呈䱍〺〰〰㐱ള䔊摮呈䱍〺〰㔰㜹ഷ匊慴瑲牆条敭瑮〺〰〰㜱ഷ䔊摮牆条敭瑮〺〰㔰㐹റ匊畯捲啥䱒栺瑴獰⼺瀯灵椮祶整档攮畤甯敳汲潯畫൰㰊瑨汭㰾潢祤ാ㰊ⴡ匭慴瑲牆条敭瑮ⴭ㰾慴汢⁥潲敬∽慴汢≥挠慬獳∽畍呩扡敬爭潯⁴獣⵳湥昱眴•摩∽㐰ㅡ㌰〹愭㙣ⵣ㤴戴㠭摢ⴳ㕤昱㑤㝢搴㝢㸢琼潢祤挠慬獳∽畍呩扡敬潂祤爭潯⁴獣⵳㙹ㅪ祭•潲敬∽潲杷潲灵㸢琼⁲汣獡㵳䴢極慔汢剥睯爭潯⁴獣⵳潣㕪∷爠汯㵥爢睯㸢琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢啐䅐瑵㱯琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩乧湯⁥畍呩扡敬敃汬猭穩䵥摥畩獣⵳㠱橡㥹≲爠汯㵥挢汥≬䰾捯瑡潩桃湡敧⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬匾獹整獭传晦捩ⵥ瑳晡⁦摡敤㱤琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢㌰㌭ⴰ〲㘲ㄠ㨲㈱〺㰵琯㹤⼼牴㰾牴挠慬獳∽畍呩扡敬潒⵷潲瑯挠獳挭橯㜵•潲敬∽潲≷㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬倾偕畁潴⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮潎敮䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ愸祪爹•潲敬∽散汬㸢潌慣楴湯䌠慨杮㱥琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢湉楤湡灡汯獩匭慴晦爠浥癯摥⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬〾ⴳ〳㈭㈰‶㈱ㄺ㨲㔰⼼摴㰾琯㹲琼⁲汣獡㵳䴢極慔汢剥睯爭潯⁴獣⵳潣㕪∷爠汯㵥爢睯㸢琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢啐䅐瑵㱯琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩乧湯⁥畍呩扡敬敃汬猭穩䵥摥畩獣⵳㠱橡㥹≲爠汯㵥挢汥≬䰾捯瑡潩桃湡敧⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬䄾潤敢䔭灭潬敹ⵥ捁潲慢側潲中浡摥䴭湡慵敲潭敶㱤琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢㌰㌭ⴰ〲㘲ㄠ㨲㈱〺㰵琯㹤⼼牴㰾牴挠慬獳∽畍呩扡敬潒⵷潲瑯挠獳挭橯㜵•潲敬∽潲≷㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬倾偕畁潴⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮潎敮䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ愸祪爹•潲敬∽散汬㸢潌慣楴湯䌠慨杮㱥琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢浅汰祯敥湁⁹敲潭敶㱤琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢㌰㌭ⴰ〲㘲ㄠ㨲㈱〺㰵琯㹤⼼牴㰾牴挠慬獳∽畍呩扡敬潒⵷潲瑯挠獳挭橯㜵•潲敬∽潲≷㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬倾偕畁潴⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮潎敮䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ愸祪爹•潲敬∽散汬㸢潌慣楴湯䌠慨杮㱥琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢瑓晡佦汮⁹敲潭敶㱤琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢㌰㌭ⴰ〲㘲ㄠ㨲㈱〺㰵琯㹤⼼牴㰾牴挠慬獳∽畍呩扡敬潒⵷潲瑯挠獳挭橯㜵•潲敬∽潲≷㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬倾偕畁潴⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮潎敮䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ愸祪爹•潲敬∽散汬㸢潌慣楴湯䌠慨杮㱥琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢穁牵ⵥ卓ⵏ慃瑮䍯湯畳敭⁲敲潭敶㱤琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢㌰㌭ⴰ〲㘲ㄠ㨲㈱〺㰵琯㹤⼼牴㰾牴挠慬獳∽畍呩扡敬潒⵷潲瑯挠獳挭橯㜵•潲敬∽潲≷㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬倾偕畁潴⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮潎敮䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ愸祪爹•潲敬∽散汬㸢潌慣楴湯䌠慨杮㱥琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢摁楶潳⁲敲潭敶㱤琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢㌰㌭ⴰ〲㘲ㄠ㨲㈱〺㰵琯㹤⼼牴㰾牴挠慬獳∽畍呩扡敬潒⵷潲瑯挠獳挭橯㜵•潲敬∽潲≷㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬倾偕畁潴⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮潎敮䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ愸祪爹•潲敬∽散汬㸢潌慣楴湯䌠慨杮㱥琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢卆䤭摮慩慮潰楬⵳䍅䱅汩祬片湡⵴坒爠浥癯摥⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬〾ⴳ〳㈭㈰‶㈱ㄺ㨲㔰⼼摴㰾琯㹲琼⁲汣獡㵳䴢極慔汢剥睯爭潯⁴獣⵳潣㕪∷爠汯㵥爢睯㸢琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩䑧晥畡瑬䴠極慔汢䍥汥⵬楳敺敍楤浵挠獳ㄭ瑶渹捩•潲敬∽散汬㸢啐䅐瑵㱯琯㹤琼⁤汣獡㵳䴢極慔汢䍥汥⵬潲瑯䴠極慔汢䍥汥⵬潢祤䴠極慔汢䍥汥⵬慰摤湩乧湯⁥畍呩扡敬敃汬猭穩䵥摥畩獣⵳㠱橡㥹≲爠汯㵥挢汥≬䰾捯瑡潩桃湡敧⼼摴㰾摴挠慬獳∽畍呩扡敬敃汬爭潯⁴畍呩扡敬敃汬戭摯⁹畍呩扡敬敃汬瀭摡楤杮敄慦汵⁴畍呩扡敬敃汬猭穩䵥摥畩獣⵳瘱㥴楮≣爠汯㵥挢汥≬䘾ⵓ湉楤湡灡汯獩䔭䕃楌汬䝹慲瑮䐭⁏敲潭敶㱤琯㹤⼼牴㰾琯潢祤㰾琯扡敬㰾ⴡ䔭摮牆条敭瑮ⴭാ㰊戯摯㹹਍⼼瑨汭>

I immediately opened Notepad in the RDP session and pasted into it:

PUPAuto Location Change <REDACTED> added 03-30-2026 12:12:05

PUPAuto Location Change <REDACTED> removed 03-30-2026 12:12:05

PUPAuto Location Change <REDACTED> removed 03-30-2026 12:12:05

PUPAuto Location Change <REDACTED> removed 03-30-2026 12:12:05

PUPAuto Location Change <REDACTED> removed 03-30-2026 12:12:05

PUPAuto Location Change <REDACTED> removed 03-30-2026 12:12:05

PUPAuto Location Change <REDACTED> removed 03-30-2026 12:12:05

PUPAuto Location Change <REDACTED> removed 03-30-2026 12:12:05

PUPAuto Location Change <REDACTED> removed

So, the remote RDP clipboard was okay, but the one on my local machine was not. I then re-copied the text from the notepad session, and then the copy in my KDE clipboard was good. This of course stripped metadata from the copied text.

I am wondering if RDM is having trouble parsing metadata on copied content properly, since copying from a web page includes more than just text itself but also text metadata representing fonts, tables, etc.

I'm going to try various things to try to isolate the problem. I had the clipboard corruption happen this morning, but this one didn't crash RDP. I copied the same text 3 times inside the RDP session, the first two times the corruption happened identically (same garbled text both times), and then it was fine the third time. I was only observing the local Linux clipboard. I'll observe both next time.

I'll also add it is random. I can sometimes go all day without issues, but then randomly it will occur. It also looks like it can happen in both directions. I've had corrupted text inside of my RDP session from text coming from my Linux host and corrupted text in my local clipboard coming from the RDP session.

In fact, it just happened again, and for giggles I copied my clipboard out and repopulated it since it wasn't garbled. I was able to then launch RDM without it crashing with the same clipboard contents, which is really odd and supports the idea that it is happening intermittently.

It doesn't seem to matter what I am copying, and I am wondering it is very specific to me using KDE on Debian.

Looks like issue isn't resolved, here's a garbled clipboard entry using copy/paste in an RDP session:

敖獲潩㩮⸰ഹ匊慴瑲呈䱍〺〰〰㤱ര䔊摮呈䱍〺〰〰㤲ഴ匊慴瑲牆条敭瑮〺〰〰㈲ഴ䔊摮牆条敭瑮〺〰〰㔲സ匊畯捲啥䱒栺瑴獰⼺瀯灵椮祶整档攮畤愯浤湩愯瑵浯瑡潩⽮捳敨畤敬⽳敒潭敶䈭潲敫卮䑉匭档摥汵⽥潪獢਍格浴㹬戼摯㹹਍ℼⴭ瑓牡䙴慲浧湥⵴㸭猼慰㹮⼳㠱㈯㈰‶㈱ㄺ㨲㔲䄠㱍猯慰㹮ℼⴭ湅䙤慲浧湥⵴㸭਍⼼潢祤ാ㰊栯浴㹬�

The quoted text above is what was in my clipboard. Had to redact some info in it.

It appears after updating to 2026.1.0.8, the problem has lessened. However, it has not eliminated the problem. I currently have content in the local clipboard that caused my RDP sessions to crash and that is crashing RDM upon launch. I am unable to determine if the text is garbled since I cannot successfully launch RDM with this content. Clearing the local clipboard allowed RDM to launch again normally.

"There were problems decrypting some credentials.

Click OK to copy the details to the clipboard.

Credentials profiles:

REDACTED: REDACTED (File) [Failed to decrypt using REDACTED credential]

"

OS and desktop environment

Debian Bookworm 2.13

Kernel 6.1.43-amd64

KDE Plasma 5.27.5

KDE Frameworks 5.103.0

Qt 5.15.8

Wayland

Remote Desktop Manager 2025.3.2.2 64-bit

When an RDP session is established using RDM, RDM may freeze and eventually silently exit after copying text to the clipboard. Frequently, the copied text, if successfully copied, will paste into the RDP session in a corrupted form, often consisting of seemingly random unicode characters. It seems that this clipboard data corruption sometimes triggers a sequence of characters that causes RDM to crash. Furthermore, if the text that caused RDM to crash is left in the clipboard, relaunching RDM will result in the application immediately crashing on launch until the clipboard is cleared. The text in the clipboard on the Linux host remains clean and uncorrupted throughout this occurring from the perspective of the Linux host.

I plan to try reproducing this issue on Debian Trixie when I get a chance. I will post results here when I do that. Also, I will capture screenshots of the clipboard corruption and upload them as well.