Marc, apologies for this lingering without comments for so long,
sometimes reports fall through the cracks. There are standard debugging
procedures for ACPI-related problems, hopefully we can address this
problem with those.
First, please confirm that this is still a problem with a stock Edgy
release.
Second, if you could test with Feisty and report back, that would be
great. However, Feisty is development software, so testing with it on a
production machine is not advised. If you can test with it, make sure
you first back up important data.
If the problem persists, please provide the following information:
Update the report with the output of
uname -a
Attach to the report the output of the following commands, one
attachment per command (please do not compress, please do not make one
big attachment, and please do not include the information in-line):
sudo lspci -vv
sudo lspci -vvn
sudo dmidecode
Please be sure to use sudo, root privileges are required to get the
information needed to make progress with this report.
Re which release to use when doing this: If you can test under Feisty
and the problem persists there, use Feisty. If you cannot test under
Feisty and the problem persists in Edgy, test under Edgy.
Of course, if the problem has disappeared, you can close the report or
request that it be closed! Thanks!
** Changed in: acpi-support (Ubuntu)
Status: Unconfirmed => Needs Info
--
Fujitsu Siemens Lifebook E4010
https://launchpad.net/bugs/46225
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
