Project

General

Profile

Bug #2746

some fraction of xterms started from the xmonad window manager get killed with SIGALRM

Added by isenmann almost 3 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
12/18/2014
Due date:
% Done:

0%


Description

Hi!

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
startup.

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.

History

#1 Updated by profmakx almost 3 years ago

  • Assignee set to profmakx

Since I am affected by this too, I'll have a look some time soon

Also available in: Atom PDF