In order to avoid this, please follow the instuctions on 1, 2, 3 and then PS 1 since that installation is done after the user has logged in their account and everything is decrypted.ġ. UPDATE: After some additional tests, I found out that on vm's that are installed on encrypted partitions or use encrypted home folders, the procedure may fail. So, let's go and do it:īEFORE YOU START DOING ANYTHING, I would strongly recommend you clone your affected vm using vbox's clone feature and work on the clone so that you won't damage your initial vm in case something goes terribly wrong. Luckily, Canonical has released two packages you can install on your guest systems and update them to use the new xorg subsystem and kernel used in version 12.10 without stopping using 12.04. The problem is caused by an incompatibility of the new VB additions with the xorg subsystem used in 12.04 and previous releases. Just follow the instructions and you'll be fine. This is the solution that I have checked and verified on 2 vm's and it's working. I faced this black screen problem right after the latest 4.2.12 update too.
0 kommentar(er)
