Got it. That fixed it! Thank you very much!

I had to comment the lines 
main = do
  dzen2 <- spawnPipe ( "killall rundzen; rundzen --" ++ (join $ map (wrap "-" "-") myWorkspaces))
  Log.dzen $ \ defaultConfig -> xmonad $
  defaultConfig -> xmonad $

and replace it with 
main = xmonad defaults

and make
default = defaultConfig {
......
}
And of course left indent defaultConfig

I'm very new to haskell & xmonad. I inferred it from the default template file. I appreciate your help a lot!

I will definitely be using xmonad & hope to make some extensions! Thanks again!

-Sean

On Tue, Feb 16, 2010 at 8:32 PM, Adam Vogt <vogt.adam@gmail.com> wrote:
Hi Sean,

This line which you didn't comment will cause xmonad to try to spawn a
dzen and write to that pipe (in addition to your usage of spawnPipe):

283.  Log.dzen $ \ defaultConfig -> xmonad $

Your problem might go away if you get rid of that too, or work out why
dzen isn't consuming it's stdin (because of missing fonts or whatever
that prevent it from running).

--
Adam

* On Tuesday, February 16 2010, Sean Neilan wrote:

>Hey All,
>
>My xmonad installation on Ubuntu 9.10 i386 stops responding after a while.
>It's just like the faq entry here:
>http://www.haskell.org/haskellwiki/Xmonad/Frequently_asked_questions#XMonad_stops_but_the_current_window_still_responds_to_keys
>
>I've commented out references to logHook in my xmonad config file
>http://pastebin.com/f8622e8a
>
>Still, the same error is happening.
>
>Does anyone know if I'm doing something wrong?
>
>Thank you for your time.
>
>Sean Neilan

>_______________________________________________
>xmonad mailing list
>xmonad@haskell.org
>http://www.haskell.org/mailman/listinfo/xmonad