New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LOOT v0.20.0 crashes on startup when run under Wine #1886
Comments
A LOOT build cross-compiled from Linux to Windows (based on 368e07b so also using Qt 6.5.2) and then run using Wine 8.13 is able to start up: |
Same error here. Arch, sway, fully updated. qt6-base and -wayland installed. |
Same experience here. Version 0.19.1 continues to work fine, though, as you said. |
LOOT 0.20.0 works with Wine in my case but I'm using the flatpak version of Wine 8.0.2 and my distribution is Debian 12 Bookworm. Either Wine 8.0.2 fixed the issue or the flatpak packaging but in any case I can't reproduce this issue. |
Wine 8.13, 0.20.0, the latest artifact, and surprisingly 0.19.1 all fail to start due to:
|
I use MO2, so the flatpak won't do me any good. I've known of the native version for a while, but until we have a high quality native mod manager, I feel like its kind of pointless. |
It's interesting to note however, that 0.19.1 doesn't give me the error when launched through MO2, but it did when launched through the console. |
I can't get either 0.20.0 or 0.19.1 to run, with wine-8.15 on OpenSUSE Tumbleweed, but I get a different error:
Output with full WINE_DEBUG=+all: output.txt.gz And another error for 0.18.6:
0.18.5 starts properly however |
Closing this as wontfix as there's now a native Linux release available on Flathub, and there's not really anything LOOT can do about Qt using Windows APIs that Wine doesn't implement (aside from downgrade to an older version of Qt, but that's not desirable as it means missing out on bug fixes and new features). |
Reopening this as it's still relevant to MO2 users on Linux, as MO2 runs under Wine and so running LOOT through it needs a Windows LOOT build. |
I have tried out the latest available stable version of proton and a later (staged) version but everytime loot is crashing. This proton prefix works with mo2 and other programs. All the messages shown during start have nothing to do with the crash. Here are the collected issue report and merge request (for wine) that could solve the issue (I do not build wine myself): Summary: I need to downgrade loot to a version that does not use Qt 6.5 (and can't build later version with QT 6.4 myself since I don't have windows). (Linux version can't obviously not be used from mo2). Workaround: Use Loot 0.19.1 or find a build service (by forking loot) that builds 0.22.0 with Qt6.4. Host system: Ubuntu 22.04. Started from within MO2 as well as alone from command line (same behaviour). Update: A local setup with crosscompiler might be possible to get Loot to build (with windows qt6.4 and all it's build dependencies as windows binaries). |
The patch has been merged and should be included in next week's wine release. |
Looks like this is fixed as of Wine 8.21, so closing this. |
doesn't work for me still. loot 0.20 - 0.22, wine-staging 8.21-1. ah, noticed you need the flatpak version now. How do you run that from within MO2? never used flatpak, and the instructions on the LOOT page say you run it from command line rather than from within MO2. |
Can you share your logs? |
[2023-12-01 23:38:19.275 D] spawning binary: I have a qt.conf in the same folder as loot with |
No, the Flatpak version is a Linux build, if you're trying to run LOOT through Wine then you still need the Windows build.
@kleshas have you tried without this |
Same error as above, with the extra lines: |
Just adding to this thread - so, the windows version runs on Linux, by running it through the system's WINE however trying to run it through MO2 on Proton (see: https://github.com/rockerbacon/modorganizer2-linux-installer ), it just does not run. Click run in MO2 and nothing. |
@cprin21 It does not run on proton since Valve has not integrated any wine patches after january 23. You will either need to wait or build proton yourself (proton tkg). If you're lucky you can use one of the nightly builds with MO2. |
First reported on Discord here. LOOT v0.19.1 works. This was confirmed here to be due to the update to Qt 6.5.1 in 638c8a2. Here's an excerpt from the Wine trace that was shared:
crash.txt
This looks like something that Wine will need to fix, or maybe a future Qt release will change the implementation in a way that doesn't trigger this bug. 6.5.2 is available so it would be good to retry this once LOOT has been updated to that.
The text was updated successfully, but these errors were encountered: