Comment 70 for bug 629258

I have the same issue in Meerkat (2.6.35-22-server, x86_64).

Confirming that it worked (i.e. did not have the issue) in Lucid. Same computer. Same hardware. Same architecture (x86_64). Only change done was a 'clean install' from Lucid to Meerkat with all updates and upgrades that it asked for.

Also confirming that this bug remains no matter how long the laptop is ON. 4 hrs - 6 hours, may be more (i.e. it does not go away in 10 min as some threads suggest). Also this remains the same whether it is a clean startup (from power-down) or a wakeup from a suspended state.

Guys, pls. don't mark this (or similar bugs) as invalid. That will be the biggest disservice to the loyal users of Ubuntu Linux. I understand and respect that some of you guys (developers & testers) might not be able to see/reproduce the problem. That's OK. But pls. don't disrespect fellow users and community members by saying/marking them as invalid. (I saw in some threads, that's why I persistently request).

Snapshot attached. Tell me anything more you need. I will provide to the best I can.
#uname -a -> Linux 2.6.35-22-server #35-Ubuntu SMP Sat Oct 16 22:02:33 UTC 2010 x86_64 GNU/Linux
gnome-power-manager version -> Version: 2.32.0-0ubuntu1