Software updater has crashed [duplicate]
This question already has an answer here:
Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?
21 answers
Could not get lock /var/lib/apt/lists/lock [duplicate]
1 answer
Have been using 14.04 LTS for years with no problems.
Have tried sudo apt-get update and get:
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
14.04
edited Dec 23 '18 at 21:25
George Udosen
20.4k94367
asked Dec 23 '18 at 21:09
alanbalanb
234
marked as duplicate by WinEunuuchs2Unix, karel, Eric Carvalho, Fabby, Community♦ Dec 24 '18 at 22:40
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?
21 answers
Could not get lock /var/lib/apt/lists/lock [duplicate]
1 answer
Have been using 14.04 LTS for years with no problems.
Have tried sudo apt-get update and get:
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
14.04
edited Dec 23 '18 at 21:25
George Udosen
20.4k94367
asked Dec 23 '18 at 21:09
alanbalanb
234
marked as duplicate by WinEunuuchs2Unix, karel, Eric Carvalho, Fabby, Community♦ Dec 24 '18 at 22:40
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
As a new poster but long time Ubuntu User I upvoted your question and answer to give you more rep :). But sadly I had to vote your question as a duplicate :(
– WinEunuuchs2Unix
Dec 23 '18 at 21:31
add a comment |
This question already has an answer here:
Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?
21 answers
Could not get lock /var/lib/apt/lists/lock [duplicate]
1 answer
Have been using 14.04 LTS for years with no problems.
Have tried sudo apt-get update and get:
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
14.04
edited Dec 23 '18 at 21:25
George Udosen
20.4k94367
asked Dec 23 '18 at 21:09
alanbalanb
234
This question already has an answer here:
Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?
21 answers
Could not get lock /var/lib/apt/lists/lock [duplicate]
1 answer
Have been using 14.04 LTS for years with no problems.
Have tried sudo apt-get update and get:
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
This question already has an answer here:
Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?
21 answers
Could not get lock /var/lib/apt/lists/lock [duplicate]
1 answer
14.04
14.04
edited Dec 23 '18 at 21:25
George Udosen
20.4k94367
asked Dec 23 '18 at 21:09
alanbalanb
234
edited Dec 23 '18 at 21:25
George Udosen
20.4k94367
asked Dec 23 '18 at 21:09
alanbalanb
234
edited Dec 23 '18 at 21:25
George Udosen
20.4k94367
edited Dec 23 '18 at 21:25
George Udosen
20.4k94367
edited Dec 23 '18 at 21:25
George Udosen
20.4k94367
20.4k94367
asked Dec 23 '18 at 21:09
alanbalanb
234
asked Dec 23 '18 at 21:09
alanbalanb
234
asked Dec 23 '18 at 21:09
alanbalanb
234
234
marked as duplicate by WinEunuuchs2Unix, karel, Eric Carvalho, Fabby, Community♦ Dec 24 '18 at 22:40
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by WinEunuuchs2Unix, karel, Eric Carvalho, Fabby, Community♦ Dec 24 '18 at 22:40
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
As a new poster but long time Ubuntu User I upvoted your question and answer to give you more rep :). But sadly I had to vote your question as a duplicate :(
– WinEunuuchs2Unix
Dec 23 '18 at 21:31
add a comment |
As a new poster but long time Ubuntu User I upvoted your question and answer to give you more rep :). But sadly I had to vote your question as a duplicate :(
– WinEunuuchs2Unix
Dec 23 '18 at 21:31
As a new poster but long time Ubuntu User I upvoted your question and answer to give you more rep :). But sadly I had to vote your question as a duplicate :(
– WinEunuuchs2Unix
Dec 23 '18 at 21:31
As a new poster but long time Ubuntu User I upvoted your question and answer to give you more rep :). But sadly I had to vote your question as a duplicate :(
– WinEunuuchs2Unix
Dec 23 '18 at 21:31
add a comment |
2 Answers
2
active
oldest
votes
Usually your system or apt is doing some work behind the scenes so when you try to access the /var/lib[apt|dpkg] and the system has a lock on this location you get those errors.
Now to see who or what is holding that lock you can run:
sudo lslocks | grep -E "/var/lib/dpkg/lock"
answered Dec 23 '18 at 21:34
George UdosenGeorge Udosen
20.4k94367
add a comment |
Panic over, all seems to be working fine after I closed down and restarted.
Do not know why this has happened.
answered Dec 23 '18 at 21:24
alanbalanb
234
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Usually your system or apt is doing some work behind the scenes so when you try to access the /var/lib[apt|dpkg] and the system has a lock on this location you get those errors.
Now to see who or what is holding that lock you can run:
sudo lslocks | grep -E "/var/lib/dpkg/lock"
answered Dec 23 '18 at 21:34
George UdosenGeorge Udosen
20.4k94367
add a comment |
Usually your system or apt is doing some work behind the scenes so when you try to access the /var/lib[apt|dpkg] and the system has a lock on this location you get those errors.
Now to see who or what is holding that lock you can run:
sudo lslocks | grep -E "/var/lib/dpkg/lock"
answered Dec 23 '18 at 21:34
George UdosenGeorge Udosen
20.4k94367
add a comment |
Usually your system or apt is doing some work behind the scenes so when you try to access the /var/lib[apt|dpkg] and the system has a lock on this location you get those errors.
Now to see who or what is holding that lock you can run:
sudo lslocks | grep -E "/var/lib/dpkg/lock"
answered Dec 23 '18 at 21:34
George UdosenGeorge Udosen
20.4k94367
Usually your system or apt is doing some work behind the scenes so when you try to access the /var/lib[apt|dpkg] and the system has a lock on this location you get those errors.
Now to see who or what is holding that lock you can run:
sudo lslocks | grep -E "/var/lib/dpkg/lock"
answered Dec 23 '18 at 21:34
George UdosenGeorge Udosen
20.4k94367
answered Dec 23 '18 at 21:34
George UdosenGeorge Udosen
20.4k94367
answered Dec 23 '18 at 21:34
George UdosenGeorge Udosen
20.4k94367
answered Dec 23 '18 at 21:34
George UdosenGeorge Udosen
20.4k94367
20.4k94367
add a comment |
add a comment |
Panic over, all seems to be working fine after I closed down and restarted.
Do not know why this has happened.
answered Dec 23 '18 at 21:24
alanbalanb
234
add a comment |
Panic over, all seems to be working fine after I closed down and restarted.
Do not know why this has happened.
answered Dec 23 '18 at 21:24
alanbalanb
234
add a comment |
Panic over, all seems to be working fine after I closed down and restarted.
Do not know why this has happened.
answered Dec 23 '18 at 21:24
alanbalanb
234
Panic over, all seems to be working fine after I closed down and restarted.
Do not know why this has happened.
answered Dec 23 '18 at 21:24
alanbalanb
234
answered Dec 23 '18 at 21:24
alanbalanb
234
answered Dec 23 '18 at 21:24
alanbalanb
234
answered Dec 23 '18 at 21:24
alanbalanb
234
234
add a comment |
add a comment |
As a new poster but long time Ubuntu User I upvoted your question and answer to give you more rep :). But sadly I had to vote your question as a duplicate :(
– WinEunuuchs2Unix
Dec 23 '18 at 21:31