Issue 137: Incorrectly specified BorderColor brings down xmonad on restart http://code.google.com/p/xmonad/issues/detail?id=137 Comment #4 by semdornus: Thanks for the fix. There is indeed no crash anymore. Two small caveats though; there is no xmessage specifying the problem, which could confuse the user ("Why doesn't my new configuration work?") and make any problem hunting in the configuration itself troublesome. Secondly I use a spawnPipe (dzen2) with DynamicLog for the workspaces, etc. This doesn't work anymore in combination with this problem. If I restart with an incorrect bordercolor dzen2 doesn't come up anymore. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings