flightlessmango
Mangohud 0.8.2-1.1 - Overwatch doesn't start
Do not report issue for old MangoHud versions
Describe the bug Hi everyone, after update, Overwatch 2 cannot be started anymore via Lutris. Downgrading to 0.8.1 works fine. Another discord user reported they have the same issue after they have updated their Nobara instance 2 days ago. Other games are running fine. Thanks to CachyOS dev the issue was narrowed down to Mangohud, hence opening this bug report.
If you need any additional info, please do not hesitate to ask me and I will provide it.
List relevant hardware/software information
- Linux Distribution: Linux 6.17.9-2-cachyos
- MangoHud version: 0.8.2-1.1
- GPU: Nvidia RTX 4090
To Reproduce Steps to reproduce the behavior: Install v.0.8.2 - The game doesn't start Downgrade to v.0.8.1 or disable mangohud - The game starts
Expected behavior The game should start with v.0.8.2
Screenshots N/A
Additional context cachyOSupdatePackages -https://pastebin.com/tkyxQYPE Lutris -d before Update - https://pastebin.com/LZE8WCua Lutris -d after update - https://pastebin.com/r9KDsz32 pacman.log after the update - https://pastebin.com/Nf5rkX5M cachyos-bugreport - https://paste.cachyos.org/p/c67bc9d.log
Additional stuff asked by a discord member: [xektop@xektopBG ~]$ pacman -Qs nvidia local/cuda 13.0.2-1 NVIDIA's GPU programming toolkit local/egl-gbm 1.1.2.1-1.1 The GBM EGL external platform library local/egl-wayland 4:1.1.20-1.1 EGLStream-based Wayland external platform local/egl-x11 1.0.3-1.1 NVIDIA XLib and XCB EGL Platform Library local/lib32-libvdpau 1.5-3 Nvidia VDPAU library local/lib32-nvidia-utils 580.105.08-1.1 NVIDIA drivers utilities (32-bit) local/lib32-opencl-nvidia 580.105.08-1.1 OpenCL implemention for NVIDIA (32-bit) local/libva-nvidia-driver 0.0.14-1.1 VA-API implementation that uses NVDEC as a backend local/libvdpau 1.5-3.1 Nvidia VDPAU library local/libxnvctrl 580.105.08-2 NVIDIA NV-CONTROL X extension local/linux-cachyos-nvidia-open 6.17.9-2 nvidia open modules of 580.105.08 driver for the linux-cachyos kernel local/linux-firmware-nvidia 1:20251125-2 Firmware files for Linux - Firmware for NVIDIA GPUs and SoCs local/nvidia-settings 580.105.08-2 Tool for configuring the NVIDIA graphics driver local/nvidia-utils 580.105.08-4 NVIDIA drivers utilities local/opencl-nvidia 580.105.08-4 OpenCL implemention for NVIDIA [xektop@xektopBG ~]$ pacman -Qs mesa local/glu 9.0.3-2.1 Mesa OpenGL utility library local/lib32-glu 9.0.3-2 Mesa OpenGL utility library (32 bits) local/lib32-mesa 1:25.3.1-2 Open-source OpenGL drivers - 32-bit local/mesa 1:25.3.1-2 Open-source OpenGL drivers local/mesa-utils 9.0.0-7.1 Essential Mesa utilities local/vulkan-mesa-implicit-layers 1:25.3.1-2 Mesa's implicit Vulkan layers [xektop@xektopBG ~]$ lspci -k -d ::03xx 00:02.0 Display controller: Intel Corporation RocketLake-S GT1 [UHD Graphics 750] (rev 04) DeviceName: Onboard - Video Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d06 Kernel driver in use: i915 Kernel modules: i915, xe 01:00.0 VGA compatible controller: NVIDIA Corporation AD102 [GeForce RTX 4090] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 5102 Kernel driver in use: nvidia Kernel modules: nouveau, nvidia_drm, nvidia
Thanks for looking into it!
I have this same issue with a Windows Steam install in a Wine prefix. Every time I start the Windows Steam, it won't launch but taking mangohud out of the launch parameters, Steam launches with no problems. The only error in the logs I see is
[MANGOHUD] [error] [cpu.cpp:784] Failed to initialize CPU power data
Like the OP, the previous version of mangohud worked.
Stumbled across a post just now and someone suggested using the environment variable MANGOHUD=1 instead of mangohud and now it works. Was there a fundamental change? Launching mangohud as a wrapper worked in the previous version.
I just bumped on this very issue when trying to run Journey and Fields of Mistria from Lutris after updating MangoHud. Both come from Steam, and I only noticed MangoHud was the likely culprit when manually running the game .exe within the prefix, which bypasses MH entirely.
My GPU is an ancient NVIDIA one, which forces me to use Proton-Sarek as upstream Proton and DXVK no longer support it because of outdated Vulkan support.
@Nemris @xektop @tda0626 what launch options are you using, what distro are you on and can you try the pre compiled released package of mangohud?
Hi @flightlessmango Those are my setting in Lutris:
I will be able to check next week if the precompiled release of 0.8.2 is working. Currently I am using the version that is in the AUR. The rest of the required info is in the initial post. Let me know if something is missing.
I have decided to update it again now and it is working this time around. I see that there is a new release v0.8.2-2.1 updated after I was trying to figure out on the 05.12.2025. Here is the pacman.log - https://pastebin.com/HkXCgTDF Here is the repo - https://packages.cachyos.org/package/cachyos-extra-v4/x86_64_v4/mangohud
[xektop@xektopBG ~]$ pacman -Qs mangohud local/lib32-mangohud 0.8.2-1 32-bit libraries for MangoHud and MangoApp local/mangohud 0.8.2-2.1 A Vulkan overlay layer for monitoring FPS, temperatures, CPU/GPU load and more.
I can't confirm this is the case for the other people though. Some people are even on different linux distribution (one person on Nobara) and are not using the cachyos repository.
If you think this could be a general bug I can check other stuff and report back. Otherwise this looks like its solved for me with v0.8.2-2.1, but I am not sure what has changed.
@flightlessmango I run Arch Linux and this is my configuration for Fields of Mistria.
Edit: disabling MangoHud from the Lutris settings and using the env variable as suggested by @tda0626 seems to work fine over here as well. The latest version of MH available in the Arch repo is 0.8.2-2, for reference.
@Nemris @xektop @tda0626 what launch options are you using, what distro are you on and can you try the pre compiled released package of mangohud?
I am using Wine-CachyOS and also on the CachyOS distro. I do not have any extra launch options being passed other than mangohud. The package I am using is from the CachyOS repo and is the same version as the OP.
Stumbled across a post just now and someone suggested using the environment variable MANGOHUD=1 instead of mangohud and now it works. Was there a fundamental change? Launching mangohud as a wrapper worked in the previous version.
I am experiencing the same issue. Using the environment variable MANGOHUD=1 does indeed work correctly.
For reference, I am using AMD. MangoHud version: 0.8.2-2 from the official Arch repository.
We did modify the dlsym behavior in the shim right before release which is completely bypassed if you use MANGOHUD=1. It would be very helpful if someone can try building 0.8.2 or latest but with 160b9f75d766c2be7767d3bdfe6e131e285c25a1 reverted
We did modify the dlsym behavior in the shim right before release which is completely bypassed if you use
MANGOHUD=1. It would be very helpful if someone can try building 0.8.2 or latest but with 160b9f7 reverted
I tried reverting that commit and can confirm that Fields of Mistria launches fine over here when the System options -> Command prefix Lutris setting is set to the custom MangoHud binary.
@Nemris I am trying to reproduce the issue on my end, but I am unable to, can you add the following environment variables and send the output logs?
LD_DEBUG=symbols
LD_DEBUG_OUTPUT=~/ld_debug_symbols
this will result into creating multiple files at your home directory called ~/ld_debug_symbols.<pid>, compress them and upload them (as they will be quite big), ideally one run with broken mangohud and one run with working mangohud
@andrew-2e128 Here are the files, obtained from launching Journey with the stock MH and with the one with that commit reverted. Remember to remove the faux .zip extension which I had to append cause GitHub.
By the way, trying to run Journey with stock MH results in an assertion error that I'm not seeing with Fields of Mistria. I attached it here for good measure.
mangohud-0.8.2-2-ld_debug.tar.xz.zip mangohud_custom-0.8.2-ld_debug.tar.xz.zip
I have the same issues, even goverley didn't start in many apps but after downgrading to 0.8.1 it's working more reliably, actually it works too reliably, it gives me a graph even on my settings app even though I don't need it.
I am a newbie so I don't know how I can help with additional data, but ask me if you need anything.
I'm on EndeavourOS, Gnome v49 wayland.
@Nemris @PNDTG can you try running the games with MANGOHUD_DLSYM_RTLD_NEXT=0?
Also regarding the the wine vulkan loader "!status" I managed to reproduce it when I had DXVK_NVAPI_VKREFLEX=1 (Nvidia Reflex enabled)