What does this mean: ...exclusive lock on the packaging backend.... ???
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am not familiar with Kubuntu, but it appears as if another service is running in the background checking for updates. Linux ensures only one such program at a time has access to the system. I use Fedora KDE and I prefer to use 'yum' from the command line instead of allowing KPackageKit to check for updates. When I try to rum 'yum' while KPK is running, I get a similar error message. I then use the system monitor to isolate and kill KPackageKit, and then I am able to "free up" the lock. I hope this is helpful.
When you post command line output then please use code-tags. Don't use the quick answer field at the end of the thread. Click on the 'Post reply' button instead. You can then insert [code][/code] tags by clicking on # symbol.
bhakta@Krishna-PC:~$ sudo aptitude search flash
[sudo] password for bhakta:
sudo: aptitude: command not found
Hm, this does not look right. It seems that you do not have aptitude installed. But you said that you are using Kunbuntu. I am not familiar with that particular distro. So I do not know if it uses some alternative to aptitude. Well, in any case this should (hopefully) work:
Perhaps in a previous instance, synaptic or apt hasnt exited gracefully, and there is a stale lock file?
In which case, the lock file can be safely removed, as it will be created again when synaptic/apt is next run.
t'be sure t'be sure, reboot, that will make sure there are no processes accessing the lock file, if the problem still persists, remove the lock file, and try again.
While performing the suggestions in post #12, I saw this after the 'update' command:
234 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 233 MB/233 MB of archives.
After this operation, 520 kB disk space will be freed.
Do you want to continue [Y/n]? y
Get:1 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main dpkg amd64 1.16.0~ubuntu7.1 [1,915 kB]
0% [1 dpkg 1,703 kB/1,915 kB 88%] 82.9 kB/s 46min 32s^
It seems that there indeed is a locked up file, and the upgrade process is stalled. It has been stuck for about 10 min (with good www connection).