From: kf8nh@kf8nh.wariat.org (Brandon S. Allbery) Subject: X386 (SLS) + X8514: olvwm and xmodmap problems Date: 8 Jan 1993 00:44:31 GMT
I'm having a few problems with the above-mentioned combination (that's the
X386 from SLS 0.99 plus x8514new plus xview3L2 plus olvwm).
1) olvwm hangs the system after a few events. I can reliably reproduce it
by going into the Properties editor and popping up the menu of property
groups: on about the sixth time the pop-up menu only draws partially, and
the system hangs. Other olvwm-related actions also cause it; however,
actions on a client such as xterm do not. olwm from xview3L2 works fine,
although it has the zombie process bug described by other posters. twm also
works (but it's UGLY! :-) I'm not running out of memory; I checked.
BTW, this is the olvwm built from the .a file (olvwmbin_gcc2.2.2.T.Z); the
olvwm binary from olvwmbin dumps core when invoked.
2) I tried to use xmodmap to swap the caps-lock and control keys, because
I'm an old-fogie keyboarder who expects the control key *above* the shift
key. :-) I was successfully able to patch the kernel to do this in the
translated (non-scancode) mode, but when I use xmodmap to do the same under
X the only thing that swaps is which key toggles the keyboard LED; the
result is slightly bizarre. (Watch the caps-lock LED blink while entering
^X^C in emacs. :-) I did this using the standard .xinitrc functionality,
so it's not a question of clients not seeing a MappingNotify event or
something of that nature.
I haven't checked these with the stock X386 server, so both may well be
X8514 bugs (it *is* an alpha release, but it's also the best server I can
find for an ATI Graphics Vantage...).
Anyone else seen these?
++Brandon