-
-
Notifications
You must be signed in to change notification settings - Fork 441
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
Mangohud no longer appears #3736
Comments
#2841 has been reverted in 2.10. In fact, I just tested the app image and it works |
I went back and did regression testing between Heroic 2.8.0 and 2.9.0. Commit 53b5bcb is what breaks mangohud on my end. |
ah I see it's broken only on native apps that are sideloaded |
I built #3767. Enabling mangohud causes any application to fail starting. Disabling mangohud in heroic allows applications to run again. Maybe it has something to do with the application path not being called correctly? Looking at the logs for Heroic 2.8.0, I see at launch: Looking at the logs for the heroic with #3767, I see the LD_PRELOAD path looks different: |
i see the issue, thanks for making it clear :) |
it has been fixed now, try again |
Works on my end. Thank you for taking a look at this. |
Describe the bug
Post AppImage version 2.8.0, mangohud no longer appears for applications. Within the logs for 2.8.0, I can see mangohud being called in an info backend message when an application launches, I do not see the same in the logs for 2.14.1. Launching heroic through the shell with mangohud,
mangohud Heroic.Appimage
, works fine and loads the config stored in~/.config/MangoHud/MangoHud.conf
. Perhaps pr#2841 may be why?Add logs
Steps to reproduce
AppImage 2.8.0
AppImage 2.14.1
Expected behavior
Mangohud appears if setting is enabled for application.
Screenshots
No response
Heroic Version
Latest Stable
System Information
openSUSE Tumbleweed
AppImage 2.8.0 & 2.14.1 (Not using flatpak)
32bit and 64bit mangohud packages installed
Additional information
Post 2.8.0, this issue occurs if the AppImage is not portable and a mangohud config file is placed in
~/.config/MangoHud/MangoHud.conf
.Post 2.8.0, this issue occurs if the AppImage is made portable by creating a directory with the same name as the AppImage plus .home and placing a mangohud config file in in
~/Heroic.AppImage.home/.config/MangoHud/MangoHud.conf
.The text was updated successfully, but these errors were encountered: