I went to the repos almost immediately upon encountering this bug and
downloaded and saved the 5.2.12-dfsg-3 pkgs. It looks like
5.2.12-dfsg-3 now has been removed. Whatever logic used in leaving the
broken 5.2.14-dfsg-1 up while removing the most recent functional
version (5.2.12-dfsg-3) is elusive.
On 07/09/2018 08:56 AM, Kent West wrote:
On Sun, 8 Jul 2018 16:01:00 -0500 "Steven R. Wright" <srwri...@anl.gov
<mailto:srwri...@anl.gov>> wrote:
> Obviously I merely downgraded to the last functioning version of
> virtualbox et. al. (5.2.12-dfsg-3) in unstable....
But how did you do this?
When I search packages.debian.org <http://packages.debian.org> for
"5.2.12-dfsg-3", I get "no results". I only find 5.2.10s and the
broken 5.2.14. When I installed the 5.2.10 ("aptitude install
virtualbox/stable") I then find no executable to start Virtualbox. So
I did an "aptitude remove virtualbox", followed by another "aptitude
install virtualbox/stable", which did more than the first install
(rebuilding modules, I believe), and ended with the
error/warning/notification "vboxweb.service is a disabled or a static
unit not running, not starting it.", and I still find no executable
with which to start Virtualbox.
Thanks!
--
Kent West <")))><
Westing Peacefully - http://kentwest.blogspot.com
