If we're doing takeaway analysis here: The first problem is that about a week before release, the -18 kernel was released. Rather than being a simple ABI bump like the last few kernels were, it contained a *large* number of cherry-picked patches that contained a wide array of changes.
No kernel with that amount of code churn should ever be introduced to a distro base a week before release. And in my experience, that's a first for Ubuntu. The second problem is that THIS bug was decided as the one all of the others became duplicates of. It downplays the severity of the defect; this isn't just about losing HDMI in all relevant control panels, it's about *being completely unable to get to a working GUI* (at least for people using binary blob drivers). And while I reported the defect as being THAT severe, that severity was lost when it got linked to a lesser-severity defect. If you take a high-severity defect and make it a duplicate of a lower severity one, the "source" defect should have its severity raised. The third problem is that this was reported a week before release, but the flawed kernel line was released anyway. When hardware isn't working (at best) or the machine isn't able to boot to a GUI (at worst), a release note IMO isn't an adequate response. Rolling back to the last kernel that worked would have been simpler, and easier. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169984 Title: 3.8.0-18 HDMI/DisplayPort audio regression: Either oops or opening device fails with -ENODEV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-tests/+bug/1169984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
