FS#43098 - [virtualbox] missing procps-ng dependency

Attached to Project: Community Packages
Opened by Simon Peeters (SimonPe) - Saturday, 13 December 2014, 02:50 GMT
Last edited by Sébastien Luttringer (seblu) - Sunday, 14 December 2014, 02:04 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Virtualbox has problems running when certain commands are not available, one of them is ps, provided by the procps-ng package.
another one is ifconfig provide by the net-tools package.

note: afaik ifconfig is only needed to set up host-only adaptors.
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Sunday, 14 December 2014, 02:04 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.3.20-2
Comment by Karol Błażewicz (karol) - Saturday, 13 December 2014, 03:40 GMT
procps-ng belongs to the base group, which you should have installed: https://wiki.archlinux.org/index.php/Installation_guide#Install_the_base_packages While you can remove packages that are part of the base group, it's up to you to fix things when stuff breaks :-)
net-tools is mentioned as an optional dependency - check the output of 'pacman -Si virtualbox'.
Comment by Sébastien Luttringer (seblu) - Saturday, 13 December 2014, 12:21 GMT
Yes, net-tools is already an optional dep, so that's expected.

Could you tell me which command are broken when ps is missing?

@karol, the base group allows a simplified installation. If a package require another one, it should dep on it.
Comment by Simon Peeters (SimonPe) - Sunday, 14 December 2014, 00:51 GMT
well, without ps virtualbox is unable to keep track of running vm's, and ends up just reporting them as "powered off" even though they are running, this has serveral side effects:
- not being able to cleanly stop the vm, for some reason.
- vagrant is unable to launch vm's trough vboxmanage (because it always answers that the vm is powered off)
- probably a lot more wierd stuff (I had virtualbox crash a couple of times while trying to debug this)

Loading...