03-24-2018, 04:24 PM
[member=6629]ralphy[/member]
The v-box packages are definitely the issue but its frustrating to try to track any known bugs. It may be the kernel vrs. package repo involving the qt5 lib, given that v-box uses the one from Ubu 16.10 even though it's listed the same in 16.04. It may also be the v-box login message application, which may be deprecated relative to lightdm. I am leaning toward a combination of factors that are causing the issue in the v-box updates. In any case I have an updated v-LL 3.8 running on my Deb machine again.
For now your method works for installation.
1) Do NOT install updates during installation, or third party software.
2) Do NOt select autologin during installation.
3) After the system reboots and is up and running HOLD the three v-box packages BEFORE running updates.
TC
The v-box packages are definitely the issue but its frustrating to try to track any known bugs. It may be the kernel vrs. package repo involving the qt5 lib, given that v-box uses the one from Ubu 16.10 even though it's listed the same in 16.04. It may also be the v-box login message application, which may be deprecated relative to lightdm. I am leaning toward a combination of factors that are causing the issue in the v-box updates. In any case I have an updated v-LL 3.8 running on my Deb machine again.
For now your method works for installation.
1) Do NOT install updates during installation, or third party software.
2) Do NOt select autologin during installation.
3) After the system reboots and is up and running HOLD the three v-box packages BEFORE running updates.
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.