Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36424 - [x11vnc] ctrl key does not work

Attached to Project: Arch Linux
Opened by John (graysky) - Monday, 05 August 2013, 20:53 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 17 August 2013, 23:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: The ctrl key stopped working in x11vnc. I do not know if this is related to the following or not: https://bugs.archlinux.org/task/36186


Additional info:
* package version(s) 0.9.13-4
* logfile is attached to bugreport

Steps to reproduce:
I am using lxdm as my greeter. It is set to autologin my user. This should not matter, but I am stating it for completeness. Once logged in, open an xterm and run the following line which will start x11vnc as I do.

% x11vnc -nap -wait 50 -noxdamage -display :0 -forever -o /dev/shm/x11vnc.log -bg
   x11vnc.log (10.6 KiB)
This task depends upon

Closed by  Gaetan Bisson (vesath)
Saturday, 17 August 2013, 23:22 GMT
Reason for closing:  Not a bug
Comment by John (graysky) - Monday, 05 August 2013, 20:59 GMT
I should say that a comment in flyspray #36186 recommends using the fltk-snapshot package from the AUR. I tried this and following a reboot, there is no change; still no ctrl key.
Comment by Gaetan Bisson (vesath) - Saturday, 17 August 2013, 10:41 GMT
Is there any indication that we can do something about this packaging-wise? This seems like an upstream issue to me. You should really report it upstream.
Comment by John (graysky) - Saturday, 17 August 2013, 11:02 GMT
@vesath - I would but since this issue is affecting both tigervnc and x11vnc, I'm not too such which package is responsible for it. For example, flspray #36186 is against fltk describing similar symptoms.
Comment by Gaetan Bisson (vesath) - Saturday, 17 August 2013, 11:13 GMT
Well you did not mention tigervnc in your report.
Anyway, you can try with a different VNC viewer; we have a few in our repos: https://www.archlinux.org/packages/?q=vnc
Comment by John (graysky) - Saturday, 17 August 2013, 12:02 GMT
Sorry, no, I didn't explicitly mention tigervnc since the linked #36186 does.

Testing alternative clients is a good idea.
Using x11vnc on the server, and connecting with the following clients, I am _unable_ to invoke any of the following actions: ctrl+F or ctlr+N or ctrl+T in chromium or in thunar:
*vinagre
*tigervnc
*remmina


The following DO work:
*gtk-vncviewer
*realvnc-viewer (from the AUR)

You are correct in that the problem is not a function of the server, but of the clients. Please close this bug report and thank you for the advice.

Comment by Gaetan Bisson (vesath) - Saturday, 17 August 2013, 23:22 GMT
No worries.

Loading...