18.04 LTS won't let me re-login and shut down after failed apt get update [duplicate]











up vote
0
down vote

favorite













This question already has an answer here:




  • Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?

    21 answers




The machine was pretty slow already. However I decided to execute sudo apt-get update.



However the update stopped at 90% updating some trigger.



So I decided to log out and re login with user. However the system didn't let me log on any more.



So I decided to log on with an alternative user and triggered the update again, same message:



Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?


Then I tried a shutdown. Now I just see the Ubuntu logo and white/red dots moving from left to right.



This machine is important for me, what's the best thing to do for me now?



Should I just switch off power and reboot?



Your help is very much appreciated!










share|improve this question















marked as duplicate by N0rbert, user535733, karel, Fabby, Eric Carvalho Nov 29 at 9:55


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.















  • Did you do apt-get update or apt-get upgrade? The update shouldn't modify anything that could broke your system, it just updates apt/dpkg indices and caches.
    – Mr Shunz
    Nov 26 at 11:55










  • apt-get update. Is there a possibility to switch from splash screen to comand line to see shutdown? Or should I just turn off? (Shutdown now already takes many many minutes)
    – ssssstut
    Nov 26 at 11:59

















up vote
0
down vote

favorite













This question already has an answer here:




  • Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?

    21 answers




The machine was pretty slow already. However I decided to execute sudo apt-get update.



However the update stopped at 90% updating some trigger.



So I decided to log out and re login with user. However the system didn't let me log on any more.



So I decided to log on with an alternative user and triggered the update again, same message:



Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?


Then I tried a shutdown. Now I just see the Ubuntu logo and white/red dots moving from left to right.



This machine is important for me, what's the best thing to do for me now?



Should I just switch off power and reboot?



Your help is very much appreciated!










share|improve this question















marked as duplicate by N0rbert, user535733, karel, Fabby, Eric Carvalho Nov 29 at 9:55


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.















  • Did you do apt-get update or apt-get upgrade? The update shouldn't modify anything that could broke your system, it just updates apt/dpkg indices and caches.
    – Mr Shunz
    Nov 26 at 11:55










  • apt-get update. Is there a possibility to switch from splash screen to comand line to see shutdown? Or should I just turn off? (Shutdown now already takes many many minutes)
    – ssssstut
    Nov 26 at 11:59















up vote
0
down vote

favorite









up vote
0
down vote

favorite












This question already has an answer here:




  • Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?

    21 answers




The machine was pretty slow already. However I decided to execute sudo apt-get update.



However the update stopped at 90% updating some trigger.



So I decided to log out and re login with user. However the system didn't let me log on any more.



So I decided to log on with an alternative user and triggered the update again, same message:



Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?


Then I tried a shutdown. Now I just see the Ubuntu logo and white/red dots moving from left to right.



This machine is important for me, what's the best thing to do for me now?



Should I just switch off power and reboot?



Your help is very much appreciated!










share|improve this question
















This question already has an answer here:




  • Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?

    21 answers




The machine was pretty slow already. However I decided to execute sudo apt-get update.



However the update stopped at 90% updating some trigger.



So I decided to log out and re login with user. However the system didn't let me log on any more.



So I decided to log on with an alternative user and triggered the update again, same message:



Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?


Then I tried a shutdown. Now I just see the Ubuntu logo and white/red dots moving from left to right.



This machine is important for me, what's the best thing to do for me now?



Should I just switch off power and reboot?



Your help is very much appreciated!





This question already has an answer here:




  • Unable to lock the administration directory (/var/lib/dpkg/) is another process using it?

    21 answers








apt login






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 28 at 17:05









Zanna

49.2k13124234




49.2k13124234










asked Nov 26 at 11:33









ssssstut

315




315




marked as duplicate by N0rbert, user535733, karel, Fabby, Eric Carvalho Nov 29 at 9:55


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 N0rbert, user535733, karel, Fabby, Eric Carvalho Nov 29 at 9:55


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.














  • Did you do apt-get update or apt-get upgrade? The update shouldn't modify anything that could broke your system, it just updates apt/dpkg indices and caches.
    – Mr Shunz
    Nov 26 at 11:55










  • apt-get update. Is there a possibility to switch from splash screen to comand line to see shutdown? Or should I just turn off? (Shutdown now already takes many many minutes)
    – ssssstut
    Nov 26 at 11:59




















  • Did you do apt-get update or apt-get upgrade? The update shouldn't modify anything that could broke your system, it just updates apt/dpkg indices and caches.
    – Mr Shunz
    Nov 26 at 11:55










  • apt-get update. Is there a possibility to switch from splash screen to comand line to see shutdown? Or should I just turn off? (Shutdown now already takes many many minutes)
    – ssssstut
    Nov 26 at 11:59


















Did you do apt-get update or apt-get upgrade? The update shouldn't modify anything that could broke your system, it just updates apt/dpkg indices and caches.
– Mr Shunz
Nov 26 at 11:55




Did you do apt-get update or apt-get upgrade? The update shouldn't modify anything that could broke your system, it just updates apt/dpkg indices and caches.
– Mr Shunz
Nov 26 at 11:55












apt-get update. Is there a possibility to switch from splash screen to comand line to see shutdown? Or should I just turn off? (Shutdown now already takes many many minutes)
– ssssstut
Nov 26 at 11:59






apt-get update. Is there a possibility to switch from splash screen to comand line to see shutdown? Or should I just turn off? (Shutdown now already takes many many minutes)
– ssssstut
Nov 26 at 11:59












1 Answer
1






active

oldest

votes

















up vote
0
down vote













1) List apt process



ps -A | grep apt


this show like output:



12421 pts/1 00:00:00 apt
12445 pts/1 00:00:00 apt


2) Kill this process:
The process ID (PID) is found in the first column from the output above.



sudo kill -SIGKILL <PID>


3) Remove Lock



sudo rm /var/lib/dpkg/lock





share|improve this answer





















  • Because ctrl alt F1/F2 didn't let me log in I decided to switch off power. When I rebooted Luckily after reboot everything was fine. And btw: the command I executed was 'sudo apt upgrade' (I wanted to do updates but without any new kernels etc.)
    – ssssstut
    Nov 26 at 12:50










  • Thank you all very much for your help!
    – ssssstut
    Nov 26 at 12:50




















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













1) List apt process



ps -A | grep apt


this show like output:



12421 pts/1 00:00:00 apt
12445 pts/1 00:00:00 apt


2) Kill this process:
The process ID (PID) is found in the first column from the output above.



sudo kill -SIGKILL <PID>


3) Remove Lock



sudo rm /var/lib/dpkg/lock





share|improve this answer





















  • Because ctrl alt F1/F2 didn't let me log in I decided to switch off power. When I rebooted Luckily after reboot everything was fine. And btw: the command I executed was 'sudo apt upgrade' (I wanted to do updates but without any new kernels etc.)
    – ssssstut
    Nov 26 at 12:50










  • Thank you all very much for your help!
    – ssssstut
    Nov 26 at 12:50

















up vote
0
down vote













1) List apt process



ps -A | grep apt


this show like output:



12421 pts/1 00:00:00 apt
12445 pts/1 00:00:00 apt


2) Kill this process:
The process ID (PID) is found in the first column from the output above.



sudo kill -SIGKILL <PID>


3) Remove Lock



sudo rm /var/lib/dpkg/lock





share|improve this answer





















  • Because ctrl alt F1/F2 didn't let me log in I decided to switch off power. When I rebooted Luckily after reboot everything was fine. And btw: the command I executed was 'sudo apt upgrade' (I wanted to do updates but without any new kernels etc.)
    – ssssstut
    Nov 26 at 12:50










  • Thank you all very much for your help!
    – ssssstut
    Nov 26 at 12:50















up vote
0
down vote










up vote
0
down vote









1) List apt process



ps -A | grep apt


this show like output:



12421 pts/1 00:00:00 apt
12445 pts/1 00:00:00 apt


2) Kill this process:
The process ID (PID) is found in the first column from the output above.



sudo kill -SIGKILL <PID>


3) Remove Lock



sudo rm /var/lib/dpkg/lock





share|improve this answer












1) List apt process



ps -A | grep apt


this show like output:



12421 pts/1 00:00:00 apt
12445 pts/1 00:00:00 apt


2) Kill this process:
The process ID (PID) is found in the first column from the output above.



sudo kill -SIGKILL <PID>


3) Remove Lock



sudo rm /var/lib/dpkg/lock






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 26 at 12:06









Carlos Dagorret

32815




32815












  • Because ctrl alt F1/F2 didn't let me log in I decided to switch off power. When I rebooted Luckily after reboot everything was fine. And btw: the command I executed was 'sudo apt upgrade' (I wanted to do updates but without any new kernels etc.)
    – ssssstut
    Nov 26 at 12:50










  • Thank you all very much for your help!
    – ssssstut
    Nov 26 at 12:50




















  • Because ctrl alt F1/F2 didn't let me log in I decided to switch off power. When I rebooted Luckily after reboot everything was fine. And btw: the command I executed was 'sudo apt upgrade' (I wanted to do updates but without any new kernels etc.)
    – ssssstut
    Nov 26 at 12:50










  • Thank you all very much for your help!
    – ssssstut
    Nov 26 at 12:50


















Because ctrl alt F1/F2 didn't let me log in I decided to switch off power. When I rebooted Luckily after reboot everything was fine. And btw: the command I executed was 'sudo apt upgrade' (I wanted to do updates but without any new kernels etc.)
– ssssstut
Nov 26 at 12:50




Because ctrl alt F1/F2 didn't let me log in I decided to switch off power. When I rebooted Luckily after reboot everything was fine. And btw: the command I executed was 'sudo apt upgrade' (I wanted to do updates but without any new kernels etc.)
– ssssstut
Nov 26 at 12:50












Thank you all very much for your help!
– ssssstut
Nov 26 at 12:50






Thank you all very much for your help!
– ssssstut
Nov 26 at 12:50





Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕