Linux Lite Forums

General => Security & Bug Fixes => Topic started by: Edgewood on March 23, 2018, 03:14:42 PM

Title: VirtualBox Update Bug Linux Lite
Post by: Edgewood on March 23, 2018, 03:14:42 PM
I did an update on a 3.2 and a 3.6 version of a VMWARE machine...and had issues after restart. Nothing except minor programs would work. So, I have done this several times since. Installed a fresh copy of 3.8 as a virtual machine (two different versions of vmware so far - 10 & 14) and then shut it down so I could make a copy of the fresh version. Then I restarted and INSTALLED all the LATEST UPDATES...and restarted...BAM!...nothing works. I get a consistent "Indicator Plugin unexpectedly left the panel" error. I can't do much more than that at this point. So SOMETHING in the latest update is killing vmware machines. 
Title: Re: VirtualBox Update Bug Linux Lite
Post by: ralphy on March 23, 2018, 03:34:50 PM
I'm running latest 3.8 version on VMWare with all updates. I haven't experienced this issue myself. Will be firing up another VM on Workstation 14 Pro to see if I can duplicate this issue and report back.


Installing updates now (182 updates available on fresh install)...
Title: Re: VirtualBox Update Bug Linux Lite
Post by: trinidad on March 23, 2018, 04:13:20 PM
I'd guess you have to install Ubuntu vmtools again after updating to the virtual system, like a few years back. Happens with AMD expecting OEM tools.

TC
Title: Re: VirtualBox Update Bug Linux Lite
Post by: ralphy on March 23, 2018, 04:20:05 PM

Just ran updates and rebooted. Desktop came back just fine with a minor issue though. The Plugin Indicator seems to have broke during the update.


This is what I recommend for you to do:


1- Instead of installing updates using the Install Updates tool in Linux Lite:


- Update from Terminal with sudo apt-get update && sudo apt-get upgrade
You will be prompted during updates installation to replace or keep some grub files. ALWAYS keep the current file in the system when prompted.


- Or use Update Manager for Linux Lite (https://unlockforus.com/update-manager-linux-lite-3-x-series/): It will also ask you to keep or replace those files when running updates. ALWAYS keep the current file in the system when prompted.


I think I now have an idea of what's causing quite a few reports of broken systems after install:


1- Kernel updates that simply don't play nice with the hardware (reverting to earlier kernel with correct the problem for users in most cases)
2- Install Updates may be replacing some files without asking the user whether to keep it or replace it (https://github.com/linuxlite/litesoftware/blob/master/usr/scripts/updates-gui#L177).


Running manual updates or using Update Manager allows the user to opt-out or a file replacement. That might explain the reason why I don't find myself having the issue in the first place (I use Update Manager instead of Install Updates).


Now back to find out what broke the Indicator Plugin... but this is a different beast that shouldn't leave anyone without a fully useable Desktop.


Those are my findings so far.


My assessment is completely wrong. My fresh VM is also broken as the OP states.
Title: Re: VirtualBox Update Bug Linux Lite
Post by: trinidad on March 23, 2018, 06:09:56 PM
I broke 3 LL vms this month (all on AMDs). I think it's the kernel change to retpoline. The Deb VMs run fine but they were vm images to begin with. I have tried all the known fixes from the past (vmtools, video mem, etc.) to no avail. I was just waiting for this topic to turn up again. Not much is being said elsewhere so I assumed it was operator error on my part. It's Ubuntu and AMD somehow. My old core2 duo Dell has no issue, in Deb, LL, or Ubuntu. I guess I'll take it seriously and look deeper now. LL may have to package a separate vm image otherwise.

TC
Title: Re: VirtualBox Update Bug Linux Lite
Post by: supergamer on March 23, 2018, 06:23:09 PM
I'm running an AMD 565 with the 4.13.0-38 hwe kernel and do not have any of these issues. I actually have just rolled several test iso's the last couple of days without any issues at all from Virtualbox.
Title: Re: VirtualBox Update Bug Linux Lite
Post by: ralphy on March 23, 2018, 07:24:35 PM
I've installed LL 5 times already to pinpoint exactly why it is breaking... I think I'm getting closer.

So far what I can say that broke in previous install is policykit-1-gnome... it fails to authenticate against session and hence apps won't launch, which make it look like everything is broken when in fact the authentication agent is what fails to start.

After I complete my fifth installation which is what I'm testing now, I believe that what's happening is that somehow the agent is failing when the primary sudoer account is created and set for auto-login during installation.

I'm running updates right now to see if it breaks again. If it doesn't break my previous description is certainly what causes the problems in the previous four installs.

It has been the authentication agent all along nevertheless.
Title: Re: VirtualBox Update Bug Linux Lite
Post by: ralphy on March 23, 2018, 09:13:01 PM
@Edgewood - virtualbox updates is what's causing the issue for the most part.  As long as these updates are not installed there will be no issues with the VM. Tested on VMWare Workstation Pro 14, VMWare Fusion and ESXi.

Also during updates I kept all original files when prompted (/etc/issue, etc/release and so on.) I installed every single update with VNC enabled and disabled, no vmware-tools installed and also no open-vm-tools installed just to make sure it was not a conflict between packages.


(https://i.imgur.com/TnliD0I.png)


So, I would certainly hold those packages and wait for the next update and test again, but for now, if installed on a VMWare VM it will kill it. As I mentioned before, it seems to prevent policykit-1-gnome from launching which basically gives you a blank screen... lightdm/session cannot authenticate due to the missing authentication agent.


Code: [Select]
sudo apt-mark hold virtualbox-guest-dkms
sudo apt-mark hold virtualbox-guest-utils
sudo apt-mark hold virtualbox-guest-x11

OR


Code: [Select]
sudo apt-mark hold virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11
Which of the three packages is the one actually killing it, I didn't test between those three because they pretty much depend on each other, so by default users will be prompted to install at least two of the tree packages due to their mutual dependency. I might run some tests later. And it makes sense after all because other users have reported having issues after installing virtualbox updates (here in the forum - recent days).


Another thing I noticed,  is that policykit failed to autostart when the primary user is set to auto-login during installation. It did the same for me twice, whether I installed updates or not during the installation process. virtualbox packages do not get updated during installation though, so there are two different scenarios in which we can end up with a blank screen VM or a VM that doesn't launch applications that requires administrative privileges due to the broken authentication agent.


Finally, I tested Install Updates (https://github.com/linuxlite/litesoftware/blob/master/usr/scripts/updates-gui#L177 (https://github.com/linuxlite/litesoftware/blob/master/usr/scripts/updates-gui#L177)) and in the case of these packages they are defaulting to keep the original file, so users shouldn't have had any issues because of the non-interactive install.


That's what I've found during my tests. Maybe someone else wants to try to replicate this.
Title: Re: VirtualBox Update Bug Linux Lite
Post by: trinidad on March 24, 2018, 12:24:17 PM
@ralphy

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



Title: Re: VirtualBox Update Bug Linux Lite
Post by: ch289 on March 24, 2018, 12:31:05 PM
So good to come here and see you all already figuring out exactly the problem I was having  ;)

Am I correct in understanding then that the only solution for now is to abandon any VMs that had the update without those packages being held?

Thanks for all your work on this excellent distro
Title: Re: VirtualBox Update Bug Linux Lite
Post by: trinidad on March 24, 2018, 01:54:19 PM
Unfortunately removing the package from the terminal will not collect the dependencies broken or unbroken to fix correctly, so yes you are probably better off to reinstall.

Yep. Tracked down the beginning of the problem. V-box updates for guest additions are from the 18.04 Ubu repos. Don't bother with them as they are buggy and have several ongoing issues. HOLD v-box updates unless you are on at least 4.13 HWE running Intel or 4.15 kernel. Also policy kit is out of date as well in LTS. Best to hold for now and wait. I think it would be best to just hold them back for now in the restricted repo for LL or people installing/running VMs are going to continue crashing them with updates. I didn't think of it immediately but it would be nice to see the install log from someone with a crashed vm. Here I think on the vm os  /var/log/vboxadd-setup.log

TC
Title: Re: VirtualBox Update Bug Linux Lite
Post by: trinidad on March 26, 2018, 10:10:01 AM
Installing a new LL VM, or updating a running LL VM.

Be aware that updating virtual box guest will cause your LL VM to crash for one/or/all of at least three reasons on some machines. Best to follow the workaround below.

When installing:
Do NOT choose to update or install third party software during installation.
Do NOT enable auto-login during the installation process.
Do NOT update after installation until you HOLD virtual box guest additions updates.

If you have a running an LL VM now HOLD the virtual box guest additions before updating. See below.
sudo apt-mark hold virtualbox-guest-dkms
sudo apt-mark hold virtualbox-guest-utils
sudo apt-mark hold virtualbox-guest-x11

This bug does not affect all users but is significant enough to report as such.

TC



Title: Re: VirtualBox Update Bug Linux Lite
Post by: Jerry on March 26, 2018, 12:16:03 PM



This bug does not affect all users but is significant enough to report as such.

TC
[/size]

Agreed.

Have been following these threads since they started. Thanks to everyone for their input.

Sent from my Mobile phone using Tapatalk

Title: Re: VirtualBox Update Bug Linux Lite
Post by: The Repairman on March 26, 2018, 03:42:00 PM
 8)
Title: Re: VirtualBox Update Bug Linux Lite
Post by: bonnevie on March 26, 2018, 07:54:02 PM
@The Repairman
It's optional.  You have to select it in your Linux Software Whisker Menu.  So no, it's not in your default install.

Title: Re: VirtualBox Update Bug Linux Lite
Post by: The Repairman on March 27, 2018, 12:52:09 AM
 8)
Title: Re: VirtualBox Update Bug Linux Lite
Post by: Skello on March 27, 2018, 04:40:20 AM
This might explain the issue I'm having.

I had an older Linux Lite deployment in a Proxmox VM (QEMU) that I used occasionally. I installed the latest updates yesterday and after reboot I no longer got a login screen. When I connected to it remotely via No Machine, the client said that no display was configured and offered to configure one. This happens after every reboot, but locally I can no longer log in. The video adapter for the VM in Proxmox is set to "vmware compatible". At first I thought the new kernel was the issue, but even booting with the old kernel did not fix the issue. I remember that the virtualbox-guest-* packages were part of the latest updates.

I then just wiped the VM and recreated it from scratch, installing Linux Lite 3.8 64-bit. It all went OK and was able to boot into it, but after the first series of updates the same thing happened. Black screen at boot, no login prompt. Switching the VM's video adapter to something else doesn't fix the issue.
Title: Re: VirtualBox Update Bug Linux Lite
Post by: Frank on April 04, 2018, 07:17:28 PM
Assuming I've run into this bug, how can I fix it after the fact?

I'm running it (in a few places) on VirtualBox... and I've long ago done the following:


Any way I can fix the installations or do I need to rebuild the VMs?

The exact problem I'm having is that some programs won't open such as (but not only) Firefox, Chromium, Lite Tweaks, and System Log...


Update, I've fixed it

For others, I've fixed it by removing the packages listed above. I'll now follow the advice and hold those packages for now.




Title: Re: VirtualBox Update Bug Linux Lite
Post by: TheDead on April 09, 2018, 11:10:18 AM
I had to install LL 3.8 x64 in VirtualBox this weekend.
Installed "3rd party..." during setup.
Put the three suggested apt-mark suggested by @trinidad and updated without problem.
Tools still worked afterwards (not broken).
But, was wondering if the problem was fixed in updates of maybe Lite Updates was modifed to prevent the problem?

Cheers!
Title: Re: VirtualBox Update Bug Linux Lite
Post by: bigmanstrat on April 17, 2018, 05:32:50 AM
I  had this problem which meant that some of the graphic applications that accessed the internet (Chrome, Team Viewer) wouldn't work although I could carry out an upgrade from the terminal.  I have 2 devices running LL 3.8 an Intel laptop and an AMD desktop.  The Intel laptop has not been affected but the AMD desktop has been.  Did a bit of googling and found this solution on a Linux Mint forum:


https://forums.linuxmint.com/viewtopic.php?t=266442


I removed the virtualbox related packages and the destop started working immediately on a reboot.  Have updated LL files subsequently and it is still working.
Title: Re: VirtualBox Update Bug Linux Lite
Post by: TheDead on April 17, 2018, 11:16:52 AM
Maybe put this in sticky? Seems to come up regularly... until the issue is fixed I guess.

Cheers!
Title: Re: VirtualBox Update Bug Linux Lite
Post by: Jerry on April 17, 2018, 09:38:35 PM
Topics merged, title updated.
Title: Re: VirtualBox Update Bug Linux Lite
Post by: Kurt_R on May 03, 2018, 08:39:33 PM
@Edgewood


(https://i.imgur.com/TnliD0I.png)


Howdy, can you please let me know how you got that, "Update Manager" in LL?

Thanks, in advance.
Title: Re: VirtualBox Update Bug Linux Lite
Post by: ralphy on May 03, 2018, 08:47:43 PM
Howdy, can you please let me know how you got that, "Update Manager" in LL?

Thanks, in advance.

@Kurt_R here (https://unlockforus.com/update-manager-linux-lite-3-x-series/).
Title: Re: VirtualBox Update Bug Linux Lite
Post by: TheDead on May 03, 2018, 11:45:28 PM
Hey all thread readerz ;)

Anyone has info if the issue was fixed with another update?
... or maybe if not affected with a newer kernel?
Its been a few weeks now. Duh duh duuuuh! (for more drama)

Cheers!
Title: Re: VirtualBox Update Bug Linux Lite
Post by: ralphy on May 04, 2018, 01:30:10 AM
Hey all thread readerz ;)

Anyone has info if the issue was fixed with another update?
... or maybe if not affected with a newer kernel?
Its been a few weeks now. Duh duh duuuuh! (for more drama)

Cheers!

I believe that it hasn't been fixed. Those updates come from upstream and they are pulling bionic updates which certainly causes issues with xenial (LL 3.x). Users on the 4.x (beta) should be able to install them without problems; for 3.x users those updates should be avoided.
Title: Re: VirtualBox Update Bug Linux Lite
Post by: Jerry on May 04, 2018, 02:14:43 AM
We're not the only Distro experiencing this. Mint for example is to despite their 'safe updates' methodology. Thanks to the wonderful folks here, the fix is documented.

Sent from my Mobile phone using Tapatalk
Title: Re: VirtualBox Update Bug Linux Lite
Post by: TheDead on May 04, 2018, 09:08:45 PM
I know Jerry, it's not just a Linux Lite thingy, I was NOT pointing a finger like the angry monkey.
(http://stayworkplay.org/wp-content/uploads/EvilMonkey-300x210.jpg)

Do not feel ashamed, do not feel sad, the Resistance will follow their unyielding leader.
People will still love you and M. Gates fear you!
May your week-end be blessed with Treasure and Glory!
FOR THE HORDE!

Jerry the Unyielding! ... a Paladin maybe?
Title: Re: VirtualBox Update Bug Linux Lite
Post by: Jerry on May 04, 2018, 09:37:41 PM
@TheDead :)
Title: Re: VirtualBox Update Bug Linux Lite
Post by: Kurt_R on June 27, 2018, 02:42:46 PM
Howdy, can you please let me know how you got that, "Update Manager" in LL?

Thanks, in advance.

@Kurt_R here (https://unlockforus.com/update-manager-linux-lite-3-x-series/).

I just installed LL 4.0, does this "Update Manager" option still work in 4?
I guess I can try it out myself but didn't want to break anything majorly.
Title: Re: VirtualBox Update Bug Linux Lite
Post by: lucasmz0800 on October 26, 2018, 11:25:36 AM
I had a problem before related that try to install gcc-8 and then when ask for the gcc8 give it the location and the virtual box package will be compilated.