I dumped Windows about 6 months ago and have not had a moment of regret. But our volunteer fire department just started using a Windows (only) tool for managing call outs etc.

I’m running Debian 13.3 and the Wine 10.0 from Debian.

I’ve played around a bit and worked through a few minor issues and can now run the various apps that ship with Wine - including iexplorer with network.

But when I try to run the one app I need, I get the following text:

[372:0115/144659.223:ERROR:network_change_notifier_win.cc(224)] WSALookupServiceBegin failed with: 0
[372:0115/144659.337:ERROR:network_sandbox.cc(302)] Failed to grant sandbox access to cache directory C:\users\[Redacted]\AppData\Roaming\fireq-desktop\Cache\Cache_Data: Procedure not found. (0x7F)
[372:0115/144659.338:ERROR:network_sandbox.cc(396)] Failed to grant sandbox access to network context data directory C:\users\[Redacted]\AppData\Roaming\fireq-desktop\Network: Success. (0x0)
02a0:err:ole:com_get_class_object class {7ab36653-1796-484b-bdfa-e74f1db7c1dc} not registered
02a0:err:ole:create_server class {7ab36653-1796-484b-bdfa-e74f1db7c1dc} not registered
02a0:err:ole:com_get_class_object no class object {7ab36653-1796-484b-bdfa-e74f1db7c1dc} could be created for context 0x5
023c:err:ole:com_get_class_object class {aa509086-5ca9-4c25-8f95-589d3c07b48a} not registered
023c:err:ole:com_get_class_object class {aa509086-5ca9-4c25-8f95-589d3c07b48a} not registered
023c:err:ole:create_server class {aa509086-5ca9-4c25-8f95-589d3c07b48a} not registered
023c:err:ole:com_get_class_object no class object {aa509086-5ca9-4c25-8f95-589d3c07b48a} could be created for context 0x17
[372:0115/144659.459:ERROR:network_service_instance_impl.cc(265)] Encountered error while migrating network context data or granting sandbox access for C:\users\[Redacted]\AppData\Roaming\fireq-desktop\Network. Result: 11: Success. (0x0)
[636:0115/144659.710:ERROR:network_change_notifier_win.cc(224)] WSALookupServiceBegin failed with: 0
01c8:err:d3d:wined3d_context_gl_set_pixel_format wglSetPixelFormatWINE failed to set pixel format 1 on device context 000000000501005D.
[636:0115/144700.128:ERROR:tcp_socket_win.cc(861)] connect failed: 10051
[636:0115/144700.129:ERROR:tcp_socket_win.cc(861)] connect failed: 10051
[636:0115/144700.129:ERROR:tcp_socket_win.cc(861)] connect failed: 10051
[636:0115/144700.129:ERROR:tcp_socket_win.cc(861)] connect failed: 10051
[704:0115/144711.603:ERROR:crashpad_client_win.cc(844)] not connected

The application opens, but just displays an empty window. I’m guessing it’s trying to connect to their server before doing something else.

I believe the app I’m trying to run is electron based and my searches show that this has historically been an issue and I’ve tried a few of the hints I found - even though they were years old and for old versions of Wine.

I know it’s a long shot, but do these error messages suggest anything obvious that I should try?

  • erinsdaddyEnglish
    6·
    13 days ago

    You’ve got several problems happening here, but the ones causing the app to just “not load” are sandbox related.

    02a0:err:ole:com_get_class_object class {7ab36653-1796-484b-bdfa-e74f1db7c1dc} not registered: This is related to an attempt to use spellcheck in the app itself: https://strontic.github.io/xcyclopedia/library/clsid_7AB36653-1796-484B-BDFA-E74F1DB7C1DC.html

    023c:err:ole:com_get_class_object class {aa509086-5ca9-4c25-8f95-589d3c07b48a} not registered: This is a WinRT API thing. Both of these are core Windows libraries that electron is trying to use. Would recommend making sure your wine settings are mirroring what would be required for a chrome emulation. See: https://strontic.github.io/xcyclopedia/library/clsid_aa509086-5ca9-4c25-8f95-589d3c07b48a.html

    The real issue that nothing loads is the network sandbox. Additionally, it’s unable to access the GPU from the sandbox. You can try a few things:

    wine /path/to/your/app.exe --no-sandbox

    wine /path/to/your/app.exe --disable-gpu --no-sandbox <-- only software rendering, not ideal for performance, but may be fine

    WINEDLLOVERRIDES="libglesv2.dll=d" wine /path/to/your/app.exe --disable-gpu --no-sandbox <— overrides the default GL implementation for compatibility

    Additionally, FireQ has a web-browser only version – can you actually do what you need to do without the native app from their cloud version and just run a web browser? Completely kill the need for the app.

    And finally: how are you configuring wine and running it? I’d recommend checking out something like bottles to manage individual settings on a per-app basis for wine: https://usebottles.com/

    • Great Blue Heron@lemmy.caOPEnglish
      1·
      13 days ago

      Thank you for your detailed response. I had previously found a page with instructions for running electron apps and tried the “WINEDLLOVERRIDES=“libglesv2.dll=d” wine /path/to/your/app.exe --disable-gpu --no-sandbox”. Unfortunately, it does not help. Strangely, it still gives the “Failed to grant sandbox access…” error, and the others but then goes into a loop of lots of “Exiting GPU process due to errors during initialization” - so at least we know it is parsing the additional options.

      I got a bit excited when you pointed out the web version. Unfortunately, all the web version has is links to download the apps for various platforms.

      I’m just running Wine from the command line for now. As this is the only Windows app I need I don’t see why I need an extra app, like bottles, to manage the configuration.

      As FireQ is an electron app, am I right in understanding that it should be close to trivial for them to ship a Linux version if they already have Windows and MacOS? They seem fairly willing to help - maybe I’ll offer to test a Linux build for them.

  • e0qdk@reddthat.comEnglish
    2·
    14 days ago

    Does it need to be run on a VPN or something, maybe? If I’m interpreting connect failed: 10051 correctly, it can’t reach the network.

    • Great Blue Heron@lemmy.caOPEnglish
      3·
      14 days ago

      Does not need a VPN or similar. I believe the “connect failed” messages are a symptom. I think the real problem is the “Failed to grant sandbox access to network…” or “ERROR:network_service_instance_impl.cc(265)] Encountered error while migrating network…” above.

      • e0qdk@reddthat.comEnglish
        3·
        14 days ago

        Hmm. You might be able to turn off the sandboxing by passing “–no-sandbox” as an argument on the command-line (depending on how the app is set up to launch), but some search results I’ve found suggest something’s already gone wrong by the first line and there may just be a bug with logging in old versions of Chromium…

        Do you already know what this app is supposed to do? If it just loads a website (and doesn’t interface with local files/hardware), you might try to see if you can figure out what it’s accessing and load it directly in a regular browser instead. Alternatively, if it’s not bundled up in some annoying way (or shipped with custom DLLs for Windows), it might be possible to copy the scripts out and just run them under a Linux version of Electron?

  • onlinepersonaEnglish
    2·
    14 days ago

    You can try winboat but it’s quite heavy. Basically runs windows in a container and passes access through to it. Apps can be installed in it and have seamless integration with your desktop.

    Alternatively, you can also talk to your group and look around for alternatives.

  • FeydEnglish
    1·
    14 days ago

    Don’t have a quick answer but I would guess that is an electron app so maybe there is some troubleshooting in that direction