Issue #2746 has been reported by isenmann. ---------------------------------------- Bug #2746: some fraction of xterms started from the xmonad window manager get killed with SIGALRM http://bugs.dragonflybsd.org/issues/2746
* Author: isenmann * Status: New * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- 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. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
