[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: raising windows by clicking: only works on titlebar



> It sounds strange because X does not know anything about Window title, frame, 
> border and the rest, it just draw all that stuff.  A window manager is 
> responsible for that.

I agree, it sounds odd, but it is definitely an X problem.  I
installed xserver-mach64 3.3.6-44.  Now the problem has gone away.
However it has been replaced by another problem: the backspace key now
behaves like the delete key.  I can fix this after logging in with:

xmodmap -e "keycode 0x16 = BackSpace"

Anybody know how to fix this permanently (without modifying users'
files)?


Getting back to the original problem of raising windows, here are a
couple more observations:

1. I wiped out version 4.1 of X with dpkg --purge, then reinstalled.
   Problem was still there.

2. I upgraded a second machine which is also acting as an X-terminal
   to debian testing and X version 4.1; this machine does NOT have the
   same problem.

   Machine with problem
   --------------------
   ATI Technologies Inc 3D Rage Pro 215GP (rev 92)
   serial mouse (Logitech MouseMan)
   old-style keyboard connector
  
   Machine without problem
   -----------------------
   VGA compatible controller: ATI Unknown device (rev 39).
      Vendor id=1002. Device id=4752.
   PS/2 mouse
   PS/2 keyboard


> Do you have a different keyboard on that terminal?

Funny you should ask.  This machine has an old-style keyboard
connector.  Furthermore, the keyboard is a little bit odd: it has a
key labelled "Macro" in the bottom left, and the backslash key is to
the right of the bottom right CTRL key.  Other than that it looks like
a standard pc101 keyboard.  The really funny thing is that this is the
ONLY keyboard which the mother board recognizes.  If I plug in another
old-style keyboard, on boot-up the BIOS complains about a missing
keyboard.

>  Or do you have kxkb 
> running to switch keyboard from ascii to something different?

Nope.


Thanks for your suggestions!



Reply to: