If Unity is running it's being very shy. I have the same problem on a different machine using a VM cloned from this one several weeks ago. A VM with a fresh install of 16.04 LTS works fine with the new packages for me, so perhaps this is a unique configuration issue. However, other than experimenting with launcher placement and turning low graphics on/off I haven't tweaked Unity settings to my recollection. I've noticed that CCSM when run from console (DISPLAY=:0 ccsm &) appears to hang at "Loading icons...", which may point in the right direction.
I have Hyper-V checkpoints immediately before and after installing the packages that break things for me, so I should be able to investigate any before/after question that might help.
To answer your specific questions, there are no dumps in /var/crash. I've attached before (working) and after (non-working) unity7 logs. I've generated them by restarting the VM from the aforementioned states and logging on, so the times in the logs might look inconsistent.
If Unity is running it's being very shy. I have the same problem on a different machine using a VM cloned from this one several weeks ago. A VM with a fresh install of 16.04 LTS works fine with the new packages for me, so perhaps this is a unique configuration issue. However, other than experimenting with launcher placement and turning low graphics on/off I haven't tweaked Unity settings to my recollection. I've noticed that CCSM when run from console (DISPLAY=:0 ccsm &) appears to hang at "Loading icons...", which may point in the right direction.
I have Hyper-V checkpoints immediately before and after installing the packages that break things for me, so I should be able to investigate any before/after question that might help.
To answer your specific questions, there are no dumps in /var/crash. I've attached before (working) and after (non-working) unity7 logs. I've generated them by restarting the VM from the aforementioned states and logging on, so the times in the logs might look inconsistent.