numpad no longer works in VNC since upgrade to 5.x

[risto3]

Another quite cumbersome regression since upgrading a post to 5.x is that the numeric keypad no longer works in VNC.
I've tried TigerVNC and the seemingly more performant RealVNC 5.0.5 flavour.

Is this related to the fact the 'udev' is now used?  Is there any way to go back to the reliable legacy mechanisms?
That is, I had to move the related section from xorg.conf to /etc/X11/xorg.conf.d/10-keyboard-terminate.conf with the following to get the keypad back locally:
Section "InputClass"
    Identifier         "Keyboard Layout"
    MatchIsKeyboard    "yes"
    MatchDevicePath    "/dev/input/event*"
    Option             "XkbLayout"     "fr"
    Option             "XkbVariant"    "oss"
    Option       "XkbOptions"    "numpad:microsoft"
EndSection

This is preventing a general deployment of the Tiny V5 upgrade as all the users are heavy keypad users.

Thanks in advance

[curaga]

Earlier versions used the "keyboard" driver instead of "evdev". If you used a xorg.conf earlier, using the same conf should work. If you didn't, see if you can generate one on TC 4.x, according to the Xorg info file.

[Juanito]

if  you load the xf86-input-{keybord,mouse} extensions instead of the xf86-input-evdev extension, then things should work as before.

[risto3]

? After upgrading, xorg.conf no longer worked and I needed to create the file indicated under xorg.conf.d.

How can I go back (read: force) to this xorg configuration?

[risto3]

if  you load the xf86-input-{keybord,mouse} extensions instead of the xf86-input-evdev extension, then things should work as before.

I can only see xf86-input-{evdev,synaptics,vmmouse,wacom}...
Perhaps there are some missing packages, which might explain why things didn't work...

Advise?

[Juanito]

I was getting mixed up between the x86 and x86_64 repos - wait one...

[Juanito]

posted - you may need:

Code: [Select]

$ cat /etc/X11/xorg.conf
Section "ServerFlags"
Option "AutoAddDevices" "false"
EndSection


[risto3]

posted - you may need:

Code: [Select]

$ cat /etc/X11/xorg.conf
Section "ServerFlags"
Option "AutoAddDevices" "false"
EndSection


Well, as can be seen by the attached Xorg.log, the keyboard and the mouse driver are now correctly used.
Unfortunately, no change in the keypad support in a VNCviewer session.  I also include a diff with the previously used
xorg.conf.

I should mention that the keypad works in the login screen to my vncserver (here, tigervnc on solaris), but once logged in and in a gnome session gnome-terminal, keypad no longer works (regardless of the numlock status).

Is this perhaps a regression in the X kbd events processing?

[Juanito]

One other option might be to use the evdev driver and adjust /usr/local/share/X11/xorg.conf.d/10-evdev.conf

[risto3]

One other option might be to use the evdev driver and adjust /usr/local/share/X11/xorg.conf.d/10-evdev.conf

Well, I created /etc/X11/xorg.conf.d/10-keyboard-terminate.conf after reading the appropriate section here: http://wiki.archlinux.fr/Xorg   so I believe that is where I realised that local works fine but remote (using X via VNCviewer) doesn't.

I'll give Xnest (actually Xephyr) a shot to see if it is broke as well...  there must be some tangible explanation.

Does anybody use VNCviewer ?

As I indicated, I don't believe it is the binaries of the VNC viewer causing the problem as the REALvnc viewer is the same physical binary used in 4.x and we've been using the server since prior to Tiny 4.0 being released.

Thanks so far, in any event!

[risto3]

One other option might be to use the evdev driver and adjust /usr/local/share/X11/xorg.conf.d/10-evdev.conf

Well, I created /etc/X11/xorg.conf.d/10-keyboard-terminate.conf after reading the appropriate section here: http://wiki.archlinux.fr/Xorg   so I believe that is where I realised that local works fine but remote (using X via VNCviewer) doesn't.

I'll give Xnest (actually Xephyr) a shot to see if it is broke as well...  there must be some tangible explanation.

Does anybody use VNCviewer ?

As I indicated, I don't believe it is the binaries of the VNC viewer causing the problem as the REALvnc viewer is the same physical binary used in 4.x and we've been using the server since prior to Tiny 4.0 being released.

Thanks so far, in any event!

More problems than what it is worth.  Going back to where I started,  the following is a KP1 as viewed with `xev`:

Code: [Select]

KeyPress event, serial 113, synthetic NO, window 0x2400001,
    root 0xfd, subw 0x0, time 1542122024, (64,97), root:(65,165),
    state 0x0, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 113, synthetic NO, window 0x2400001,
    root 0xfd, subw 0x0, time 1542122024, (64,97), root:(65,165),
    state 0x1, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 116, synthetic NO, window 0x2400001,
    root 0xfd, subw 0x0, time 1542122177, (64,97), root:(65,165),
    state 0x0, keycode 87 (keysym 0xff9c, KP_End), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Is there perhaps a different way to map these keys?  If not, how can I roll back to the previous version of xorg?