[Bug 2017846] Re: System kept waking up after pressing power button

Nick Rosbrook 2017846 at bugs.launchpad.net
Fri Jun 9 16:28:12 UTC 2023 

I do see the behavior you are describing in those logs:

Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:35:10 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:35:45 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:35:45 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:36:02 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:40:00 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:40:00 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:40:17 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:50:15 Y4M1-II systemd-logind[2855]: The system will power off now!
Apr 27 00:50:15 Y4M1-II systemd-logind[2855]: System is powering down.

Each gap is 17 seconds, which is interesting I guess.

If you are using suspend-then-hibernate (/etc/systemd/sleep.conf) and
your battery is low, the system might be waking up from suspend to then
hibernate (it does not look like you are on batter power though).
Otherwise there might be a timer unit installed with WakeSystem=true
that happens to be firing when you suspend. Besides that I don't think
systemd would do anything else to wake the system (I don't see any other
relevant uses of CLOCK_BOOTTIME_ALARM). If you want to investigate
systemd involvement further, than you can enable debug logs for systemd-
logind and attach updated logs if this issue occurs again.

$ cat > /etc/systemd/system/systemd-logind.service.d/debug-logs.conf << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF

Probably best to reboot for that to take effect.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2017846

Title:
  System kept waking up after pressing power button

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Tried it 3 times in the last 15min, each time it keeps waking back up.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  yamiyuki  42974 F.... wireplumber
   /dev/snd/controlC3:  yamiyuki  42974 F.... wireplumber
   /dev/snd/controlC0:  yamiyuki  42974 F.... wireplumber
   /dev/snd/seq:        yamiyuki  42972 F.... pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 27 00:45:37 2023
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0xffffffff quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware                            20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570S AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  Package: systemd 252.5-2ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0xffffffff quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570S AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017846/+subscriptions

More information about the foundations-bugs mailing list