Strange spawnPipe error

Hi all, I'm getting my laptop re-set up (after installing a new hard drive after the old one died). I've got an up-to-date arch linux installed, and darcs xmonad, using the same config that I had before. However, now when xmonad starts up it fails to start dzen via spawnPipe. Instead, I get this error: createSession: permission denied (Operation not permitted) Due to various debugging activites on my part it is clear that this is being generated by the call to spawnPipe. Anyone have any ideas? I could file this on the bug tracker but it is not at all clear to me that it's an xmonad bug, I was just hoping someone might have an idea what is wrong. I don't really understand what spawnPipe is doing under the hood and what might go wrong. -Brent

Brent Yorgey
when xmonad starts up it fails to start dzen via spawnPipe. Instead, I get this error:
createSession: permission denied (Operation not permitted)
Due to various debugging activites on my part it is clear that this is being generated by the call to spawnPipe.
spawnPipe calls createSession, which is the setsid system call. From man setsid: The only error which can happen is EPERM. It is returned when the process group ID of any process equals the PID of the calling process. Thus, in particular, setsid() fails if the calling process is already a process group leader. Since spawnPipe calls this right after forking, I don't understand how this could happen. Maybe strace -f could provide some insight. -- Regards, Feri.
participants (2)
-
Brent Yorgey
-
Ferenc Wagner