From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] MangoHud Completely Broken on Lutris since 0.6.7.1_1, Causing CTD of the entire Wine-Stack
Date: Tue, 31 May 2022 18:59:03 +0200 [thread overview]
Message-ID: <20220531165903.I-uxCuNhd0IusZfgyeTEl8geEAl7Lsz42egf4KTydkU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37365@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3808 bytes --]
Closed issue by TeusLollo on void-packages repository
https://github.com/void-linux/void-packages/issues/37365
Description:
Warning: This issue has also been posted to MangoHud developers, here. As such, there's some degree of copy-paste:
https://github.com/flightlessmango/MangoHud/issues/776
### System
* xuname:
Void 5.15.41_1 x86_64 GenuineIntel uptodate rFFFF
GPU Architecture: AMD Polaris 20 GPU on GCN 4.0 architecture
Drivers: AMDGPU OpenSource + MESA RADV + AMD RADV OpenSource
Libraries: Mesa 21.3.7, Mesa-Dri 21.3.7 Mesa-Vulkan-Radeon 21.3.7, Mesa-Vulkan-Overlay-Layer 21.3.7
* package:
MangoHud-0.6.7.1_1
MangoHud-32bit-0.6.7.1_1
### Expected behavior
MangoHud Used to work perfectly on package version MangoHud-0.6.5_1 when run through the Lutris interface. It would manifest itself as an overlay into a compatible application run through the Wine-Stack.
### Actual behavior
CTD to desktop of the entire Wine-Stack and Wine-Server when MangoHud is enabled through the Lutris advanced interface (Output below). If MangoHud is simply disabled into the Lutris advanced interface, none of that happens, yet obviously this prevents actual MangoHud usage.
### Steps to reproduce the behavior
Currently, MangoHud appears completely non-functional since v. 0.6.7.1 update on my system, causing CTDs.
When trying to run a Windows application on Lutris through Wine, with MangoHud enabled through the Lutris advanced interface, I get an output similar to this (My actual username was redacted and replaced with a generic "Username"), and subsequently a CTD of the entire Wine-Stack and Wine-Server:
lutris-wrapper: Tomb Raider II
Started initial process 6636 from mangohud /home/username/.local/share/lutris/runners/wine/lutris-6.21-6-x86_64/bin/wine /home/username/Games/Tomb Raider II/Tomb2.exe
Start monitoring process.
/home/username/.local/share/lutris/runners/wine/lutris-6.21-6-x86_64/bin/wine: symbol lookup error: /usr/lib32/mangohud/libMangoHud.so: undefined symbol: _ZN6spdlog5sinks18rotating_file_sinkISt5mutexEC1ENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEjjb
Monitored process exited.
Initial process has exited (return code: 32512)
All processes have quit
Exit with return code 32512
Although this output utilizes "Tomb2.exe", this happens with all kinds of windows applications relying upon Direct3D7-8-9-10-11, as far as I can test. Thus, all kinds of Direct3D applications seem to be affected (Don't have Direct3D12 applications to test). The "undefined symbol" seems also to vary depending on utilized .ext, but this is probably to be expected.
This output also happens both with the generic WineD3D wrapper (When compatible with the executable), and with DXVK. Thus, wrappers seem not to affect output.
Although the output mentions "lutris-6.21-6-x86_64" Wine version, I can confirm this happens also on lutris-7.2-x86_64 Wine version (Most recent Wine version on Lutris). Similarly, this also happens on older Lutris-Wine versions. Wine version thus seems not to affect output.
No CTDs happen if MangoHud is disabled through the Lutris advanced interface.
Can confirm MangoHud-0.6.5_1 (Previous package installed on my system) was working perfectly.
Although I could technically revert package version, I'll hold unto if developers need some further outputs.
Only similar issues I could find is the following:
https://github.com/flightlessmango/MangoHud/issues/772
Except, compared to the aforementioned GitHub issue, MangoHud 0.6.7.1 is non-functional ALSO in Lutris on my end, and I'm away from my Steam machine, thus I can't test MangoHud with Steam.
Kind Regards to the Void Linux Team, and Thank You for your work.
Sorry for the copy-paste, but I believe it was a good explanation.
next prev parent reply other threads:[~2022-05-31 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 13:59 [ISSUE] " TeusLollo
2022-05-31 14:06 ` TeusLollo
2022-05-31 14:07 ` TeusLollo
2022-05-31 14:27 ` TeusLollo
2022-05-31 14:51 ` TeusLollo
2022-05-31 16:59 ` Johnnynator [this message]
2023-10-12 23:02 ` TeusLollo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220531165903.I-uxCuNhd0IusZfgyeTEl8geEAl7Lsz42egf4KTydkU@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).