11 to 12 Upgrade Broken in VBox - and Another Minor 12 Issue

VirtualBox
1

Hi Patrick,

I’ve been running Qubes 3.1-rc2 almost exclusively, of late - and BTW, you and Joanna have done superb work in getting Whonix to work, properly, in Qubes. Thank you for that impressive Qubes effort!

On my VBox rigs, I tried upgrading the Gateway from 11 to 12, obviously, by running:

sudo apt-get update && sudo apt-get dist-upgrade

Normal 11 package updates would, of course, get installed, but 11 would never pull in the 12 package (set). Futhermore, whonixcheck would always report I was running 11.X-X.

I saw that same fail on two different fully updated OSes, both running VBox.

If you want to fix that upgrade fail, please do. In any event, I pulled the 12-releases of the Gateway and Workstation *.ova files, and both of those are running, correctly.

However, I did notice a minor issue, on both OSes. The very first time 12 is started, and you get to the ‘I understand/Agreement’ screen, as soon as I clicked on ‘I understand/Agreement’ my Gateway 12 went hard power down, immediately. On the subsequent 12 boot, all was OK, and working as expected.

You might want to find out if anyone else has seen this, and what is driving this issue, as it does not create a good first impression, especially for Whonix newbies.

Best regards,

CCP

2

Corrupt Correct Pig:

Normal 11 package updates would, of course, get installed, but 11 would never pull in the 12 package (set). Futhermore, whonixcheck would always report I was running 11.X-X.

Not a bug. Just a usability issue (since no one clicks the link or
cannot see it in terminal. The output will be removed unless running
with --verbose. Explained here:
systemcheck - Security Check Application

However, I did notice a minor issue, on both OSes, the very first time 12 is started, and you get to the ‘I understand/Agreement’ screen. As soon as you click on ‘I understand/Agreement’ my Gateway 12 went hard power down, immediately. On the subsequent VBox boot, all was OK, and working as expected.

You might want to find out if anyone has seen this, and what is driving this issue, as it does create a good first impression, especially for Whonix newbies.

This is the first report of this ever and the code for that hasn’t
changed in a long time. Are you sure you did not accidentally left the
pre-selected not-accept clicked? That would indeed lead to power off.