regression nvidia, nvidia-open between releases 42.20250602 and 42.20250603

[Vaneixus]

Describe the bug

When booting any images nvidia/nvidia-open built after image tagged 42.20250602. My second external monitor stops working.

What did you expect to happen?

three monitors working.

Output of bootc status

● Booted ostree
           Commit: 8a1231e917a703342c3e6845e07cbb1f42360264ebddc9733b8da819d489c6c1

  Rollback ostree
           Commit: c53755c4694e642a153f591f6f6d2f951692bb265b82aeb611c343a7cdd82132

 Other ostree
       Commit: 76239bf3edb18cb157fc87aad32a0b5866e83e5cf6858e5d2dd21242430cc607
       Pinned: yes

Output of groups

<username redacted> wheel uinput docker incus-admin libvirt

Extra information or context

waydroid package is layered, but I believe it is of no consequence, since even the driver included in the initram fails to initialize the third monitor.

[dosubot]

Hi @Vaneixus! I'm Dosu and I’m helping the bluefin team.

There isn't any official documentation or confirmed fix for this specific regression with nvidia/nvidia-open and external monitors between 42.20250602 and 42.20250603. However, similar NVIDIA driver issues have happened recently, sometimes due to incomplete driver upgrades or build problems, and were resolved in later releases or by rolling back to a previous working snapshot. The most reliable workaround for now is to rollback to 42.20250602 using ujust rebase-helper or bootc. Keep an eye on Bluefin release notes and the Discord for updates, as these types of regressions are often discussed and resolved there. If you want to help diagnose, collect logs like dmesg, journalctl, and xrandr after booting the problematic release and share them with the community for more targeted troubleshooting.

References:

• Recent NVIDIA build failures and resolution
• Previous NVIDIA driver regression and rollback advice

Official docs: https://docs.projectbluefin.io

Tip: You can use tldr bootc for a quick summary of bootc commands.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[Vaneixus]

@dosu I have checked today's stable release and the regression is still present. I should also mention that the FreeIPA plugin was layered at one point.

[dosubot]

No known conflicts exist between the FreeIPA plugin and NVIDIA drivers or display management on Bluefin, and there’s no documentation or community report linking layered FreeIPA to multi-monitor regressions. To help isolate the issue, try removing the FreeIPA plugin (if still layered) and see if the problem persists. Collecting logs like dmesg, journalctl, and xrandr after booting the affected release can help pinpoint the cause. Keep an eye on Bluefin release notes and community channels, as similar NVIDIA regressions have been resolved in the past. Official docs: https://docs.projectbluefin.io

Tip: Use ujust rebase-helper to quickly roll back or switch images. For a quick summary of bootc commands, try tldr bootc.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.