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

[Bruce Pieterse]

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 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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Launchpad Bug Tracker]

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 2018
13:56:41 +0100

** Changed in: virtualbox (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[LocutusOfBorg via ubuntu-bugs]

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 --ping
  response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Grzegorz Rajda]

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 service fails to start due to hanging plymouth --ping
  response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Matthijs Lambooy]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Bruce Pieterse]

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 plymouth process as far as I know, is suppose to terminate before or
once the login screen is displayed.

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Marc MAURICE]

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.
https://bugs.launchpad.net/bugs/1722745

Title:
  Virtualbox service fails to start due to hanging plymouth --ping
  response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Launchpad Bug Tracker]

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:
  Virtualbox service fails to start due to hanging plymouth --ping
  response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Bruce Pieterse]

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.
invoke-rc.d: initscript apport, action "start" failed.
● apport.service - LSB: automatic crash report generation
   Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
   Active: failed (Result: timeout) since Fri 2017-10-27 08:32:10 SAST; 10ms ago
 Docs: man:systemd-sysv-generator(8)
  Process: 28855 ExecStart=/etc/init.d/apport start (code=killed, signal=TERM)
Tasks: 2 (limit: 4915)
   CGroup: /system.slice/apport.service
   └─28858 plymouth --ping

Oct 27 08:27:10 hostname systemd[1]: Starting LSB: automatic crash report 
generation...
Oct 27 08:32:10 hostname systemd[1]: apport.service: Start operation timed out. 
Terminating.
Oct 27 08:32:10 hostname systemd[1]: Failed to start LSB: automatic crash 
report generation.
Oct 27 08:32:10 hostname systemd[1]: apport.service: Unit entered failed state.
Oct 27 08:32:10 hostname systemd[1]: apport.service: Failed with result 
'timeout'.
Setting up gir1.2-mutter-1:amd64 (3.26.1-2ubuntu2) ...
Setting up mutter (3.26.1-2ubuntu2) ...
...

strace as requested.

** Attachment added: "strace-plymouth-ping.txt"
   
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+attachment/4997508/+files/strace-plymouth-ping.txt

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Brian Murray]

** 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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Steve Langasek]

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

Title:
  Virtualbox service fails to start due to hanging plymouth --ping
  response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[LocutusOfBorg]

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

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Bruce Pieterse]

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 
@sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
root  1029  0.0  0.0  12936  1124 ?Ss   08:37   0:00 /bin/plymouth 
--wait
root  1290  0.0  0.0  12936  1076 ?S08:37   0:00 /bin/plymouth 
quit
root  1376  0.0  0.0  12936  1128 ?S08:37   0:00 plymouth --ping
root  1377  0.0  0.0  12936  1016 ?S08:37   0:00 plymouth --ping
root  1381  0.0  0.0  12936  1040 ?S08:37   0:00 plymouth --ping

Plymouth is waiting, quiting, pinging.

$ sudo service virtualbox restart is the only thing that works, but you
have to kill the latest plymouth --ping it spawns in order for the
service to start.

Starting the virtualbox service on boot can sometimes delay the boot up
process due to this bug.

** Changed in: virtualbox (Ubuntu)
   Status: Invalid => Incomplete

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Bruce Pieterse]

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.

** Changed in: virtualbox (Ubuntu)
   Status: Incomplete => Invalid

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[LocutusOfBorg]

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 Ubuntu.
https://bugs.launchpad.net/bugs/1722745

Title:
  Virtualbox service fails to start due to hanging plymouth --ping
  response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1722745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Bruce Pieterse]

** 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
    headers, most likely linux-headers-generic.
  
    You will not be able to start VMs until this problem is fixed.
  
  I tried reinstalling the virtualbox-dkms package, but the process takes
  a while to complete due to the virtualbox service timing out.
  
  $ sudo apt-get install virtualbox-dkms --reinstall
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 0 B/646 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 351318 files and directories currently installed.)
  Preparing to unpack .../virtualbox-dkms_5.1.28-dfsg-2_all.deb ...
  
   Uninstall Beginning 
  Module:  virtualbox
  Version: 5.1.28
  Kernel:  4.13.0-12-generic (x86_64)
  -
  
  Status: Before uninstall, this module version was ACTIVE on this kernel.
  
  vboxdrv.ko:
   - Uninstallation
     - Deleting from: /lib/modules/4.13.0-12-generic/updates/dkms/
   - Original module
     - No original module was found for this module on this kernel.
     - Use the dkms install command to reinstall any previous module version.
  
  vboxnetadp.ko:
   - Uninstallation
     - Deleting from: /lib/modules/4.13.0-12-generic/updates/dkms/
   - Original module
     - No original module was found for this module on this kernel.
     - Use the dkms install command to reinstall any previous module version.
  
  vboxnetflt.ko:
   - Uninstallation
     - Deleting from: /lib/modules/4.13.0-12-generic/updates/dkms/
   - Original module
     - No original module was found for this module on this kernel.
     - Use the dkms install command to reinstall any previous module version.
  
  vboxpci.ko:
   - Uninstallation
     - Deleting from: /lib/modules/4.13.0-12-generic/updates/dkms/
   - Original module
     - No original module was found for this module on this kernel.
     - Use the dkms install command to reinstall any previous module version.
  
  depmod...
  
  DKMS: uninstall completed.
  
  --
  Deleting module version: 5.1.28
  completely from the DKMS tree.
  --
  Done.
  Unpacking virtualbox-dkms (5.1.28-dfsg-2) over (5.1.28-dfsg-2) ...
  Setting up virtualbox-dkms (5.1.28-dfsg-2) ...
  Loading new virtualbox-5.1.28 DKMS files...
  Building for 4.13.0-12-generic
  Building initial module for 4.13.0-12-generic
  Done.
  
  vboxdrv:
  Running module version sanity check.
   - Original module
     - No original module exists within this kernel
   - Installation
     - Installing to /lib/modules/4.13.0-12-generic/updates/dkms/
  
  vboxnetadp.ko:
  Running module version sanity check.
   - Original module
     - No original module exists within this kernel
   - Installation
     - Installing to /lib/modules/4.13.0-12-generic/updates/dkms/
  
  vboxnetflt.ko:
  Running module version sanity check.
   - Original module
     - No original module exists within this kernel
   - Installation
     - Installing to /lib/modules/4.13.0-12-generic/updates/dkms/
  
  vboxpci.ko:
  Running module version sanity check.
   - Original module
     - No original module exists within this kernel
   - Installation
     - Installing to /lib/modules/4.13.0-12-generic/updates/dkms/
  
  depmod...
  
  DKMS: install completed.
  
  Job for virtualbox.service failed because a timeout was exceeded.
  See "systemctl  status virtualbox.service" and "journalctl  -xe" for details.
  invoke-rc.d: initscript virtualbox, action "restart" failed.
  ● virtualbox.service - LSB: VirtualBox Linux kernel module
     Loaded: loaded (/etc/init.d/virtualbox; generated; vendor preset: enabled)
     Active: failed (Result: timeout) since Wed 2017-10-11 10:24:15 SAST; 29ms 
ago
   Docs: man:systemd-sysv-generator(8)
    Process: 17897 ExecStart=/etc/init.d/virtualbox start (code=killed, 
signal=TERM)
  Tasks: 2 (limit: 4915)
     CGroup: /system.slice/virtualbox.service
     ├─ 1522 plymouth --ping
     └─17900 plymouth --ping
  
  At this point, we now have two plymouth --ping processes.
  
  After this I tried removing virtualbox and the virtualbox-dkms packages
  and tried to reinstall:
  
  $sudo apt-get remove virtualbox
  [sudo] password for bruce:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    libgsoap-2.8.49 libvncserver1
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
    virtualbox virtualbox-qt
  0 upgraded, 0 newly