Htop signals seem not to be sent on (K)Ubuntu 18.04
Clash Royale CLAN TAG#URR8PPP
I am on Ubuntu 18.04 (Kubuntu), running through Konsole.
I have a node process I can see in htop if I F4 and search for node. I highlight it and use F9 to send it a signal (tried SIGINT, SIGQUIT, SIGTERM, SIGKILL), but nothing causes it to exit.
This is not specific to node, as I can't SIGKILL other things (for example the Kate text editor).
If I exit htop and simply type kill -SIGINT 6015 (PID taken from htop), the process exits properly.
Why is this not working?
I am guessing it has something to do with how the desktop version works, because on servers I have never had the issue of htop being unable to signal processes.
Another thing that goes contrary to my expectations is if I run sudo htop I can only see about 4 processes under my user (3 related to kde and one (sd-pam)) whereas running it as myself shows me 100+ (including node and all the other apps I have going). I would expect that running as root I would see all processes for all users.
kubuntu htop konsole
asked Jan 30 at 18:08
AlexAlex
83
add a comment |
I am on Ubuntu 18.04 (Kubuntu), running through Konsole.
I have a node process I can see in htop if I F4 and search for node. I highlight it and use F9 to send it a signal (tried SIGINT, SIGQUIT, SIGTERM, SIGKILL), but nothing causes it to exit.
This is not specific to node, as I can't SIGKILL other things (for example the Kate text editor).
If I exit htop and simply type kill -SIGINT 6015 (PID taken from htop), the process exits properly.
Why is this not working?
I am guessing it has something to do with how the desktop version works, because on servers I have never had the issue of htop being unable to signal processes.
Another thing that goes contrary to my expectations is if I run sudo htop I can only see about 4 processes under my user (3 related to kde and one (sd-pam)) whereas running it as myself shows me 100+ (including node and all the other apps I have going). I would expect that running as root I would see all processes for all users.
kubuntu htop konsole
asked Jan 30 at 18:08
AlexAlex
83
add a comment |
I am on Ubuntu 18.04 (Kubuntu), running through Konsole.
I have a node process I can see in htop if I F4 and search for node. I highlight it and use F9 to send it a signal (tried SIGINT, SIGQUIT, SIGTERM, SIGKILL), but nothing causes it to exit.
This is not specific to node, as I can't SIGKILL other things (for example the Kate text editor).
If I exit htop and simply type kill -SIGINT 6015 (PID taken from htop), the process exits properly.
Why is this not working?
I am guessing it has something to do with how the desktop version works, because on servers I have never had the issue of htop being unable to signal processes.
Another thing that goes contrary to my expectations is if I run sudo htop I can only see about 4 processes under my user (3 related to kde and one (sd-pam)) whereas running it as myself shows me 100+ (including node and all the other apps I have going). I would expect that running as root I would see all processes for all users.
kubuntu htop konsole
asked Jan 30 at 18:08
AlexAlex
83
I am on Ubuntu 18.04 (Kubuntu), running through Konsole.
I have a node process I can see in htop if I F4 and search for node. I highlight it and use F9 to send it a signal (tried SIGINT, SIGQUIT, SIGTERM, SIGKILL), but nothing causes it to exit.
This is not specific to node, as I can't SIGKILL other things (for example the Kate text editor).
If I exit htop and simply type kill -SIGINT 6015 (PID taken from htop), the process exits properly.
Why is this not working?
I am guessing it has something to do with how the desktop version works, because on servers I have never had the issue of htop being unable to signal processes.
Another thing that goes contrary to my expectations is if I run sudo htop I can only see about 4 processes under my user (3 related to kde and one (sd-pam)) whereas running it as myself shows me 100+ (including node and all the other apps I have going). I would expect that running as root I would see all processes for all users.
kubuntu htop konsole
kubuntu htop konsole
asked Jan 30 at 18:08
AlexAlex
83
asked Jan 30 at 18:08
AlexAlex
83
asked Jan 30 at 18:08
AlexAlex
83
asked Jan 30 at 18:08
AlexAlex
83
asked Jan 30 at 18:08
AlexAlex
83
83
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I have good news, and bad news.
Kill works for htop installed with sudo apt install htop.
Kill doesn't works for htop installed with sudo snap install htop.
I believe snap's sandbox is blocking the signal.
Also, the htop from snap list fewer processes than the htop from apt.
answered Feb 1 at 20:15
Marcos ZolnowskiMarcos Zolnowski
1162
1
Thank you, Marcos! I was not aware of snap sandboxing applications installed through it. Removing htop via snap and installing via apt solved my issue. I am now able to send signals and see all the processes I expected to see.
– Alex
Feb 4 at 16:14
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497751%2fhtop-signals-seem-not-to-be-sent-on-kubuntu-18-04%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have good news, and bad news.
Kill works for htop installed with sudo apt install htop.
Kill doesn't works for htop installed with sudo snap install htop.
I believe snap's sandbox is blocking the signal.
Also, the htop from snap list fewer processes than the htop from apt.
answered Feb 1 at 20:15
Marcos ZolnowskiMarcos Zolnowski
1162
1
Thank you, Marcos! I was not aware of snap sandboxing applications installed through it. Removing htop via snap and installing via apt solved my issue. I am now able to send signals and see all the processes I expected to see.
– Alex
Feb 4 at 16:14
add a comment |
I have good news, and bad news.
Kill works for htop installed with sudo apt install htop.
Kill doesn't works for htop installed with sudo snap install htop.
I believe snap's sandbox is blocking the signal.
Also, the htop from snap list fewer processes than the htop from apt.
answered Feb 1 at 20:15
Marcos ZolnowskiMarcos Zolnowski
1162
1
Thank you, Marcos! I was not aware of snap sandboxing applications installed through it. Removing htop via snap and installing via apt solved my issue. I am now able to send signals and see all the processes I expected to see.
– Alex
Feb 4 at 16:14
add a comment |
I have good news, and bad news.
Kill works for htop installed with sudo apt install htop.
Kill doesn't works for htop installed with sudo snap install htop.
I believe snap's sandbox is blocking the signal.
Also, the htop from snap list fewer processes than the htop from apt.
answered Feb 1 at 20:15
Marcos ZolnowskiMarcos Zolnowski
1162
I have good news, and bad news.
Kill works for htop installed with sudo apt install htop.
Kill doesn't works for htop installed with sudo snap install htop.
I believe snap's sandbox is blocking the signal.
Also, the htop from snap list fewer processes than the htop from apt.
answered Feb 1 at 20:15
Marcos ZolnowskiMarcos Zolnowski
1162
answered Feb 1 at 20:15
Marcos ZolnowskiMarcos Zolnowski
1162
answered Feb 1 at 20:15
Marcos ZolnowskiMarcos Zolnowski
1162
answered Feb 1 at 20:15
Marcos ZolnowskiMarcos Zolnowski
1162
1162
1
Thank you, Marcos! I was not aware of snap sandboxing applications installed through it. Removing htop via snap and installing via apt solved my issue. I am now able to send signals and see all the processes I expected to see.
– Alex
Feb 4 at 16:14
add a comment |
1
Thank you, Marcos! I was not aware of snap sandboxing applications installed through it. Removing htop via snap and installing via apt solved my issue. I am now able to send signals and see all the processes I expected to see.
– Alex
Feb 4 at 16:14
1
1
Thank you, Marcos! I was not aware of snap sandboxing applications installed through it. Removing htop via snap and installing via apt solved my issue. I am now able to send signals and see all the processes I expected to see.
– Alex
Feb 4 at 16:14
Thank you, Marcos! I was not aware of snap sandboxing applications installed through it. Removing htop via snap and installing via apt solved my issue. I am now able to send signals and see all the processes I expected to see.
– Alex
Feb 4 at 16:14
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497751%2fhtop-signals-seem-not-to-be-sent-on-kubuntu-18-04%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown