On 04/10/2009 09:42 AM, robert delius royar wrote:
I installed X11-2.3.3_rc5.dmg and copied X11.bin-1.5.3-apple5 to /A/U/X11.app/Contents/MacOS/X11.bin.
EEK. Yeah, sorry. Don't do that! I should've mentioned that the binary 1.5.3-apple5 is not compatible due to some changes I made to libXplugin (libXplugin is still compatible with every released server, and is source-compatible with that one, but I reverted some changes, so it doesn't support the "additions" that were in 2.3.3_rc4 any more).
10/04/2009 10 Apr 07:24:19 [0x0-0x12a12a].org.x.X11[75263] xmodmap: .Xmodmap:74: bad keysym target keysym '65506', no corresponding keycodes 10/04/2009 10 Apr 07:24:19 [0x0-0x12a12a].org.x.X11[75263] xmodmap: .Xmodmap:75: bad keysym target keysym '65505', no corresponding keycodes 10/04/2009 10 Apr 07:24:19 [0x0-0x12a12a].org.x.X11[75263] xmodmap: .Xmodmap:78: bad keysym target keysym 'F1', no corresponding keycodes [..] 10/04/2009 10 Apr 07:13:50 org.x.startx[74194] xmodmap: /Users/royar/.Xmodmap:90: bad keysym target keysym 'F13', no corresponding keycodes 10/04/2009 10 Apr 07:13:50 org.x.startx[74194] xmodmap: 15 errors encountered, aborting.
Odd... I wouldn't expect these errors...
These errors were not in the startup with X11-2.3.3_rc4.dmg and X11.bin-1.5.3-apple5.
I reinstalled X11-2.3.3_rc5.dmg to get the xorg-server 1.4.2-apple41 server. When I restarted X11, it ran fine, without the errors (and without the need to sleep before calling xmodmap to get my settings).
I am not sure that X11.bin-1.5.3-apple5 is compatible with X11-2.3.3_rc5.dmg; no one said that I should try the two together.
Sorry for not mentioning it... still, I'm confused why it's having this kind of breakage. I'll get a 1.5.3-apple6 build for you to try with all the spaces/window-levels updates in it.
Also, when I use the command sh -c "sleep 15; xmodmap /Users/royar/.Xmodmap" in ~/.xinitrc.d/50-xmodmap.sh, my initial windows lack decoration for the period taken by sleep. [This relates to an earlier problem I described regarding xmodmap and a race condition.]
Oh, yeah... that's to be expected. Throw a '&' after it, and you should be happy again.