It's possible that this could be caused by faulty hardware, but I doubt it. This seems to come up every other Ubuntu/Debian upgrade reinstall I do. I noticed this with Mint8 fresh install. After upgrade it went away. Now after trying Ubuntu 10.04 it's back. On my part it's definitely software issue and I also begin to believe like Angelo that it's intentional. Can someone please do audit on the people who are supposed to oversee this code?
-Angelo Corsaro wrote on 2009-07-03
"I'm thinking that this bug is left opened intentionally. I'm agree with Johan Christiansen, two years and a half is enough to solve this problem that is not affecting the Window$ environment.. mmmhhh strange"
It's possible that this could be caused by faulty hardware, but I doubt it. This seems to come up every other Ubuntu/Debian upgrade reinstall I do. I noticed this with Mint8 fresh install. After upgrade it went away. Now after trying Ubuntu 10.04 it's back. On my part it's definitely software issue and I also begin to believe like Angelo that it's intentional. Can someone please do audit on the people who are supposed to oversee this code?
-Angelo Corsaro wrote on 2009-07-03
"I'm thinking that this bug is left opened intentionally. I'm agree with Johan Christiansen, two years and a half is enough to solve this problem that is not affecting the Window$ environment.. mmmhhh strange"