It will spend some time in precise-proposed before it hits precise-updates. This will occur after 3.2.0-26.41, which is currently in precise-proposed, moves to precise-updates. 3.2.0-26.41 is based on the upstream 3.2.19 kernel - see bug 1008711. You can see this bug number under the precise heading at http://people.canonical.com/~ubuntu-archive/pending-sru.html and you can also monitor that page for the next kernel after 3.2.0-26.41.
See https://wiki.ubuntu.com/Testing/EnableProposed for instructions on how to enable and use -proposed. Technically, I was a little hasty in marking this bug as Fix Released. I should have waited until the fix moved into either quantal-release or precise-proposed, but I was eager to get it off my radar. I hope you don't mind too much. 3.5.0-1.1 is now in quantal-release so if my understanding is correct Fix Released is now technically correct since this bug is not targeted to a specific Ubuntu version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002562 Title: no 3D with radeon driver, AIGLX error: Calling driver entry point failed To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1002562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
