Laptop lid is always reported as closed

[Alex]

On Livefan S1 laptop lid is _always_ reported as closed.

#cat /proc/acpi/button/lid/LID0/state
state: closed

#lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04

`acpi_listen` doesn't detect any events
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: av 2654 F.... pulseaudio
 /dev/snd/controlC1: av 2654 F.... pulseaudio
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
HibernationDevice: RESUME=UUID=32f21a3f-3826-4c6f-87f3-003691b95fd1
InstallationDate: Installed on 2016-07-25 (262 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=d7a13f95-ab6e-4c80-947d-4c9dfd7855bb ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic N/A
 linux-firmware 1.164
Tags: zesty
Uname: Linux 4.10.0-19-generic x86_64
UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/14/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.011
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: HN01
dmi.board.vendor: Hylink
dmi.board.version: 1.2
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd04/14/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnHylink:rnHN01:rvr1.2:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: av 2654 F.... pulseaudio
 /dev/snd/controlC1: av 2654 F.... pulseaudio
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
HibernationDevice: RESUME=UUID=32f21a3f-3826-4c6f-87f3-003691b95fd1
InstallationDate: Installed on 2016-07-25 (262 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=d7a13f95-ab6e-4c80-947d-4c9dfd7855bb ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic N/A
 linux-firmware 1.164
Tags: zesty
Uname: Linux 4.10.0-19-generic x86_64
UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/14/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.011
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: HN01
dmi.board.vendor: Hylink
dmi.board.version: 1.2
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd04/14/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnHylink:rnHN01:rvr1.2:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1682712

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Alex (ex-lxndr)]

apport information

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7

[Alex (ex-lxndr)]

# uname -r
4.11.0-041100rc7-generic

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel