xmonad on solaris, input issue

older
Issue 365 in xmonad: shellPrompt...

Stephan Schulz

22 Jan 2010 22 Jan '10

10:29 p.m.

Hello all! I've succeeded in building xmonad 0.9.1 on a sparc box with Solaris 10 and GHC 6.10.4 (bootstrapped with the 6.8.3 binary sparc package). The only issue is, that it doesn't recognize it's metakey. So I can't open a terminal or quit it with Meta+Shift+Q. It has definitely something to do with the build process as remotely starting xmonad on a linux box does work flawless (remotely as in "ssh -X" to it). Has anyone suggestions were I should start to check for errors? best regards, Stephan

Show replies by date

Christian Walther

22 Jan 22 Jan

10:32 p.m.

Hello Stephan, 2010/1/22 Stephan Schulz :

...

Hello all!

I've succeeded in building xmonad 0.9.1 on a sparc box with Solaris 10 and GHC 6.10.4 (bootstrapped with the 6.8.3 binary sparc package). The only issue is, that it doesn't recognize it's metakey. So I can't open a terminal or quit it with Meta+Shift+Q. It has definitely something to do with the build process as remotely starting xmonad on a linux box does work flawless (remotely as in "ssh -X" to it). Has anyone suggestions were I should start to check for errors?

I'm using xmonad 0.9.1 on Solaris 10/Sparc, too, and don't have any issues with it. Is it possible that there is a mismatch between the modifier you configured in your xmonad.hs and the corresponding key? xmodmap should tell you. HTH Christian

Stephan Schulz

23 Jan 23 Jan

3:58 p.m.

On Fri, 22 Jan 2010, Christian Walther wrote:

...

Hello Stephan,

2010/1/22 Stephan Schulz :

...
Hello all!

I've succeeded in building xmonad 0.9.1 on a sparc box with Solaris 10 and GHC 6.10.4 (bootstrapped with the 6.8.3 binary sparc package). The only issue is, that it doesn't recognize it's metakey. So I can't open a terminal or quit it with Meta+Shift+Q. It has definitely something to do with the build process as remotely starting xmonad on a linux box does work flawless (remotely as in "ssh -X" to it). Has anyone suggestions were I should start to check for errors?

I'm using xmonad 0.9.1 on Solaris 10/Sparc, too, and don't have any issues with it. Is it possible that there is a mismatch between the modifier you configured in your xmonad.hs and the corresponding key? xmodmap should tell you.

I'm using the standard modifier as I have no ~/.xmonad directory (neither on the linux box nor the solaris box). The output of xmodmap -pm is this: xmodmap: up to 2 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lock Caps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1 Alt_L (0x40) mod2 Mode_switch (0x71) mod3 Num_Lock (0x4d) mod4 Meta_L (0x73), Meta_R (0x74) mod5 Seems ok to me... Any other ideas what I can try? kind regards, Stephan -- A computer is like an Old Testament god, with a lot of rules and no mercy. - Joseph Campbell

Ralph Hofmann

5:55 p.m.

Am Samstag, den 23.01.2010, 16:58 +0100 schrieb Stephan Schulz:

...

On Fri, 22 Jan 2010, Christian Walther wrote:

...
Hello Stephan,

2010/1/22 Stephan Schulz :

...
Hello all!

I've succeeded in building xmonad 0.9.1 on a sparc box with Solaris 10 and GHC 6.10.4 (bootstrapped with the 6.8.3 binary sparc package). The only issue is, that it doesn't recognize it's metakey. So I can't open a terminal or quit it with Meta+Shift+Q. It has definitely something to do with the build process as remotely starting xmonad on a linux box does work flawless (remotely as in "ssh -X" to it). Has anyone suggestions were I should start to check for errors?

I'm using xmonad 0.9.1 on Solaris 10/Sparc, too, and don't have any issues with it. Is it possible that there is a mismatch between the modifier you configured in your xmonad.hs and the corresponding key? xmodmap should tell you.

I'm using the standard modifier as I have no ~/.xmonad directory (neither on the linux box nor the solaris box). The output of xmodmap -pm is this:

xmodmap: up to 2 keys per modifier, (keycodes in parentheses):

shift Shift_L (0x32), Shift_R (0x3e) lock Caps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1 Alt_L (0x40) mod2 Mode_switch (0x71) mod3 Num_Lock (0x4d) mod4 Meta_L (0x73), Meta_R (0x74) mod5

Seems ok to me...

Any other ideas what I can try?

I had the same problem on linux at the beginning. The reason in my case was, that xmonad called a terminal, which has not been installed. You could try a very simple xmonad configuration: http://www.xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Doc-Configuring.html and edit the "terminal=..." line properly. Ralph

Stephan Schulz

6:47 p.m.

Am 23.01.2010 18:55, schrieb Ralph Hofmann:

...

Am Samstag, den 23.01.2010, 16:58 +0100 schrieb Stephan Schulz:

...
On Fri, 22 Jan 2010, Christian Walther wrote:

...
Hello Stephan,

2010/1/22 Stephan Schulz:

...
Hello all!

I've succeeded in building xmonad 0.9.1 on a sparc box with Solaris 10 and GHC 6.10.4 (bootstrapped with the 6.8.3 binary sparc package). The only issue is, that it doesn't recognize it's metakey. So I can't open a terminal or quit it with Meta+Shift+Q. It has definitely something to do with the build process as remotely starting xmonad on a linux box does work flawless (remotely as in "ssh -X" to it). Has anyone suggestions were I should start to check for errors?

I'm using xmonad 0.9.1 on Solaris 10/Sparc, too, and don't have any issues with it. Is it possible that there is a mismatch between the modifier you configured in your xmonad.hs and the corresponding key? xmodmap should tell you.

I'm using the standard modifier as I have no ~/.xmonad directory (neither on the linux box nor the solaris box). The output of xmodmap -pm is this:

xmodmap: up to 2 keys per modifier, (keycodes in parentheses):

shift Shift_L (0x32), Shift_R (0x3e) lock Caps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1 Alt_L (0x40) mod2 Mode_switch (0x71) mod3 Num_Lock (0x4d) mod4 Meta_L (0x73), Meta_R (0x74) mod5

Seems ok to me...

Any other ideas what I can try?

I had the same problem on linux at the beginning. The reason in my case was, that xmonad called a terminal, which has not been installed. You could try a very simple xmonad configuration:

http://www.xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Doc-Configuring.html

and edit the "terminal=..." line properly.

I tried it with the following: import XMonad main = xmonad defaultConfig { modMask = mod1Mask , terminal ="xterm" } xmonad --recompile yielded no errors or warnings, but it didn't help either. best regards, Stephan

Christian Walther

8:23 p.m.

Hi, On 23 January 2010 19:47, Stephan Schulz wrote: [...]

...

xmonad --recompile yielded no errors or warnings, but it didn't help either.

This is odd. Maybe there's something broken with the keyboard definition? You could run xev from inside a terminal to see what happens when you press any of the modifier keys. If you move the focus to the xev window you'll be able to monitor what's happening in the terminal. The output should look like: KeyPress event, serial 24, synthetic NO, window 0x1a00001, root 0x6e, subw 0x0, time 48918465, (342,370), root:(343,385), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 27, synthetic NO, window 0x1a00001, root 0x6e, subw 0x0, time 48918584, (342,370), root:(343,385), state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False Btw: What's your hardware configuration? Are you running on some old sparc box, or is it a USB keyboard? And what about the software, is it a stock Solaris 10 (including Xsun), or do you use any additional packages? OpenCSW for example comes with it's own Xorg server, which might lead to some configuration trouble (this is just a guess, though). Did you modify the xorg.conf of your X server? Christian

Stephan Schulz

25 Jan 25 Jan

11:50 a.m.

Hi! On Sat, 23 Jan 2010, Christian Walther wrote:

...

Hi,

On 23 January 2010 19:47, Stephan Schulz wrote: [...]

...
xmonad --recompile yielded no errors or warnings, but it didn't help either.

This is odd. Maybe there's something broken with the keyboard definition? You could run xev from inside a terminal to see what happens when you press any of the modifier keys. If you move the focus to the xev window you'll be able to monitor what's happening in the terminal. The output should look like:

KeyPress event, serial 24, synthetic NO, window 0x1a00001, root 0x6e, subw 0x0, time 48918465, (342,370), root:(343,385), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 27, synthetic NO, window 0x1a00001, root 0x6e, subw 0x0, time 48918584, (342,370), root:(343,385), state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False

This is my output of xev: KeyPress event, serial 25, synthetic NO, window 0x1e00001, root 0x3f, subw 0x1e00002, time 1699071935, (42,49), root:(44,51), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 characters: "" KeyRelease event, serial 25, synthetic NO, window 0x1e00001, root 0x3f, subw 0x1e00002, time 1699072015, (42,49), root:(44,51), state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 characters: "" Looks okay to me..

...

Btw: What's your hardware configuration? Are you running on some old sparc box, or is it a USB keyboard? And what about the software, is it a stock Solaris 10 (including Xsun), or do you use any additional packages? OpenCSW for example comes with it's own Xorg server, which might lead to some configuration trouble (this is just a guess, though). Did you modify the xorg.conf of your X server?

First, it's not my dedicated sparc box but my companies. Its a SPARC Enterprise M3000 Server and I'm connected to it through a SunRay with an USB keyboard. The Xserver is Xnewt. This means I cannot change any X-related configurations but I also think is isn't necessary as other windowmanagers work flawless. (I'm currently using a self-compiled fluxbox on it). Any other tips? kind regards, Stephan

Christian Walther

12:35 p.m.

Hello Stephan, 2010/1/25 Stephan Schulz :

...

On Sat, 23 Jan 2010, Christian Walther wrote:

...
On 23 January 2010 19:47, Stephan Schulz wrote: [...] First, it's not my dedicated sparc box but my companies. Its a SPARC Enterprise M3000 Server and I'm connected to it through a SunRay with an USB keyboard. The Xserver is Xnewt. This means I cannot change any X-related configurations but I also think is isn't necessary as other windowmanagers work flawless. (I'm currently using a self-compiled fluxbox on it).

Now that's a nice box. :-)

...

Any other tips?

Sorry, I'm completely at a loss here. I'm using a Sunray here, too (connected to a T5240), so my setup is similar to yours. However, there's difference in software: I used ghc 6.8.3 to compile xmonad. Maybe there's a problem with your Haskell X11 library. You could try to compile xmonad with ghc 6.8.3 directly. I could send you a minimal xmonad binary, compiled using the configuration you've given above. AFAIK ghc is static, which means that if my xmonad binary works there really should be a problem with your haskell environment. Regards, Christian

Christian Walther

2:05 p.m.

Hi there, 2010/1/25 Christian Walther : [...]

...

Sorry, I'm completely at a loss here. I was just reviewing my xmonad.hs when I came across the NumlockMask. This is used to tell XMonad where the NumLock key is, because it might influence ModMask. I recompiled xmonad using the default, and indeed: If ModMask isn't explicitely set, ModMask doesn't work *when NumLock is on*. Is it possible that your NumLock is on (which is it by default even on Sun keyboards)?

Regards Christian PS: Now I messed up installation. After moving back my old configuration xmonad keeps crashing on me with "Illegal instruction fault." Luckily I have a backup because I'm in a workshop and don't have the time to debug this issue.

Stephan Schulz

27 Jan 27 Jan

8:30 a.m.

New subject: Bug in X11 and/or xmonad? was: xmonad on solaris, input issue

Hi! I wanted to reply earlier but I still can't figure out under which circumstances it seems to work (I got it once to work with ghc-6.8.3 but the next compile failed again..). I will get back to you when I got a working setup, thanks so far :) best regards, Stephan Christian Walther wrote:

...

Hi there,

2010/1/25 Christian Walther : [...]

...
Sorry, I'm completely at a loss here. I was just reviewing my xmonad.hs when I came across the NumlockMask. This is used to tell XMonad where the NumLock key is, because it might influence ModMask. I recompiled xmonad using the default, and indeed: If ModMask isn't explicitely set, ModMask doesn't work *when NumLock is on*. Is it possible that your NumLock is on (which is it by default even on Sun keyboards)?

Regards Christian

PS: Now I messed up installation. After moving back my old configuration xmonad keeps crashing on me with "Illegal instruction fault." Luckily I have a backup because I'm in a workshop and don't have the time to debug this issue.

Stephan Schulz

28 Jan 28 Jan

6:32 a.m.

New subject: xmonad 0.9.1 does not work on solaris (but xmonad-0.9 does)

Hi all! As mentioned before I had trouble getting xmonad running on Solaris. I tried different versions of xmonad, X11, and ghc which yielded the following result: It seems to be unimportant if I use ghc-6.8.3 or ghc-6.10.4 aside from little issue with ghc-6.8.3 and X11 which needs manually copying of HsX11Config.h from the source to the appropiate place. But I can't get anything newer than X11-1.4.6.1 with xmonad-0.9 to work on Solaris. X11-1.5.0.0 with xmonad-0.9.1 has the input issue as mentioned here: http://www.haskell.org/pipermail/xmonad/2010-January/009613.html Has anyone an idea where things could went wrong? best regards, Stephan

Christian Walther

7:31 a.m.

New subject: xmonad 0.9.1 does not work on solaris (but xmonad-0.9 does)

Hi Stephan, I just wanted to check back with you to tell you that this really might be a version issue. Checking my config I found out that my Solaris install still uses xmonad-0.8.1. Getting confused by the status of my different xmonad installs, it appears... I'll try to compile ghc-6.10.4 an needed dependencies and check if I get the same results. Regards Christian Walther

Stephan Schulz

7:52 a.m.

New subject: xmonad 0.9.1 does not work on solaris (but xmonad-0.9 does)

Hi Christian! Just for reference: The only dependencies that I needed were a working ghc installation (6.8.3 binary package in my case) and X11-1.4.6.1 for xmonad-0.9 or X11-1.5.0.0 for xmonad-0.9.1. I couldn't bring xmonad-0.9 to compile with X11-1.4.6.1 because of some type mismatching during the compilation. Regards, Stephan

Stephan Schulz

8:02 a.m.

New subject: xmonad 0.9.1 does not work on solaris (but xmonad-0.9 does)

Stephan Schulz wrote:

...

Hi Christian!

Just for reference: The only dependencies that I needed were a working ghc installation (6.8.3 binary package in my case) and X11-1.4.6.1 for xmonad-0.9 or X11-1.5.0.0 for xmonad-0.9.1. I couldn't bring xmonad-0.9 to compile with X11-1.4.6.1 because of some type mismatching during the compilation.

I meant xmonad-0.9 did not compile with X11-1.5.0.0 of course. regards, Stephan

5639

Age (days ago)

5645

Last active (days ago)

List overview

Download

13 comments

3 participants

participants (3)

Christian Walther
Ralph Hofmann
Stephan Schulz