i3 FAQ - Individual question feed

i3 FAQ - Individual question feedhttps://faq.i3wm.org/questions/Frequently asked questions and answers about the i3 window managerenCopyright i3, 2012Sun, 28 Dec 2014 18:49:28 +0000SIGINT is not delivered to processed launched from dmenuhttps://faq.i3wm.org/question/5275/sigint-is-not-delivered-to-processed-launched-from-dmenu/Hello! I've found strange behavior of processes launched from `dmenu`. Here are the steps to reproduce: 1. Launch `sleep 1000000` using `dmenu`. The key combination for `dmenu` is `Win-D` on my system. I believe `Alt-D` is the default one. 2. Execute `pgrep sleep` from shell to get a pid for process launched in step 1. 3. Execute `kill -2 $(pgrep sleep)`. 4. Nothing happened. The `sleep 1000000` process is still running. `kill -2` is working perfectly when I run `sleep 1000000` process from shell. What kind of magic is done by `dmenu` to block `SIGINT` from being delivered to processes? Is there any way to disable it? PS. I'm using `i3` metapackage of version `4.7.2-1` in Ubuntu 14.0.4. Further investigation shows that `dmenu` isn't guilty. I've created `sleep-999999` script with `sleep 999999 &` and put `exec sleep-999999` on a hotkey in `~/.i3/config`. This setup reproduces strange behavior described formerly.Sun, 28 Dec 2014 17:37:05 +0000https://faq.i3wm.org/question/5275/sigint-is-not-delivered-to-processed-launched-from-dmenu/Answer by sergej for Hello! I've found strange behavior of processes launched from <code>dmenu</code>. Here are the steps to reproduce: 1. Launch <code>sleep 1000000</code> using <code>dmenu</code>. The key combination for <code>dmenu</code> is <code>Win-D</code> on my system. I believe <code>Alt-D</code> is the default one. 2. Execute <code>pgrep sleep</code> from shell to get a pid for process launched in step 1. 3. Execute <code>kill -2 $(pgrep sleep)</code>. 4. Nothing happened. The <code>sleep 1000000</code> process is still running. <code>kill -2</code> is working perfectly when I run <code>sleep 1000000</code> process from shell. What kind of magic is done by <code>dmenu</code> to block <code>SIGINT</code> from being delivered to processes? Is there any way to disable it? PS. I'm using <code>i3</code> metapackage of version <code>4.7.2-1</code> in Ubuntu 14.0.4. Further investigation shows that <code>dmenu</code> isn't guilty. I've created <code>sleep-999999</code> script with <code>sleep 999999 &</code> and put <code>exec sleep-999999</code> on a hotkey in <code>~/.i3/config</code>. This setup reproduces strange behavior described formerly. https://faq.i3wm.org/question/5275/sigint-is-not-delivered-to-processed-launched-from-dmenu/?answer=5276#post-id-5276The answer is here: git.savannah.gnu.org/cgit/bash.git/tree/jobs.c#n1728 `bash` masks out `SIGINT` for background processes.Sun, 28 Dec 2014 18:49:28 +0000https://faq.i3wm.org/question/5275/sigint-is-not-delivered-to-processed-launched-from-dmenu/?answer=5276#post-id-5276