Performance overlay: please update mangohud — mangoapp ignores overlay-level changes for NVIDIA metrics, aborts on startup X error

Aperta
  • Qualcosa non va?
#3,009 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp, linux
Ambito
performance

Direzione di ricerca

Start by reviewing the SteamOS package recipe and the upstream MangoHud change 4e69793b referenced in the issue. The report says updating to MangoHud 0.8.3 or later fixes NVIDIA metrics that stop updating when the overlay level changes; the second startup abort has no identified cause. Done means the packaged version keeps those metrics live across level changes and the startup abort is investigated.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Your system information

  • SteamOS 3.9.5 (BUILD_ID 20261023.100), mangohud 0.8.3.rc1.r24.g33c2c7dd-4
  • ASUS ROG NUC 15: Core Ultra 9 275HX + RTX 5080 Laptop GPU
  • I'm aware NVIDIA isn't a supported SteamOS configuration (nvidia-open 615.71.09 added on top); reporting because the main fix already exists upstream and the packaged mangohud predates it.

Please describe your issue in as much detail as possible:

  1. GPU stats stay at 0 after changing the overlay level. In the packaged version, NVIDIA::get_samples_and_copy() reads get_params() once when the sampling thread starts, so only the metrics enabled at mangoapp's startup level are ever queried. Raising the Performance Overlay to level 4 shows GPU temperature and clock as 0 °C / 0 MHz; systemctl --user restart gamescope-mangoapp at level 4 makes them appear (61 °C / 2040 MHz). Fixed upstream in flightlessmango/MangoHud@4e69793b ("nvidia: Update params in the infinite loop", in v0.8.3). The AMD path re-reads params every sample, which is why Deck hardware isn't affected.

  2. mangoapp aborts at session start. Backtrace: main → XSync → _XReply → _XError → _XDefaultError → exit() → (mangoapp exit handlers) → abort. An X error during startup makes Xlib call exit(), and something in mangoapp's teardown then aborts (systemd restarts it, so the overlay recovers). The packaged build is stripped, so I can't say which destructor aborts yet; reporting it for completeness.

Steps for reproducing this issue:

  1. Boot into Gaming Mode with the Performance Overlay at level 1 or 2.
  2. Start a game, raise the overlay to level 4.
  3. GPU temperature/clock read 0; restarting gamescope-mangoapp fixes it until the level changes again.

Updating the package to mangohud ≥ 0.8.3 would pick up the fix for (1). Verified: Valve's 0.8.3.rc1.r24.g33c2c7dd-4 source package with 4e69793b cherry-picked on top (built against the SteamOS image's own libraries) keeps NVIDIA stats live across overlay-level changes.

Related, not yet upstream: on laptop NVIDIA GPUs the overlay also shows garbage for the power limit and fan (unchecked NVML queries), proposed in flightlessmango/MangoHud#2192.

Lingua principale
Nessun dato sulla lingua
Stelle
2.7k
Fork
89
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ValveSoftware/SteamOS

Tutte le issue di ValveSoftware/SteamOS

Issue simili

Altre issue su Performance

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.