lid closure behavior unpredictable

Bug #1896395 reported by Gerald Gilbert-Thorple
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

in 20.04.01 LTS (release 20.04), suspend on lid closure works for a while, then one day stops working, with no error message in syslog. The event is not even registered. The problem seems to start when the system has been inactive for long enough so that the screen is blanked.

 systemd:
  Installed: 245.4-4ubuntu3.2
  Candidate: 245.4-4ubuntu3.2
  Version table:
 *** 245.4-4ubuntu3.2 500
        500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     245.4-4ubuntu3 500
        500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages

seems similar to bug #1840784, even though no error message is generated.

Revision history for this message
Gerald Gilbert-Thorple (gxgilthor) wrote :

Using systemctl status systemd-logind, I see that lid events are no longer being detected.
This behavior persists even after restarting the service. This is *not* what is requested in logind.conf, where HandleLidSwitch=suspend and HandleLidSwitchDocked=suspend.

Revision history for this message
Dan Streetman (ddstreet) wrote :

You need to provide some kind of logs to review.

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Gerald Gilbert-Thorple (gxgilthor) wrote :

sorry, you can withdraw this bug as I discovered it is a kernel bug, not systemd.
(I wanted to withdraw it earlier but did not know how to get back to this report.)
thanks

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

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

Changed in systemd (Ubuntu):
status: Incomplete → Expired
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.