Public bug reported:
VirtualBox on Ubuntu 20.04 seems to have the vboxweb.service
automatically enabled after installation even though it is not
configured and working properly. This leads to a systemd being in
"degraded" state with "vboxweb.service: Can't open PID file
/run/vboxweb.pid (yet?) after start: Operation not permitted" error
being printed in system journal every time the computer boots. Please,
consider disabling the vboxweb.service by default, it is usually used by
headless VirtualBox setups and should not be enabled on a regular
desktop setup anyway.
** Affects: hundredpapercuts
Importance: Undecided
Status: New
** Affects: virtualbox (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal
** Description changed:
- Virtualbox on Ubuntu 20.04 seems to have the vboxweb.service
+ VirtualBox on Ubuntu 20.04 seems to have the vboxweb.service
automatically enabled after installation even though it is not
configured and working properly. This leads to a systemd being in
"degraded" state with "vboxweb.service: Can't open PID file
/run/vboxweb.pid (yet?) after start: Operation not permitted" error
being printed in system journal every time the computer boots. Please,
consider disabling the vboxweb.service by default, it is usually used by
headless VirtualBox setups and should not be enabled on a regular
desktop setup anyway.
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894862
Title:
"vboxweb.service: Can't open PID file /run/vboxweb.pid (yet?) after
start: Operation not permitted" on a clean installation of VirtualBox
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1894862/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
