Recent NVIDIA driver update broke GPU reporting

[chris-gputrader]

Is there an existing issue for this?

• [X] I searched the existing issues and did not find anything similar.

Current Behavior

GPU reporting was working fine but with the latest NVIDIA driver update 565.77 everything in GPU resources is showing N/A. nvtop and vitals seem to still report correctly.

Expected Behavior

No response

Steps to Reproduce

No response

Debug Logs

Expand logs

flatpak run --env=RUST_LOG=resources=debug net.nokyan.Resources
DEBUG resources::utils > Running as Flatpak
INFO  resources::application > Resources (net.nokyan.Resources)
INFO  resources::application > Version: 1.7.1
INFO  resources::application > Datadir: /app/share/resources
DEBUG resources::application > Operating system: Fedora Linux 41 (Workstation Edition)
DEBUG resources::application > Kernel version: 6.11.10-300.fc41.x86_64  ```
</details>


### Environment

_No response_

### Anything Else?

_No response_

[nokyan]

Are your host NVIDIA driver version and the Flatpak driver version equal? You can check with the following commands:

cat /sys/module/nvidia/version
flatpak info "org.freedesktop.Platform.GL.nvidia-$(cat /sys/module/nvidia/version | tr '.' '-')"

[chris-gputrader]

`❯ cat /sys/module/nvidia/version flatpak info "org.freedesktop.Platform.GL.nvidia-$(cat /sys/module/nvidia/version | tr '.' '-')" 565.77 ID: org.freedesktop.Platform.GL.nvidia-565-77 Ref: runtime/org.freedesktop.Platform.GL.nvidia-565-77/x86_64/1.4 Arch: x86_64 Branch: 1.4 Origin: flathub Collection: org.flathub.Stable Installation: system Installed: 2.1 MB

  Commit: 6d0443571bd02e073f4c7d276e5e5785f229640eac6fe9a6631d38206c46d3b3
  Parent: 292864500332d845090a83aab90fc0075449d25515395244fb1f9ef040450d50
 Subject: Add Vulkan 550.40.82 (6da56b62)
    Date: 2024-12-12 23:50:42 +0000`

[nokyan]

Does GPU usage display work in the GPU column of the Processes/Apps views?

[Norbiros]

I encountered the same issue after updating to new drivers. Running flatpak update resolved it for me by downloading the correct drivers

[feer9]

I encountered the same issue after updating to new drivers. Running flatpak update resolved it for me by downloading the correct drivers

I can confirm running flatpak update solves this issue.