Regression in Bazzite 44: Triple Monitor failure on GTX 1060 & Missing fix-nvidia recipe

System Specs:

  • GPU: NVIDIA GeForce GTX 1060 6GB (Driver 580.142)

  • OS: Bazzite 44 (Fedora 44 / GNOME 50 base)

  • Environment: Wayland

Description of the Issue: Upon upgrading from Bazzite 43 to 44, the system failed to detect a triple monitor setup. Only the primary monitor remained active, locked at a fallback resolution of 1024x768.

Technical Details:

  1. Driver Status: nvidia-smi reported that the driver was loaded (v580.142), but Disp.A was marked as Off and memory usage was minimal (~22MiB), suggesting GNOME 50 failed to utilize the NVIDIA driver for display composition.

  2. Missing Tools: Attempting to fix the issue via ujust fix-nvidia failed with an error stating the recipe does not exist in the current justfile, leaving no immediate recovery path within the new image.

  3. Attempted Fixes: - Deleting monitors.xml did not resolve the resolution lock or the missing displays.

    • Forcing a refresh of the desktop database had no effect.

Resolution: A manual rpm-ostree rollback to Version 43.20260420 restored full functionality, including the triple monitor detection and correct resolutions.

Request: Please investigate if there is a known issue with the GNOME 50 transition for Pascal-based GPUs (GTX 10 series) and why the fix-nvidia utility was removed/omitted in this build.

That’s odd… Negativo17 nvidia repo is generally very reliable. I use it also on my fedora workstation

Following this thread as i have also encountered this same issue with the same gpu when upgrading to F44. I am on KDE version by the way.

I checked rpm-ostree status and saw that the state was: busy- The core of the problem i believe is that the system is stuck in a partial, unfinished upgrade as it failed to push the new image. That ‘‘busy’’ state is perhaps why the NVIDIA driver isn’t fully initialising, leading to the wrong resolution and stuttering issues.

For now, i rolled back to F43 and disabled automatic updates: sudo systemctl disable --now uupd.timer so i won’t have to deal with this again.

I will wait it out for a week or two before i attempt rebuilding again and resume the auto update.Hopefully many of the issues will be resolved by then.

If it does not resolve itself, i will dig further.

Yeap, I did a rollback, but yesterday the Bazzite team solved it and now it works perfectly :smiley: so, thanks to the Bazzite team for reacting so fast :smiley: