New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't remove on-screen keyboard through config #47
Comments
Which config file are you referring to? The on-screen keyboard is configured using the |
I'm referring to xpra.conf. Options in there have no effect on xpra-html5? I see that there is https://github.com/Xpra-org/xpra-html5/blob/master/html5/default-settings.txt, I'm going to see if I can somehow remove it from there. The URL parameters work for now. Do you know if those commits are included in the xpra version packaged for ubuntu-20.04? |
That's only used by the server, though some of these options will apply to all clients. (but not the on-screen keyboard, which only exists in the html5 client)
OK. I'm closing this ticket then.
The 4.2 release will be out soon and will be packaged for Ubuntu 20.04 in the xpra.org repositories. |
Ok for xpra.conf. Changing default-settings.txt did not seem to have any effect. I will wait for the 4.2 release, thanks for answering me and clarifying those points this fast! |
Hi, I'm now using these versions on Ubuntu 20.04:
and the on-screen keyboard still appears. Is this normal? Thanks for your help. |
No. Sorry. I had missed one location. |
Perfect many thanks :) |
Hi again, The keyboard is still showing in groovy (xpra repos). The versions that are installed are:
Would it be possible to get newer versions? Thanks! |
A new release of the html5 client will happen quite soon but you will not get packages for groovy anywhere: |
Whoops, somehow I missed that! Thanks |
I'm using xpra-html5 on a headless server inside a docker container, and the on-screen keyboard shows up. I can't find a way to deactivate it via the config file.
Could you please let me know how to do that?
The text was updated successfully, but these errors were encountered: