I have lots of different virtual machines running under VirtualBox on a Win10 host. All the various machines can be shutdown by sending a shutdown signal from the machine menu (emulating ACPI button press I believe). This includes all my Leap machines which immediately show the shutdown menu in LXDE environment. However my Tumbleweed machine does not respond at all.
I am sure it’s just something missing but am keen to understand why it’s broken. Any ideas on the needed packages or services required to respond to an ACPI shutdown signal?
Thanks.
PS The machine is up to date and been ‘broken’ for months, so it’s unlikely to be a transient update issue.
Explain what exact menu you are invoking. Do not assume everyone immediately understands what “machine menu” is. I just tested sending “ACPI shutdown” to Tumbleweed guest - and it shut down. I do not see “shutdown signal”.
Apologies, yes it is labeled as “ACPI Shutdown” which is under the “Machine” menu. It can also be activated via the close window X at the top right of the running VM, which also fails to do anything in my case.
When I try to close running VM console window, VB crashes after dialog is closed Even if I just do “Cancel”. It does send (ACPI) shutdown signal if I chose it.
ACPI shutdown should be handled by systemd-logind via power button. Show output of
I open the Power Manager configuration applet (System -> Preferences -> Power Manger)
If I set the “When power button is pressed” option to “Shutdown” an ACPI shutdown signal does indeed shut it down. If I set it to “Ask” then nothing happens when I send an ACPI shutdown signal. I was expecting to see the same dialogue that I get when I go to “Logout” from the start menu but sadly not.
Anyway, it’s set to “Shutdown” now and all is well.