Public bug reported:
By default, /etc/systemd/logind.conf sets HandlePowerKey to poweroff. This is
a terrible default, because this poweroff action does not ask for any
confirmation whatsoever, encouraging data loss. The power key does get pressed
inadvertently from time to time:
- It's usually also the resume-from-suspend key, so if you thought you had
suspended the computer but in fact it only locked after inactivity, you could
press the power key to resume, only to find that you just nuked your session.
- On many laptops, the power button is close to backspace. A single slip of
your pinky nukes your session.
Each of these mishaps can result in loss of unsaved data, and/or data
corruption if some background task is running that doesn't expect to get killed
in the middle. This is an especially terrible user experience for novices who
have little prior exposure to system setting files, who will likely have a hard
time fixing it. This is not a sensible default.
Please at least show confirmation for this poweroff action by default,
or if that's difficult to do, make the default more benign, like ignore
or lock.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd 249.11-0ubuntu3.7
ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Flashback:GNOME
Date: Fri Apr 21 10:01:27 2023
InstallationDate: Installed on 2023-02-02 (77 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Supermicro Super Server
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic
root=UUID=7851a3b8-a4dc-460a-abb0-6f754ae2d343 ro quiet splash vt.handoff=7
SourcePackage: systemd
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.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2022
dmi.bios.release: 5.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.5
dmi.board.asset.tag: Default string
dmi.board.name: X11SRA
dmi.board.vendor: Supermicro
dmi.board.version: 1.02
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd01/27/2022:br5.15:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SRA:rvr1.02:cvnSupermicro:ct17:cvr0123456789:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Super Server
dmi.product.sku: Default string
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
modified.conffile..etc.systemd.logind.conf: [modified]
mtime.conffile..etc.systemd.logind.conf: 2023-04-21T09:55:04.295695
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
** Description changed:
By default, /etc/systemd/logind.conf sets HandlePowerKey to poweroff. This
is a terrible default, because this poweroff action does not ask for any
confirmation whatsoever, encouraging data loss. The power key does get pressed
inadvertently from time to time:
- It's usually also the resume-from-suspend key, so if you thought you had
suspended the computer but in fact it only locked after inactivity, you could
press the power key to resume, only to find that you just nuked your session.
- On many laptops, the power button is close to backspace. A single slip of
your pinky nukes your session.
- Each of these mishaps can result in loss of unsaved data, and/or data
corruption if some background task is running that doesn't expect to get killed
in the middle. This is an especially terrible user experience for novices who
have little prior exposure to system setting files. This is not a sensible
default.
+ Each of these mishaps can result in loss of unsaved data, and/or data
corruption if some background task is running that doesn't expect to get killed
in the middle. This is an especially terrible user experience for novices who
have little prior exposure to system setting files, who will likely have a hard
time fixing it. This is not a sensible default.
Please at least show confirmation for this poweroff action by default,
or if that's difficult to do, make the default more benign, like ignore
or lock.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd 249.11-0ubuntu3.7
ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Flashback:GNOME
Date: Fri Apr 21 10:01:27 2023
InstallationDate: Installed on 2023-02-02 (77 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Supermicro Super Server
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic
root=UUID=7851a3b8-a4dc-460a-abb0-6f754ae2d343 ro quiet splash vt.handoff=7
SourcePackage: systemd
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.
+ 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.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2022
dmi.bios.release: 5.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.5
dmi.board.asset.tag: Default string
dmi.board.name: X11SRA
dmi.board.vendor: Supermicro
dmi.board.version: 1.02
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd01/27/2022:br5.15:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SRA:rvr1.02:cvnSupermicro:ct17:cvr0123456789:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Super Server
dmi.product.sku: Default string
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
modified.conffile..etc.systemd.logind.conf: [modified]
mtime.conffile..etc.systemd.logind.conf: 2023-04-21T09:55:04.295695
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2017184
Title:
Terrible Default for HandlePowerKey
Status in systemd package in Ubuntu:
New
Bug description:
By default, /etc/systemd/logind.conf sets HandlePowerKey to poweroff. This
is a terrible default, because this poweroff action does not ask for any
confirmation whatsoever, encouraging data loss. The power key does get pressed
inadvertently from time to time:
- It's usually also the resume-from-suspend key, so if you thought you had
suspended the computer but in fact it only locked after inactivity, you could
press the power key to resume, only to find that you just nuked your session.
- On many laptops, the power button is close to backspace. A single slip of
your pinky nukes your session.
Each of these mishaps can result in loss of unsaved data, and/or data
corruption if some background task is running that doesn't expect to get killed
in the middle. This is an especially terrible user experience for novices who
have little prior exposure to system setting files, who will likely have a hard
time fixing it. This is not a sensible default.
Please at least show confirmation for this poweroff action by default,
or if that's difficult to do, make the default more benign, like
ignore or lock.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd 249.11-0ubuntu3.7
ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Flashback:GNOME
Date: Fri Apr 21 10:01:27 2023
InstallationDate: Installed on 2023-02-02 (77 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Supermicro Super Server
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic
root=UUID=7851a3b8-a4dc-460a-abb0-6f754ae2d343 ro quiet splash vt.handoff=7
SourcePackage: systemd
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.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2022
dmi.bios.release: 5.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.5
dmi.board.asset.tag: Default string
dmi.board.name: X11SRA
dmi.board.vendor: Supermicro
dmi.board.version: 1.02
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd01/27/2022:br5.15:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SRA:rvr1.02:cvnSupermicro:ct17:cvr0123456789:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Super Server
dmi.product.sku: Default string
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
modified.conffile..etc.systemd.logind.conf: [modified]
mtime.conffile..etc.systemd.logind.conf: 2023-04-21T09:55:04.295695
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017184/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
