[xmonad] Issue 543 in xmonad: StackSet: non-positive argument to StackSet.new with mroe monitors than workspaces

codesite-noreply at google.com codesite-noreply at google.com
Thu Apr 25 16:49:09 CEST 2013

Status: Accepted
Owner: nome... at gmail.com

New issue 543 by nome... at gmail.com: StackSet: non-positive argument to  
StackSet.new with mroe monitors than workspaces

At http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706149 this bug was  
reported (Version 0.10):

My xmonad configuration only sets up a single workspace: I create the
rest dynamically as I need them. I use a laptop, and sometimes have an
external monitor. If I have a single workspace when I attach the second
monitor, xmonad fails to start.

A minimal .xmonad.hs that exhibits the problem:

--- 8< ---
import XMonad
import XMonad.Config.Gnome

main :: IO ()
main = do xmonad $ gnomeConfig { workspaces = ["GTD"] }
--- 8< ---

Procedure for reproducing:

* Use the above .xmonad.hs.
* Log into a GNOME+Xmonad session in wheezy.
* If there are two monitors, xmonad fails to start.
* If there is a single monitor, this works. If I attach a second monitor,
   xmonad does not crash. However, re-starting it (e.g., due to a
   change to .xmonad.hs) doesn't work.

The error message xmonad gives when starting up:

xmonad-x86_64-linux: xmonad: StackSet: non-positive argument to StackSet.new

I am probably unsual in liking to create my workspaces dynamically on
demand. However, it would be good if xmonad would at least start even
if it can't have something on every monitor.

You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:

More information about the xmonad mailing list