Solid Edge 2025/Solid Edge X on Fedora 41

[Spirit532]

I'm having a bit of trouble getting Solid Edge X, the cloud SaaS thing, to run under wine on Fedora 41(latest everything as of Nov 19).
The Siemens Software Center installs, but when I attempt to log in, the OAuth redirect in the browser seems to point to 127.0.0.1:0, which indicates that the Software Center fails to bind to the port. In a VM this binds to something in the 6000 range.

I can download the installer via a VM, but installing it doesn't seem to work on Wine Staging(9.21 as of this post). It gets stuck at the "copying files" stage, with wine outputting "tlpWaitForCriticalSection" section "dlls/wbemprox/builtin.c: table.cs" "wait timed out in thread" in a loop.
For some reason, a Steam Proton fork, GE-Proton9-20, installs fine, but only from within steam.

However, running that via WINEPREFIX="$HOME/.path-to-prefix" wine "path-to-prefix/drive_c/Program Files/Siemens/Solid Edge 2025/Program/Edge.exe"

Seems to cause the following error:
0218:fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x20. 0218:fixme:d2d:d2d_device_context_CreateSvgDocument iface 0000000007AD65B0, input_xml_stream 000000000B3FBAE0, svg_document 0000000000A1C460 stub! 0218:fixme:wincodecs:FormatConverter_CanConvert Unsupported source format {6fddc324-4e03-4bfe-b185-3d77768dc900} 0218:fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x20.

None of the icons end up working, and the fonts end up broken. The fonts are probably an easy fix, but the icons I'm not so sure about.

Additionally, because the software center isn't running, it pops up with the cloud gateway sign-in window. The sign-in works, and if I run the gateway directly it seems to say that I have a valid token in the console log, but the "Sign In" button just gets greyed out for a few seconds and then there is no option to launch SE, it just goes back to being active. So I can't actually use the SE X license, only the "Viewer Mode" button works.

Any ideas on what to do with this mess?
@cryinkfly

[Spirit532]

Update. The OAuth login/socket binding issue is resolved by ensuring you have IPv6 enabled. It only agreed to bind to the socket(port 6113) when I had v6 on lo. Still not sure about icons, working on that.