Daniel, fair point. I do agree the process matters here, especially because this was not just an obscure packaging edge case. The transition created an apparent upgrade path from 470 to 535 even though 535 cannot support the hardware most likely still using 470.
So yes, there are two separate issues: 1. the immediate technical regression for Kepler users; 2. the process failure that allowed an incompatible migration path to be proposed, verified, and then treated as acceptable. My main concern is still keeping the report actionable, because once the thread becomes mostly about blame, it gets easier for maintainers to ignore. But I agree the process question should not be dismissed either. At minimum, this needs a post-mortem or packaging-policy lesson: transitional packages should not point legacy hardware users toward a driver branch that the kernel/NVIDIA stack itself says will ignore their GPU. That matters not only for 470 now, but for future legacy transitions as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2155202 Title: Latest Update Breaks Systems Using Nvidia 470 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2155202/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
