Comment 26 for bug 598242

lucid-updates appears to be official updates, so with 2.6.32-23-generic fixing the problem and being in lucid-updates it seems to be fixed in an official update. So yes, I think closing the bug with "fixed in linux-image 2.6.32-23-generic" is appropriate. (It'd be nice to know precisely which change fixed it, in case it gets reverted again, but it's probably not worth the effort of digging through everything that changed between 2.6.32-22-generic and 2.6.32-23-generic, since there's a long list of changes.)

Ewen