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

Abierto
  • ¿Algo no está bien?
#3,009 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, linux
Área
performance

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
2.7k
Forks
89
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ValveSoftware/SteamOS

Todos los issues de ValveSoftware/SteamOS

Issues similares

Más issues de Performance

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.