"vboxweb.service: Can't open PID file /run/vboxweb.pid (yet?) after start: Operation not permitted" on a clean installation of VirtualBox
Bug #1894862 reported by
AsciiWolf
This bug affects 13 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| One Hundred Papercuts |
New
|
Undecided
|
Unassigned | ||
| virtualbox (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
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.
| description: | updated |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in virtualbox (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| phirestalker (firestalker1-deactivatedaccount) wrote | #2 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in virtualbox (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.