My question(s) are related to the sequence of the following actions:
i) I performed a fresh installation of 12.04 on a machine
ii) After the installation was complete and the media ( optical disk ) were removed ( as per the prompt ), I rebooted the machine and logged in into the brand-new system.
iii) I opened a terminal and tried to do an update of APT's cache ( sudo apt-get update
). This results in apt-get
reporting an error due to some conflict it detects ( indicated by the /var/lib/apt/lists/lock
file being locked by some other application )
This question ( or related questions ) seems to have been asked several times and one ( plausible ) post explains the error as having been caused by some updating software such as Software Center
or Synaptic
already running.
Is this systematic ( i.e. part of the installation process )?
Is the system trying to run
Synaptic
after a fresh installation ( ... perhaps as some automated post-installation sequence which runs on initial log-in )?Did I get the lock error for
apt-get update
because I was inadvertently interfering with another instance ofapt-get
or similar which gets started immediately after the first log in of a user after a fresh installation?
In short I would like to understand why this happened, because as outlined above, after the installation and my firs log-in, I did not launch or start any apps. >other< than the terminal (....from previous experience with the Synaptic package I knew that if you intend to use apt-get
you must make sure Synaptic
is not running..).
Note:
You only seem to get this when you try to run sudo apt-get
from one of the pseudo terminals within the X windowing system. You don't get the lock error if you use one of the virtual terminals ( the character based ones you get by doing 'Ctrl+Alt+F(1-6)').
Exact error messages ( added at request from one of the commenters @Sushantp606 ):
E: Could not get lock /var/lib/apt/lists/lock -open ( 11: Resource temporarily unavailable )
E: Unable to lock directory /var/lib/apt/lists/