Unable to stop VIM with Kill, Htop, or anything else
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I'm running Ubuntu Bionic. I installed SLiM display manager so my GUI uses tty2 and I ran vim to edit some C++ code in tty1. Suddenly, it froze completely. I tried to type things but nothing would show up. I used ps -A to find the PID of vim, but even kill 14092 wouldn't work. I used htop and sent process 14092 a SIGTERM, but it hanged there. I sent it a SIGKILL, but it hanged there. I even nuked it with a SIGSEGV, but it still hanged there! How do I stop it?
Thank you very much.
EDIT:
I got it to stop after a reboot (well duh), but how can I do it in the future without the need for a reboot?
vim process kill htop
asked Jun 11 at 22:01
Baaing Cow
27428
 |Â
show 1 more comment
up vote
0
down vote
favorite
I'm running Ubuntu Bionic. I installed SLiM display manager so my GUI uses tty2 and I ran vim to edit some C++ code in tty1. Suddenly, it froze completely. I tried to type things but nothing would show up. I used ps -A to find the PID of vim, but even kill 14092 wouldn't work. I used htop and sent process 14092 a SIGTERM, but it hanged there. I sent it a SIGKILL, but it hanged there. I even nuked it with a SIGSEGV, but it still hanged there! How do I stop it?
Thank you very much.
EDIT:
I got it to stop after a reboot (well duh), but how can I do it in the future without the need for a reboot?
vim process kill htop
asked Jun 11 at 22:01
Baaing Cow
27428
Did you try logging out? I.e. kill the parent, reap the zombie. What state is the process in?
– ubfan1
Jun 12 at 23:15
I tried htop andps -l, but it wouldn't even show the process, onlyps -Awould ... ??? what is going on ??? ALso, normally zombies would die from being sent aSIGSEGV.
– Baaing Cow
Jun 12 at 23:16
Did you press Ctrl + S during your editing? if yes check this answer unix.stackexchange.com/questions/72086/…
– digiwizkid
Jun 12 at 23:25
No, I did not press Ctrl-S.
– Baaing Cow
Jun 12 at 23:31
Could it be possible the terminal window itself froze and not vim ?
– Sergiy Kolodyazhnyy
Jun 12 at 23:54
 |Â
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm running Ubuntu Bionic. I installed SLiM display manager so my GUI uses tty2 and I ran vim to edit some C++ code in tty1. Suddenly, it froze completely. I tried to type things but nothing would show up. I used ps -A to find the PID of vim, but even kill 14092 wouldn't work. I used htop and sent process 14092 a SIGTERM, but it hanged there. I sent it a SIGKILL, but it hanged there. I even nuked it with a SIGSEGV, but it still hanged there! How do I stop it?
Thank you very much.
EDIT:
I got it to stop after a reboot (well duh), but how can I do it in the future without the need for a reboot?
vim process kill htop
asked Jun 11 at 22:01
Baaing Cow
27428
I'm running Ubuntu Bionic. I installed SLiM display manager so my GUI uses tty2 and I ran vim to edit some C++ code in tty1. Suddenly, it froze completely. I tried to type things but nothing would show up. I used ps -A to find the PID of vim, but even kill 14092 wouldn't work. I used htop and sent process 14092 a SIGTERM, but it hanged there. I sent it a SIGKILL, but it hanged there. I even nuked it with a SIGSEGV, but it still hanged there! How do I stop it?
Thank you very much.
EDIT:
I got it to stop after a reboot (well duh), but how can I do it in the future without the need for a reboot?
vim process kill htop
asked Jun 11 at 22:01
Baaing Cow
27428
edited Jun 12 at 23:07
asked Jun 11 at 22:01
Baaing Cow
27428
asked Jun 11 at 22:01
Baaing Cow
27428
asked Jun 11 at 22:01
Baaing Cow
27428
27428
Did you try logging out? I.e. kill the parent, reap the zombie. What state is the process in?
– ubfan1
Jun 12 at 23:15
I tried htop andps -l, but it wouldn't even show the process, onlyps -Awould ... ??? what is going on ??? ALso, normally zombies would die from being sent aSIGSEGV.
– Baaing Cow
Jun 12 at 23:16
Did you press Ctrl + S during your editing? if yes check this answer unix.stackexchange.com/questions/72086/…
– digiwizkid
Jun 12 at 23:25
No, I did not press Ctrl-S.
– Baaing Cow
Jun 12 at 23:31
Could it be possible the terminal window itself froze and not vim ?
– Sergiy Kolodyazhnyy
Jun 12 at 23:54
 |Â
show 1 more comment
Did you try logging out? I.e. kill the parent, reap the zombie. What state is the process in?
– ubfan1
Jun 12 at 23:15
I tried htop andps -l, but it wouldn't even show the process, onlyps -Awould ... ??? what is going on ??? ALso, normally zombies would die from being sent aSIGSEGV.
– Baaing Cow
Jun 12 at 23:16
Did you press Ctrl + S during your editing? if yes check this answer unix.stackexchange.com/questions/72086/…
– digiwizkid
Jun 12 at 23:25
No, I did not press Ctrl-S.
– Baaing Cow
Jun 12 at 23:31
Could it be possible the terminal window itself froze and not vim ?
– Sergiy Kolodyazhnyy
Jun 12 at 23:54
Did you try logging out? I.e. kill the parent, reap the zombie. What state is the process in?
– ubfan1
Jun 12 at 23:15
Did you try logging out? I.e. kill the parent, reap the zombie. What state is the process in?
– ubfan1
Jun 12 at 23:15
I tried htop and
ps -l, but it wouldn't even show the process, only ps -A would ... ??? what is going on ??? ALso, normally zombies would die from being sent a SIGSEGV.– Baaing Cow
Jun 12 at 23:16
I tried htop and
ps -l, but it wouldn't even show the process, only ps -A would ... ??? what is going on ??? ALso, normally zombies would die from being sent a SIGSEGV.– Baaing Cow
Jun 12 at 23:16
Did you press Ctrl + S during your editing? if yes check this answer unix.stackexchange.com/questions/72086/…
– digiwizkid
Jun 12 at 23:25
Did you press Ctrl + S during your editing? if yes check this answer unix.stackexchange.com/questions/72086/…
– digiwizkid
Jun 12 at 23:25
No, I did not press Ctrl-S.
– Baaing Cow
Jun 12 at 23:31
No, I did not press Ctrl-S.
– Baaing Cow
Jun 12 at 23:31
Could it be possible the terminal window itself froze and not vim ?
– Sergiy Kolodyazhnyy
Jun 12 at 23:54
Could it be possible the terminal window itself froze and not vim ?
– Sergiy Kolodyazhnyy
Jun 12 at 23:54
 |Â
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045737%2funable-to-stop-vim-with-kill-htop-or-anything-else%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Did you try logging out? I.e. kill the parent, reap the zombie. What state is the process in?
– ubfan1
Jun 12 at 23:15
I tried htop and
ps -l, but it wouldn't even show the process, onlyps -Awould ... ??? what is going on ??? ALso, normally zombies would die from being sent aSIGSEGV.– Baaing Cow
Jun 12 at 23:16
Did you press Ctrl + S during your editing? if yes check this answer unix.stackexchange.com/questions/72086/…
– digiwizkid
Jun 12 at 23:25
No, I did not press Ctrl-S.
– Baaing Cow
Jun 12 at 23:31
Could it be possible the terminal window itself froze and not vim ?
– Sergiy Kolodyazhnyy
Jun 12 at 23:54