[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

Gianfranco, Sorry for the late response. This seems to be fixed now. I haven't had this problem for a good couple of months :). ** Changed in: plymouth (Ubuntu) Status: Incomplete => Fix Released ** No longer affects: plymouth (Ubuntu) -- You received this bug notification because you

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

This bug was fixed in the package virtualbox - 5.2.8-dfsg-3 --- virtualbox (5.2.8-dfsg-3) unstable; urgency=medium * Do not delay startup because of notify-send not being ready (Closes: #880594, LP: #1722745) -- Gianfranco Costamagna Fri, 16 Mar

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

Hello, let me know if the ongoing upload will fix (it will go in bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722745 Title: Virtualbox service fails to start due to hanging plymouth

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

As wrote previous this problem still exists. I use kernel 4.13.0-32. Only kill plymouth processes allow to start VirtualBox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722745 Title: Virtualbox

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

Have the exact same issue on 4.13.0-25-generic since today -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722745 Title: Virtualbox service fails to start due to hanging plymouth --ping response

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

On my home PC, there are no plymouth processes after the boot up process is complete and I have logged in. On my work machine however, where I am having this problem, I have plymouth processes as described in comment #4 after logging in and for the duration of the session (a few days). The

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

To my understanding plymouth should to stay started once the system is booted no ? I killed all plymouth processes, then I was able to start the virtualbox service via systemd properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: virtualbox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722745 Title:

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

Seeing this with other services now: ... Setting up apport (2.20.7-0ubuntu3.1) ... Installing new version of config file /etc/apport/crashdb.conf ... Job for apport.service failed because a timeout was exceeded. See "systemctl status apport.service" and "journalctl -xe" for details.

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

** Tags added: plymouth-ping -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722745 Title: Virtualbox service fails to start due to hanging plymouth --ping response To manage notifications about

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

So what is the state of the plymouth service when this happens? What does 'strace plymouth --ping' show about why this process is hanging? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722745

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

sudo systemctl virtualbox restart you mean: sudo systemctl restart virtualbox I'm reassigning to plymouth, not sure why vbox should be the culprit here ** Package changed: virtualbox (Ubuntu) => plymouth (Ubuntu) ** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

I have this problem again, however this time I updated a bunch of packages and rebooted straight away and now have the problem after boot. $ sudo systemctl virtualbox restart Unknown operation virtualbox. $ ps aux | grep plymouth root 735 0.0 0.3 139000 28576 ?S08:37 0:00

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

I didn't manually do it, as the above commands would automatically restart it. modprobe vboxdrv loaded but I wasn't able to fire up the VM's. I just did a soft reboot due to a large chunk of updates landing and everything is working fine now. I'll continue to monitor for the next week. **

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

did you try a systemctl virtuabox restart? seems that the dkms went fine, so probably just a modbprobe vboxdrv is sufficient ** Changed in: virtualbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

** Description changed: I am unable to start any Vagrant VM's due to the virtualbox service not being able to start or restart. $ VBoxManage --version WARNING: The character device /dev/vboxdrv does not exist.   Please install the virtualbox-dkms package and the appropriate