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 not input content on AWT textbox (cursor missing) #287
Comments
Can you provide a little more detail (OS, JRE, how to replicate the problem, etc.)? -brian |
Thanks for your quick feedback. I tried to use TigerVNC work with xrdp. I used mstsc to connect my Ubuntn server with "sesman-Xvnc" module, my application (created in java) run into this error. |
I'm sorry, but where does TigerVNC get involved in this if you are using mstsc and xrdp? And is the exception from our viewer? Or some other Java application? |
Contrary to expectations, xrdp does not have a Xserver, but acts as a rdp to rfb translator, using Xvnc. |
Ah, I see. Thanks. So I then assume that the crash here is some random application and not our Java viewer? And looking at the error, it looks like that program is not handling missing atoms properly. Which would most likely be a bug in that program rather than TigerVNC. @happylinda, can you determine which atom it is trying to look up? |
The exception is from our Java application, it is related with copy/paste operation. The detail exception is as below, It seems that it is X related Java problem. I see the following JRE bug fixed. I also see the following suggestion of switching the clipboard manager to workaround the issue: It seems that it is not related with TigerVNC. Thanks for your help. |
Hi,
When I use tigervnc, I run into following error
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException: Failed to retrieve atom name.
at sun.awt.X11.XlibWrapper.XGetAtomName(Native Method)
at sun.awt.X11.XAtom.getName(XAtom.java:198)
Could you help to give me some suggestion? I'm not sure that It's my configuration issue or tigervnc defect.
The text was updated successfully, but these errors were encountered: