FS#42796 - [tigervnc][fltk] fltk 1.3.3-1 breaks control keys within vnc-sessions.
Attached to Project:
Community Packages
Opened by John (graysky) - Saturday, 15 November 2014, 11:40 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 24 November 2014, 17:26 GMT
Opened by John (graysky) - Saturday, 15 November 2014, 11:40 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 24 November 2014, 17:26 GMT
|
Details
The 1.3.3-1 release breaks any combination of ctrl + another
key when connected to a tigervnc server. Downgrading to
1.3.2-5 fixes the problem. Not sure if this is an upstream
regression or something patch we are not applying.
Additional info: * package version(s) fltk 1.3.3-1 Steps to reproduce: 1) Install tigervnc and a DE ... on my box it runs lxde. 2) My ~/.vnc/xstartup contains online 1 line: exec startlxde and is started with this command: vncserver -geometry 1792x1008 -alwaysshared 3) Connect to the vncserver and try to ctrl+f or ctrl+t in chromium for example. Nothing happens. Now downgrade fltk and restart the vncserver. The ctrl+x combinations work as expected. |
This task depends upon
Closed by Sergej Pupykin (sergej)
Monday, 24 November 2014, 17:26 GMT
Reason for closing: Fixed
Additional comments about closing: thanks
Monday, 24 November 2014, 17:26 GMT
Reason for closing: Fixed
Additional comments about closing: thanks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181345
https://bugs.archlinux.org/task/36186
FS#36186are part of the 1.3.3 release. It seems not all of them are, so dropping the tigervnc patch entirely was not the right way to go, a new tigervnc patch will need to be created. Or Arch packages a SVN snapshot of fltk, that would work too.FS#42795is about segfaults not this issue.[1] https://github.com/TigerVNC/tigervnc/issues/72#issuecomment-63786427
PKGBUILD: https://gist.github.com/graysky2/b834c6d3d8fe7db70e3b
@Snowman: Can we ship that beta of tigervnc with arch (put it in testing for a few days, and then release it as 'stable', if everything works out)?
EDIT: Good news seems to be, that we wouldn't need to patch fltk anymore (Gusar already posted the related link):
"The keyboard handling is a messy area. We rely on a lot of patches for FLTK 1.3.2 to get things right. All of them are included in FLTK 1.3.3, but unfortunately some things changed a bit. Meaning that TigerVNC 1.3.1 and FLTK 1.3.3 won't get a fully functional keyboard. TigerVNC 1.4.0 should work fine though, so please test the beta we just released." - https://github.com/TigerVNC/tigervnc/issues/72#issuecomment-63786427
FS#42795(the crasher bug).@sergej: Some notes about the PKGBUILD: I added mesa-dri as a dependency - Xvnc uses swrast_dri.so, which nowadays is part of the mesa-dri package. Then, xorg116 and xserver116 patches can be dropped - the former isn't required anymore, the latter is part of the upstream source, so we don't need to ship it ourselves. The PKGBUILD is modified accordingly.
Edit: Hmm, now that I think about it, both mesa-dri and libgl could be optdepends - if they're not around, Xvnc simply won't have opengl available, but it'll still work. I'm attaching a PKGBUILD that does this.