reboot command is SysV-init compatibility command and is specified as non-interactive.
Why are you typing reboot? seriously this is not something desktop users typically do, at all =) -- 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/1748095 Title: Non-root user can reboot machine from the command line Status in systemd package in Ubuntu: Opinion Bug description: Open a gnome-terminal as your normal user and type 'reboot' and ENTER. The PC reboots immediately, losing all unsaved work for all users (this is the case on both my VM and laptop running Ubuntu 18.04, so I don't think it's a weird configuration issue). In the old days, didn't you have to be root (or sudoed) for this command to work? While we're on the subject, wouldn't it be nicer if the reboot command (ie when run as root) asked you to confirm before executing, pointing out that all unsaved work for all users will be lost? Note that you can't reboot a server if you are logged in via ssh as a non-root user: Failed to set wall message, ignoring: Interactive authentication required. Failed to reboot system via logind: Interactive authentication required. Failed to open /dev/initctl: Permission denied Failed to talk to init daemon. I am assuming this is a systemd issue, because reboot just links to systemctl, and systemctl can be executed by non-root users: $ ll /sbin/reboot /bin/systemctl -rwxr-xr-x 1 root root 182352 Dec 12 21:25 /bin/systemctl* lrwxrwxrwx 1 root root 14 Dec 12 21:25 /sbin/reboot -> /bin/systemctl* ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 8 12:49:33 2018 InstallationDate: Installed on 2017-12-18 (51 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171212) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=dd72d916-58fc-49a1-9798-feded5ce6eff ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : email@example.com Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp