If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
Please do not use the CODE tag when pasting content that contains formatting (colored, bold, underline, italic, etc).
The CODE tag displays all content as plain text, including the formatting tags, making it difficult to read.
First, make sure you don't have another package manager window or apt-get running somewhere.
The full error would be more helpful, but I think that we can get the right file here
Package managers, and some other programs use a "lock" file to prevent more than one instance of the program from running at the same time. In this instance, it is the package management system (apt and dpkg under the hood). Sometimes this lock file does not go away when there is a crash, the machine looses power, or whatever reason. All we have to do is delete the file that it is complaining about. Thing is, it can reside in a couple different places (I do not know why) but the line or two above the error you pasted would have given the full path in the message.
Something like E: Could not open lock file /var/lib/dpkg/lock
This is the offending "stale" lock file, and we would remove it using a file manager with admin privileges, or by:
sudo rm /var/lib/dpkg/lock
But we need to have the correct path to the file. If the above command does not remove a file (because it does not exist) you may have to run sudo apt-get dist-upgrade or similar command to see the full error message.
occasionally i get this when update manager is doing some business in taskbar, this mostly happens shortly after system boot.
oh, and mostly with Suse..
yes! im cheating on you Kubuntu ha ha
K 14.4 64 AMD 955be3200MHz 8GB 1866Mhz 6TB Plex/samba.etc.+ Macbook Air 13".
occasionally i get this when update manager is doing some business in taskbar, this mostly happens shortly after system boot.
oh, and mostly with Suse..
yes! im cheating on you Kubuntu ha ha
Well, yeah, as the updater is using the package management tools under the hood, this is to be expected.
There is no such thing as cheating, linux is polyamorous
Comment