LINUX

Search This Blog

social media tools

February 29, 2024

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

https://scripai.com/youtube-hashtag

social media

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Comments

Fix “Implementation of the USB 2.0 controller not found!” VirtualBox Error

Fix “Implementation of the USB 2.0 controller not found!” VirtualBox Error Today I started my Ubuntu virtual machine from Oracle VirtualBox and encountered with the following error: Implementation of the USB 2.0 controller not found! Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings. Note! This error could also mean that an incompatible version of the 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND). Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} Virtualbox error - Implementation of the USB 2.0 controller not found As you may have already guessed, this error usually occurs if you are running outdated version of VirtualBox extension pack. Fix "Implementation of the USB 2.0 controller not found!"

How to fix "another app is currently holding the yum lock" error

How to fix "another app is currently holding the yum lock" error Table of Contents Method 1: Kill the locked process to fix "another app is currently holding the yum lock" Method 2: Use DNF instead of YUM YUM vs DNF If you are working with Linux environment, you must have once in your carrier ended up with this error " another app is currently holding the yum lock " or " Existing lock /var/run/yum.pid: another copy is running as pid XXX " while executing yum. I mostly use RHEL/CentOS environment in my work life so will only talk about this distribution. But i can say with some confidence that the same steps should work with SuSE environment. Now this error " another app is currently holding the yum lock " is seen mostly with older yum versions especially with YUMv3 which was part of RHEL/CentOS 6 and also some versions of RHEL/CentOS 7. Now with RHEL 7.7, Red Hat has moved to YUMv4. We will discuss ab

YUM Remove Repo (Repository) – YUM Disable Repo (Repository)

Quick guide, howto remove and disable YUM repo (repository). Yum command itself does not contain any way to remove the repository. YUM repo files is located in /etc/yum.repos.d/ directory. I use kde.repo file with following content as example on this guide: Shell [kde] name=kde mirrorlist=http://apt.kde-redhat.org/apt/kde-redhat/fedora/mirrors-stable gpgkey=http://apt.kde-redhat.org/apt/kde-redhat/kde-redhat.RPM-GPG-KEY enabled=1 0 1 2 3 4 5 6 [ kde ] name = kde mirrorlist = http : / / apt .kde - redhat .org / apt / kde - redhat / fedora / mirrors - stable gpgkey = http : / / apt .kde - redhat .org / apt / kde - redhat / kde - redhat .RPM - GPG - KEY enabled = 1 Remove YUM Repo (Repository) Permanently Before moving repository permanently is a good idea to check that is the repository installed using rpm package. As many repos usually are, like RPM-Fusion, Livna, etc. Search Repository RPM-package with following command:

Powered by Blogger

social media tools

Comments

Post a Comment