SetWMName does not seem to be sucessfull

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install current xmonad with cabal in ubuntu
2. Add SetWMName extension to xmonad.hs to fix Java Bug
3. Configure the use of Gnome Integration
4. Start Java Application

What is the expected output? What do you see instead?

I expected to see a functional matlab, but I'm only seeing gray boxes.

What version of the product are you using? On what operating system?

$ xmonad --version
xmonad 0.8

$ cabal --v
cabal-install version 0.6.0
using version 1.6.0.1 of the Cabal library 

$ ~/.cabal/packages/hackage.haskell.org/ ls
00-index.tar     HTTP        X11      binary             cabal-install 
happy             hpc       mtl       pandoc      regex-base    soegtk    
  uulib   xmonad          zip-archive
00-index.tar.gz  QuickCheck  X11-xft  build-reports.log  cgi           
haskell-src       hscolour  network   parsec      regex-compat  time      
  xhtml   xmonad-contrib  zlib
Cabal            Stream      arrows   bytestring         ghc-core      
haskell-src-exts  hslogger  old-time  pcre-light  regex-posix   utf8-string
 xmobar  xmonad-utils

Please provide any additional information below.

I attached my xmonad.hs, please tell me if there is any further information
I need to attach.

If this error is due to a module from XMonadContrib, please tag this issue
with 'Component-Contrib' below.

Component-Contrib

Original issue reported on code.google.com by brian.amberg@gmail.com on 29 Oct 2008 at 8:32

Attachments:

• xmonad.hs

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I found out that this seems to be a problem with gnomeConfig, when I replace
gnomeConfig with defaultConfig, the problem goes away. I've attached the two
xmonad.hs files, the working and the broken version.

Original comment by brian.amberg@gmail.com on 29 Oct 2008 at 8:43

Attachments:

• xmonad.hs
• xmonad.hs.gnome

[GoogleCodeExporter]

Ok, I've drilled down more on the problem. It seems that the logHook hook is
responsible. When I overwrite the logHook, my Matlab is working, when I use the 
gnome
log hook, it does not work.

-- Configuration
main = xmonad $ gnomeConfig {
                startupHook = startupHook'
              , logHook    = dynamicLog
              , terminal = terminal'
              , borderWidth = borderWidth'
              , normalBorderColor = normalBorderColor'
              , focusedBorderColor = focusedBorderColor'
              }
              `additionalKeysP`
              [
                -- moving workspaces
                  ("M-<Left>",    prevWS )
                , ("M-<Right>",   nextWS )
                , ("M-S-<Left>",  shiftToPrev )
                , ("M-S-<Right>", shiftToNext )
              ]

Original comment by brian.amberg@gmail.com on 29 Oct 2008 at 9:01

Attachments:

• xmonad.hs

[GoogleCodeExporter]

Good debugging work!  Starting from here I drilled down through the code and 
found
the culprit-- the gnome config uses the generic desktop config, which uses the
logHook from EwmhDesktops -- and guess what, the EwmhDesktops logHook sets the 
WM
name to "xmonad", overriding whatever you set it to!  duh.

Does anyone know of any good reason why the line 'setWMName "xmonad"' should not
simply be removed from the EwmhDesktops logHook?  And if there is a good reason 
it is
there, can anyone think of a better solution?  Of course in theory the WM_NAME 
should
not matter, but in practice it obviously does.

Original comment by byor...@gmail.com on 29 Oct 2008 at 11:51

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by byor...@gmail.com on 29 Oct 2008 at 11:52

• Added labels: Component-Contrib, Type-Defect, Usability

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hello Byorgey,

thank you for finding the problem, I should have looked there myself, but I'm 
not
proficient with Haskell.

I removed the line, and now my system is running nicely again.

Brian

Original comment by brian.amberg@gmail.com on 29 Oct 2008 at 6:10

[GoogleCodeExporter]

http://junmin.walsai.com/2009/01/get-java-working-with-xmonad.html

i had to modify that line(not removing)

Original comment by junmi...@gmail.com on 8 Jan 2009 at 11:00

[GoogleCodeExporter]

I had the same issue with the EwmhDesktop loghook and from the irc channel came 
the
suggestion to use 

ewmhDesktopsLogHook >> setWMName "LG3D" 

as part of my logHook which works fine. Maybe you could do something similar 
instead
of changing the logHook...

Original comment by que...@gmail.com on 31 Aug 2009 at 7:04

[GoogleCodeExporter]

This patch (included in 0.9) pushes the setWMName call in
ewmhDesktops to the startup hook, so setWMName "LG3D" should
do the right thing at any order in the logHook:

    Sun Oct 11 01:35:38 EDT 2009  Justin Bogner <mail@justinbogner.com>
      * Move EWMH support initialization to a startupHook

      Set EWMH support atoms and the window manager name in a startup hook,
      rather than in the log hook: the log hook occurs far too frequently
      for it to make sense to set constants with it.

Original comment by vogt.a...@gmail.com on 28 Oct 2009 at 1:58

• Changed state: Fixed