With the bug re-appearing in Maverick final, and persisting, shouldn't this bug be re-opened for Maverick current? The problem remains up to, and including the latest 2.6.35-24-virtual kernel.
With the bug re-appearing in Maverick final, and persisting, shouldn't this bug be re-opened for Maverick current? The problem remains up to, and including the latest 2.6.35-24-virtual kernel.