Keypress problems with Chromium

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Keypress problems with Chromium

Linus Lüssing
Hi!

First of all, I have to say that I'm really impressed with how
well tightvnc works over 802.11n wifi. I have to admit that I
didn't actually have much hope that VNC would be usable over Wifi
at all.

As it works so well I thought, I'd ask here to iron out the last
issue I'm currently having between two machines I'm trying to
use VNC:


# Chromium and special characters

I'm using a slightly customized Neo keyboard layout (1), loaded
via xmodmap. This works fine for both machines locally. However
over tightvnc chromium on the vnc-server does not recognize
certain characters anymore: For instance umlauts (äöü) or
numbers. Other applications like Firefox or LXTerminal work fine
over VNC. Also the xev output looks fine to me:

----------
KeyPress event, serial 41, synthetic NO, window 0x1800001,
    root 0x25, subw 0x0, time 2499180456, (169,-10), root:(170,8),
    state 0x0, keycode 95 (keysym 0xe4, adiaeresis), same_screen YES,
    XLookupString gives 2 bytes: (c3 a4) "ä"
    XmbLookupString gives 2 bytes: (c3 a4) "ä"
    XFilterEvent returns: False

KeyRelease event, serial 41, synthetic NO, window 0x1800001,
    root 0x25, subw 0x0, time 2499180508, (169,-10), root:(170,8),
    state 0x0, keycode 95 (keysym 0xe4, adiaeresis), same_screen YES,
    XLookupString gives 2 bytes: (c3 a4) "ä"
    XFilterEvent returns: False

KeyPress event, serial 42, synthetic NO, window 0x1800001,
    root 0x25, subw 0x0, time 2499107550, (167,-11), root:(294,8),
    state 0x0, keycode 90 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 42, synthetic NO, window 0x1800001,
    root 0x25, subw 0x0, time 2499108126, (167,-11), root:(294,8),
    state 0x0, keycode 96 (keysym 0xffb1, KP_1), same_screen YES,
    XLookupString gives 1 bytes: (31) "1"
    XmbLookupString gives 1 bytes: (31) "1"
    XFilterEvent returns: False

KeyRelease event, serial 42, synthetic NO, window 0x1800001,
    root 0x25, subw 0x0, time 2499108637, (167,-11), root:(294,8),
    state 0x0, keycode 96 (keysym 0xffb1, KP_1), same_screen YES,
    XLookupString gives 1 bytes: (31) "1"
    XFilterEvent returns: False

KeyRelease event, serial 42, synthetic NO, window 0x1800001,
    root 0x25, subw 0x0, time 2499109102, (167,-11), root:(294,8),
    state 0x0, keycode 90 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
----------

On the vnc-client side I'm loading the xmodmap (2) in the following
way:

$ setxkbmap lv && xmodmap neon_de.xmodmap && xset -r 51

Has anyone had an issue like that before?

Cheers, Linus

(1): http://neo-layout.org/index_en.html
(2): http://metameute.de/~tux/bugreport/chromium/neon_de.xmodmap

------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

Re: Keypress problems with Chromium

Fernando Rodriguez
On Thursday, September 03, 2015 11:14:18 PM Linus Lüssing wrote:

> Hi!
>
> First of all, I have to say that I'm really impressed with how
> well tightvnc works over 802.11n wifi. I have to admit that I
> didn't actually have much hope that VNC would be usable over Wifi
> at all.
>
> As it works so well I thought, I'd ask here to iron out the last
> issue I'm currently having between two machines I'm trying to
> use VNC:
>
>
> # Chromium and special characters
>
> I'm using a slightly customized Neo keyboard layout (1), loaded
> via xmodmap. This works fine for both machines locally. However
> over tightvnc chromium on the vnc-server does not recognize
> certain characters anymore: For instance umlauts (äöü) or
> numbers. Other applications like Firefox or LXTerminal work fine
> over VNC. Also the xev output looks fine to me:
>
> ----------
> KeyPress event, serial 41, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499180456, (169,-10), root:(170,8),
>     state 0x0, keycode 95 (keysym 0xe4, adiaeresis), same_screen YES,
>     XLookupString gives 2 bytes: (c3 a4) "ä"
>     XmbLookupString gives 2 bytes: (c3 a4) "ä"
>     XFilterEvent returns: False
>
> KeyRelease event, serial 41, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499180508, (169,-10), root:(170,8),
>     state 0x0, keycode 95 (keysym 0xe4, adiaeresis), same_screen YES,
>     XLookupString gives 2 bytes: (c3 a4) "ä"
>     XFilterEvent returns: False
>
> KeyPress event, serial 42, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499107550, (167,-11), root:(294,8),
>     state 0x0, keycode 90 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,

>     XLookupString gives 0 bytes:
>     XmbLookupString gives 0 bytes:
>     XFilterEvent returns: False
>
> KeyPress event, serial 42, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499108126, (167,-11), root:(294,8),
>     state 0x0, keycode 96 (keysym 0xffb1, KP_1), same_screen YES,
>     XLookupString gives 1 bytes: (31) "1"
>     XmbLookupString gives 1 bytes: (31) "1"
>     XFilterEvent returns: False
>
> KeyRelease event, serial 42, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499108637, (167,-11), root:(294,8),
>     state 0x0, keycode 96 (keysym 0xffb1, KP_1), same_screen YES,
>     XLookupString gives 1 bytes: (31) "1"
>     XFilterEvent returns: False
>
> KeyRelease event, serial 42, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499109102, (167,-11), root:(294,8),
>     state 0x0, keycode 90 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,

>     XLookupString gives 0 bytes:
>     XFilterEvent returns: False
> ----------
>
> On the vnc-client side I'm loading the xmodmap (2) in the following
> way:
>
> $ setxkbmap lv && xmodmap neon_de.xmodmap && xset -r 51
>
> Has anyone had an issue like that before?
>
> Cheers, Linus
>
> (1): http://neo-layout.org/index_en.html
> (2): http://metameute.de/~tux/bugreport/chromium/neon_de.xmodmap
>
>
------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> ___________________________________________________________
> TightVNC mailing list, [hidden email]
> To change your subscription or to UNSUBSCRIBE, please visit
> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

I subscribed to this list about 6 months ago and this is the first message
since. So good luck.

Maybe you should try some other vnc fork if you need support.

--
Fernando Rodriguez

------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

Re: Keypress problems with Chromium

Linus Lüssing
In reply to this post by Linus Lüssing
On Thu, Sep 03, 2015 at 11:14:18PM +0200, Linus Lüssing wrote:

> Hi!
>
> First of all, I have to say that I'm really impressed with how
> well tightvnc works over 802.11n wifi. I have to admit that I
> didn't actually have much hope that VNC would be usable over Wifi
> at all.
>
> As it works so well I thought, I'd ask here to iron out the last
> issue I'm currently having between two machines I'm trying to
> use VNC:
>
>
> # Chromium and special characters
>
> I'm using a slightly customized Neo keyboard layout (1), loaded
> via xmodmap. This works fine for both machines locally. However
> over tightvnc chromium on the vnc-server does not recognize
> certain characters anymore: For instance umlauts (äöü) or
> numbers. Other applications like Firefox or LXTerminal work fine
> over VNC. Also the xev output looks fine to me:
>
> ----------
> KeyPress event, serial 41, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499180456, (169,-10), root:(170,8),
>     state 0x0, keycode 95 (keysym 0xe4, adiaeresis), same_screen YES,
>     XLookupString gives 2 bytes: (c3 a4) "ä"
>     XmbLookupString gives 2 bytes: (c3 a4) "ä"
>     XFilterEvent returns: False
>
> KeyRelease event, serial 41, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499180508, (169,-10), root:(170,8),
>     state 0x0, keycode 95 (keysym 0xe4, adiaeresis), same_screen YES,
>     XLookupString gives 2 bytes: (c3 a4) "ä"
>     XFilterEvent returns: False
>
> KeyPress event, serial 42, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499107550, (167,-11), root:(294,8),
>     state 0x0, keycode 90 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
>     XLookupString gives 0 bytes:
>     XmbLookupString gives 0 bytes:
>     XFilterEvent returns: False
>
> KeyPress event, serial 42, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499108126, (167,-11), root:(294,8),
>     state 0x0, keycode 96 (keysym 0xffb1, KP_1), same_screen YES,
>     XLookupString gives 1 bytes: (31) "1"
>     XmbLookupString gives 1 bytes: (31) "1"
>     XFilterEvent returns: False
>
> KeyRelease event, serial 42, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499108637, (167,-11), root:(294,8),
>     state 0x0, keycode 96 (keysym 0xffb1, KP_1), same_screen YES,
>     XLookupString gives 1 bytes: (31) "1"
>     XFilterEvent returns: False
>
> KeyRelease event, serial 42, synthetic NO, window 0x1800001,
>     root 0x25, subw 0x0, time 2499109102, (167,-11), root:(294,8),
>     state 0x0, keycode 90 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
>     XLookupString gives 0 bytes:
>     XFilterEvent returns: False
> ----------
>
> On the vnc-client side I'm loading the xmodmap (2) in the following
> way:
>
> $ setxkbmap lv && xmodmap neon_de.xmodmap && xset -r 51
>
> Has anyone had an issue like that before?
>
> Cheers, Linus
>
> (1): http://neo-layout.org/index_en.html
> (2): http://metameute.de/~tux/bugreport/chromium/neon_de.xmodmap
>
> ------------------------------------------------------------------------------

Just for the record: I think I have found the root of this problem and a
workaround:

It seems that with tightvnc the xmodmap of the remote desktop is very sparse
in the beginning. Further keycodes are added on-demand after
pressed for the first time. A selection from "xmodmap -pk" on the remote
machine running tightvnc:

-----
[...]
     87         0xffc8 (F11)    
     88         0xffc9 (F12)    
     89         0xffd5 (F24)    
     90         0xfe03 (ISO_Level3_Shift)      
     91         0xff7e (Mode_switch)    
     92         0xffb5 (KP_5)  
     93         0xffb8 (KP_8)  
     94         0x00e4 (adiaeresis)     0x00c4 (Adiaeresis)    
     95         0xffb9 (KP_9)  
     96         0xffb3 (KP_3)  
     97         0xffb0 (KP_0)  
     98         0xffb1 (KP_1)  
     99         0xffb6 (KP_6)  
    100         0xffb7 (KP_7)  
    101         0xffeb (Super_L)        
    102         0xffb4 (KP_4)  
    103         0xffb2 (KP_2)
[...]
-----


Chromium however seems to read the keyboard layout just once on
startup. So after pressing KP_1...KP_9 once and then (re)starting
chromium makes things work.

I'm going to add the keycodes manually, earlier on vnc startup
through "xmodmap -e 'keycode XX = FooKey'" lines in
~/.vnc/xstartup.

Cheers, Linus

------------------------------------------------------------------------------
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list