[Bug]: Client 3.14.0/3.14.1 crash in RDP session.

[sjmoller]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

When I RDP to the Win10 client, the Nextcloud client crashes.
If I login directly on the client, the Nextcloud client starts normally.
I made sure my VC++ 2015-2022 x64/x86 is up2date (vm3dgl64.dll).
This is a fresh install of the 3.14.1 client.
nextcloud-3.13.4 works.

Found i EventLog-Application:

Faulting application name: nextcloud.exe, version: 3.14.1.55839, time stamp: 0x66f6776f
Faulting module name: vm3dgl64.dll, version: 3.6.0.0, time stamp: 0x66a16726
Exception code: 0xc0000005
Fault offset: 0x0000000000e3696d
Faulting process id: 0x2958
Faulting application start time: 0x01db130d5d0e75e5
Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe
Faulting module path: C:\WINDOWS\SYSTEM32\vm3dgl64.dll
Report Id: f052a978-a246-491f-8359-7d03d963426f
Faulting package full name:
Faulting package-relative application ID:

Steps to reproduce

RDP to the client host.

Expected behavior

Nextcloud client 3.14.x crashes.

Which files are affected by this bug

nextcloud.exe

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Official Windows MSI

Nextcloud Server version

30.0.0

Nextcloud Desktop Client version

3.14.1

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

Not server related

Additional info

No response

[mgallien]

looks like a crash from the graphics API that is being used by the UI
would be worth investigating if you can find a workaround following the steps there:

• debug logs: https://doc.qt.io/qt-6/qrhi.html#error-reporting
• select alternate rendering backend https://doc.qt.io/qt-6/qtquick-visualcanvas-scenegraph-renderer.html#rendering-via-the-qt-rendering-hardware-interface