Virtualbox missing vboxautostart-service.sh

Bug #1912861 reported by Cameron Tacklind
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virtualbox (Debian)
New
Unknown
virtualbox (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

After installing Virtualbox via `sudo apt install virtualbox`, I expect a service to be installed that enabled automatically starting guest VMs on system boot.

Looking at the Virtualbox sources, I see a file `vboxautostart-service.sh` that is the appropriate service configuration.

`dkpg-query -L virtualbox`, after installing, shows only 1 file in `/etc/init.d/`: `/etc/init.d/virtualbox`.

If memory serves, this init script used to be installed on my system but I believe unattended updates broke it.

Without this file, one must manually create it (or an equivalent with Systemd).

Was this removed intentionally? Or maybe I just broke something on my system? I've tried re-installing virtualbox a few times.

```
cameron@uberfall:~$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
cameron@uberfall:~$ apt-cache policy virtualbox
virtualbox:
  Installed: 6.1.16-dfsg-6~ubuntu1.20.04.1
  Candidate: 6.1.16-dfsg-6~ubuntu1.20.04.1
  Version table:
 *** 6.1.16-dfsg-6~ubuntu1.20.04.1 500
        500 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages
        100 /var/lib/dpkg/status
     6.1.6-dfsg-1 500
        500 http://us.archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages
```

Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1912861

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: xfwm4 (Ubuntu) → virtualbox (Ubuntu)
Revision history for this message
Chris Guiver (guiverc) wrote :

Was there a reason why you reported the bug as being related to `xfwm4` ?

Your description implies it's related to virtualbox, thus I've changed the package to that.

If I'm missing something, please elaborate in comment.

Revision history for this message
Cameron Tacklind (cinderblock) wrote :

I believe I typed in `virtualbox` in the package. I was confused when I saw it changed. Unclear if I messed up or if website revered it on its own.

Norbert (nrbrtx)
tags: added: bionic focal groovy hirsute xenial
Changed in virtualbox (Ubuntu):
status: New → Confirmed
Changed in virtualbox (Debian):
status: Unknown → New
Norbert (nrbrtx)
tags: added: impish
removed: groovy
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

Hello, I think that script is used to *stop* running vms, not to automatically start them.

To start them I created a gnome applet that runs vboxmanage on startup.

Changed in virtualbox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Cameron Tacklind (cinderblock) wrote :

@costamagnagianfranco I think this is incorrect. Looking at the official script, https://www.virtualbox.org/svn/vbox/trunk/src/VBox/Installer/linux/vboxautostart-service.sh, I see:
- a `start()` function that runs:
- `/usr/lib/virtualbox/VBoxAutostart` with params:
- `--start --config $VBOXAUTOSTART_CONFIG` where:
- `VBOXAUTOSTART_CONFIG=/etc/vbox/autostart.cfg`

@guiverc I am not able to run `apport-collect 1912861` successfully as I am running a headless server and `apport-collect` tries to launch a browser to auth, which fails.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.