Hi. I went to raring about three weeks before release trying to help debug. So I ran into the HDMI problem pretty much right away, and I reported the bug ... so far so good, this is why I tried a prelease. But the point of that is to help make the release better, and that didn't work out, except for a line in the release note. This was a bad bug because it affected just about everyone using Ubuntu as a media PC (where you will find HDMI displays). How did the kernel team not realise the severity? I guess one problem was the report was spread over countless bugs; the duplicate detection in bug reporting didn't work, and therefore perhaps it wasn't obvious how many people were affected.
My USB DAC is still broken with all Raring kernels so far. This was also a bug introduced during development, I think from selective patch applications. That's another bug report we are still working on... but by and large, Raring was not a great release for me. I think the Ubuntu kernel approach is fragile ... regressions and breaks get introduced faster than they can be triaged and fixed. Raring's kernel was not release quality in my opinion ... the release note line about broken HDMI audio basically proves it: Ubuntu released a kernel with a known bug, the severity of which was either not well understood, or the affected users were considered outside the target user-base (which I can't believe). Either way, not very impressive. Luckily we can use generic kernels. -- 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 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
