Lid Switch always reports closed on Gigabyte T1005 Netbook

Bug #874483 reported by xrayA4T
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Description: Ubuntu 11.10
Release: 11.10

Whether the lid is open or closed /proc/acpi/button/lid/LID0/state reports:
state: closed

If I close the lid the screen blanks and does not unblank until I interact with the laptop
---
ApportVersion: 1.23-0ubuntu3
Architecture: i386
DistroRelease: Ubuntu 11.10
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
Package: linux (not installed)
Tags: oneiric
Uname: Linux 3.1.0-999-generic i686
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: needs-upstream-testing oneiric
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.20)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Revision history for this message
xrayA4T (xraya4t) wrote : Re: Lip Switch always reports closed on Gigabyte T1005 Netbook

Tested with :
Linux laptop 3.1.0-999-generic #201110171146 SMP Mon Oct 17 12:45:36 UTC 2011 i686 i686 i386 GNU/Linux

and the bug persists. As I mentioned in the report the screen remains blank after closing the lid for 10 seconds or so. Is there anything I could test to see if something else is detecting the lid event other than the /proc/acpi/button/lid/LID0/state ?

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
xrayA4T (xraya4t)
summary: - Lip Switch always reports closed on Gigabyte T1005 Netbook
+ Lid Switch always reports closed on Gigabyte T1005 Netbook
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

We would like to gather additional information about your system. From a terminal, can you run the following:

sudo apport-collect 874483

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
xrayA4T (xraya4t) wrote : ProcEnviron.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Igor Zavorotkin (ivzave) wrote :

This bug does affect me too. I've noticed the lid reports ACPI event when closing like this (as per acpi_listen):

button/lid LID0 00000080 0000000a

where the last number is being incremented each time I close the lead (e.g. next time it will be 0000000b etc).
However there're no such event when I open the lid. Hope it helps.

Revision history for this message
penalvch (penalvch) wrote :

xrayA4T, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12.1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: bot-stop-nagging needs-kernel-logs regression-potential
removed: kernel-request-3.0.0-12.20
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Triaged → Incomplete
Revision history for this message
xrayA4T (xraya4t) wrote :

I no longer have the machine that was affected. If no one else if affected then I'm happy that the bug is closed.

Revision history for this message
penalvch (penalvch) wrote :

xrayA4T, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/874483/comments/9 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.