Prompt the user when the power button is pressed on a VM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned | ||
gnome-settings-daemon (Ubuntu) |
Triaged
|
High
|
Unassigned |
Bug Description
Steps to reproduce:
1. Install Ubuntu 18.04 LTS as VirtualBox guest
2. Login to session
3. Press ACPI Power button/key
Expected behavior:
* Ubuntu asks user about action
Actual behavior:
* Ubuntu immediately shutdowns
Note 1: Problem exists with both VirtualBox 5.1.36 and 5.2.10 (guest additions and extpack are installed and have corresponding versions). Ubuntu 16.04.4 LTS amd64 is a host.
Note 2: Problem exists if use QEMU-KVM (sudo kvm -m 1536 -drive file=/dev/
Workaround/fix (1)
gsettings set org.gnome.
Workaround/fix (2)
Settings >
Power >
Suspend & Power Button >
When the Power Button is pressed = Power Off (actually does prompt the user)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-desktop 1.417
ProcVersionSign
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 5 18:32:06 2018
InstallationDate: Installed on 2018-04-28 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-04-28 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: gnome-settings-
PackageArchitec
ProcVersionSign
Tags: bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
no longer affects: | gnome-power-manager (Ubuntu) |
no longer affects: | gnome-session (Ubuntu) |
no longer affects: | policykit-1 (Ubuntu) |
no longer affects: | policykit-gnome (Ubuntu) |
no longer affects: | ubuntu-meta (Ubuntu) |
tags: |
added: hirsute impish removed: eoan groovy |
I posted my analysis in AskUbuntu question ( https:/ /askubuntu. com/q/1032461/ 66509 ) .
Currently I can state that in terminal session aka `multi-user.target` (`systemctl isolate multi-user.target`) all variables from */etc/systemd/ logind. conf* are sourced normally. So the problem is with GNOME session (`systemctl isolate graphical.target`) in `gnome- settings- daemon` or something other.