There has been no activity on this bug report for over 60 days, and there was
almost a full year between the last two comments. It's probably time to close
it once and for all (status is Triaged for Linux (Ubuntu), but just in case
If anyone is experiencing this exact problem with Karmic
I'm closing this based on the latest two comments, re the bug not
appearing in Edgy or Feisty. If the problem recurs, we can reopen the
bug, and collect appropriate debugging information, e.g.,
The output from uname -a, in the body of the report;
The output of sudo lspci -vv, attached to the
Folks, is this a duplicate of 50031? That seems to be the report
receiving the most attention, and the inconsistent and mysterious
behaviours others are reporting in 50031 are consistent (:-) with the
what doesn't quite work for me.
I'll leave this on its own for now, would appreciate guidance re
FYI, when I opened this bug, I misassigned it because I didn't
understand the wheres and hows of power management: My laptop WAS NOT
and IS NOT running ACPI, it is running APM. This is most definitely not
an ACPI bug, ACPI is (most likely) a red herring, at least in my case.
As Matthew points out,
While this behavior continues, at least now there is a consistent
(99%+guaranteed) workaround (with only one caveat...).
Two cases: 1) machine asleep for a while; 2) machine asleep briefly.
A while is on the order of hours; briefly is on the order of minutes
(as much as an hour or two).
Case 1:
