Tested the bugs that I could (so I was unable to test bugs that only applied to HiDPI screens or multi-monitor (please can people with these setups verify the bugs and then update to the relevant Proposed packages and test the fixes?)). I used VirtualBox on Ubuntu 17.10 to test 16.04. To test a bug on Ubuntu MATE (in that list), I (accidentally) installed mate-desktop and then (correctly) ubuntu-mate-desktop . This seemed to break some theming on the standard Unity desktop and also made it impossible for me to reproduce this bug because Ubuntu SDK seemed to be using MATE’s file manager rather than GNOME Files. Maybe this is to be expected, but perhaps in the future it would be nice to have it possible to install Ubuntu flavors without breaking the other flavors. Maybe this is impossible, though.

Many test cases weren’t as precise as they could’ve been so I was unable to follow them through, I’ve left comments asking for specific improvements in the test cases. I also got '‘No such key ‘lowgfx’’ when trying to run gsettings set com.canonical.Unity lowgfx false which prevented me from testing without lowgfx (I was unable to reproduce some bugs and thought this may have been because I was on lowgfx).

Note that if you’re testing the Unity that is in 16.04 Proposed, if you have set the pin priority so that you’re on 16.04 and not 16.04 Proposed, and you just selectively install packages from proposed (which is what the wiki recommends you to do), then to be able to sudo apt install unity/xenial-proposed you will need to do sudo apt install compiz-core/xenial-proposed compiz-plugins/xenial-proposed libcompizconfig0/xenial-proposed compiz-gnome/xenial-proposed compiz/xenial-proposed first (at least, until those packages are released from Proposed into 16.04 proper - it might be better if you just work out what you need to install by trying to install Unity from Proposed and installing other packages from Proposed as Apt prompts you to do so).

In the end, I’ve only tested the fixes for https://bugs.launchpad.net/unity/+bug/1316862 and https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1618405. The former is fixed by the new package, I think, the latter is not.

Sorry I couldn’t verify more and wow I’ve really stayed up too late (I’m GMT)…

Thanks for the great attention to detail Marco!