If you have Microsoft Teams installed on Ubuntu used with a company single sign-on page, you might have problems logging in with your personal Microsoft account.
If you want to clear any login info from Microsoft Teams. doing apt remove teams or apt purge teams won’t clear login cache, or company SSO page from the application, as those are stored inside you home folder.
To clear SSO page in Microsoft Teams on Ubuntu you need to remove its configurations files inside your home directory inside .config folder.
There are two folders related to Microsoft Teams, that get created in your user home folder, which get created when you run Microsoft Teams for the first time.
Those two folders are Microsoft/Microsoft Teams/ and Microsoft Teams - Preview/ inside .config folder in your home directory.
Their full paths, if you home folder is /home/$USER, will be /home/$USER/.config/Microsoft Teams - Preview/ and /home/$USER/.config/Microsoft/Microsoft Teams/, if you delete those folder, you will reset Microsoft Teams, as they were just freshly installed and never run before.
TLDR; to reset Microsoft Teams on Ubuntu as they were just freshly installed and remove company SSO page from it, do the following.
When doing a fresh install of Ubuntu 16.04, or any other version of Ubuntu or Linux, after the install you might get your laptop or desktop machine not booting the installed OS, but instead returning “No Bootable Device” message, if laptop is set to UEFI mode.
You might be presented with this image after rebooting your laptop, after a successful OS install.
To resolve this issue reboot your laptop and enter BIOS.
There go to “Select and UEFI file as trusted for executing:” and press Enter key.
Once there choose HDD1.
Then choose <EFI>.
Then you should be able to see <ubuntu> or possibly some other name of your Linux installation.
Then choose shimx64.efi
And then choose Yes when asked if you want to add this file to allowable database.
Reboot your laptop and you should now be able to boot your OS normally.
When trying to run VirtualBox on Ubuntu 16.04, or some other version of Linux, you might get a following type an error message, when trying to start a virtual machine, you just created on a fresh installation of VirtualBox.
VirtualBox might return error saying that it failed to open a session for the virtual machine.
Details of error message will say that virtual machine has terminated unexpectedly during startup with exit code 1 (0x1).
You will also get a “Kernel driver not installed (rc=-1908” message.
Error will say “The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv.”
Error message will ask you to try to reinstall the kernel module by executing /sbin/vboxconfig as root, to reinstall the module, which could fail to complete successfully when you try to run the command in terminal.
One of the possible causes of this type of behavior is that you have Secure Boot enabled in your BIOS on the host machine, which is preventing the install of third-party drivers, and causing issues with VirtualBox installation, which fails to install all kernel modules.
To resolve this error, disable Secure Boot in your BIOS, and then try to run /sbin/vboxconfig command as root, or reinstall VirtualBox, with Secure Boot disabled, to install all the necessary modules.