some fraction of xterms started from the xmonad window manager get killed with SIGALRM
Sorry for being so lazy, but I am going to report a problem today, that
probably already started with Dragonfly 3.6. Same situation with 3.8 and
4.0 (maybe the probability to die is higher with 4.0).
When I use the xmonad key binding that starts a new xterm, there is a
chance, that the new process gets kill by an SIGALRM signal during
As far as I know, the xmonad/ghc runtime uses SIGALRM for the haskell
threads. Looks to me, like the child gets a signal from a timer, that
was started for/in the parent process.
Updated by profmakx over 8 years ago
- Assignee set to profmakx
Since I am affected by this too, I'll have a look some time soon