This bug is officially also acts in the name of bug #226279. What to do
when this bug is officially fixed, but MY BUG #226279 is still a bug for
me! The kernel that's said to fix bug #226279 does NOT fix bug #221213,
which is the situation reported by me!

So: as long as bug #221213 is concerned, and for my Acer, Hardy is
broken, only Gutsy and Intrepid have working kernels.

HOW CAN THIS BUG REPORT READ "FIX RELEASED" WHEN NOT ALL OF ITS 15
"DUPLICATES" ARE CONFIRMED TO BE FIXED TOO?

(Sorry for shouting, but the policy of marking bugs as "duplicates" is
too lax.)

-- 
Kernel 2.6.24-17 - broken resume from suspend to RAM
https://bugs.launchpad.net/bugs/226279
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to