Opened 9 years ago
Closed 9 years ago
#14910 closed defect (fixed)
VirtualBox --startvm should notify about a new ext-pack after upgrade
| Reported by: | LocutusOfBorg | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.0.10 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | all |
Description
Hi, as spotted by this Ubuntu bug [1], virtualbox when upgraded doesn't always notify about a old ext-pack version, and this leads to a crash. examples of missing notify is when it is started by shell, with --startvm parameter.
a fix should be rolled if possible to all maintained branches, because this is making difficult to update virtualbox for Debian and Ubuntu stable releases.
[1] https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1520656
thanks!
G.
Change History (2)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This problem was fixed in another way. If there was an incompatible change in the API used by the ExtPack then the (old) ExtPack will not be available and the error message will mention that the "unavailable ExtPack" could be due to the incompatible change.
The upgrade may lead to a crash (not the normal case). I agree that VirtualBox should warn the user if the version of the Extension Pack is older than the version of the VirtualBox base package.