Arch Linux

hugleo

Member

Registered: 2013-04-29

Posts: 3

Control keys stop working after the last tigervnc upgrade

I've upgrade to the last tigervnc package (tigervnc-1.3.0-1-x86_64.pkg.tar.xz) and control keys like CTRL+C, CTRL+V stop working.
Is someone facing the same problem?

qfingers

Member

Registered: 2010-07-09

Posts: 6

Re: Control keys stop working after the last tigervnc upgrade

Yes, I have the same problem.  It seems to be the viewer as I can connect to the server with
a different vncviewer (tightvnc) and all keyboard control keys work.  I ran xev and pressing
CTRL-T and it shows:

KeyPress event, serial 34, synthetic NO, window 0x2c00001,
    root 0x13d, subw 0x0, time 272693323, (-452,-13), root:(362,803),
    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x2c00001,
    root 0x13d, subw 0x0, time 272693402, (-452,-13), root:(362,803),
    state 0x4, keycode 255 (keysym 0x1000014, (no name)), same_screen YES,
    XLookupString gives 1 bytes: (14) ""
    XmbLookupString gives 1 bytes: (14) ""
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x2c00001,
    root 0x13d, subw 0x0, time 272693530, (-452,-13), root:(362,803),
    state 0x4, keycode 255 (keysym 0x1000014, (no name)), same_screen YES,
    XLookupString gives 1 bytes: (14) ""
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x2c00001,
    root 0x13d, subw 0x0, time 272694875, (-452,-13), root:(362,803),
    state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

The

(keysym 0x1000014, (no name))

shows up on a normal xserver as

(keysym 0x74, t)

.

I'm not sure how to fix it though.

Gusar

Member

Registered: 2009-08-25

Posts: 3,605

Re: Control keys stop working after the last tigervnc upgrade

I was wondering how long it'll take until someone notices. If you look closely, you'll find other things not working/missing, most notably fullscreen support.

Here's the thing: Tigervnc 1.2 was compiled against an internal patched copy of fltk. 1.3 doesn't have such an internal copy anymore, so the system fltk is used. But the system fltk isn't patched to support what tigervnc needs. I'll open a bug, see if the Arch devs will add the necessary patches to fltk. In the mean time, use tigervnc-svn from AUR.

Edit: Bug report - https://bugs.archlinux.org/task/36186

Last edited by Gusar (2013-07-17 17:49:37)

sas

Member

Registered: 2009-11-24

Posts: 155

Re: Control keys stop working after the last tigervnc upgrade

Same problem here, after upgrading to tigervnc 1.3.0 on the client side.

Installing fltk-snapshot and tigervnc-svn fixed it.

---

my AUR packages ~~ my community contributions