-
Notifications
You must be signed in to change notification settings - Fork 106
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
TigerVNC check does not work for new versions of TigerVNC #69
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
@goekce this is an amazing issue writeup! Thank you!!! I think the short term fix at least should be to look if |
Currently I don't have time for a PR. Someone else is welcome to take over the pull request. |
Both TurboVNC (vncserver.in) and TigerVNC (vncserver.in) has vncserver.in, but Tiger as installed via I think we should still check for @goekce Is the file you see when doing Content from two images installing tiger/turbo vnc
|
You are right, the packaging of tigervnc from Debian/Ubuntu seems to be idiosyncratic:
|
Bug description
I am on Arch Linux. I installed my own TigerVNC, because the bundled TigerVNC segfaults when I start Firefox.
jupyter-remote-desktop-proxy picks the configuration based on whether the string
TigerVNC
can be found invncserver
:jupyter-remote-desktop-proxy/jupyter_remote_desktop_proxy/__init__.py
Line 25 in 024ab7d
The newest version of
vncserver
does not includeTigerVNC
as a string, which can lead to wrong configuration of the installed VNC server.The workaround is to use
tigervnc
as a string instead ofTigerVNC
. I can happily prepare a PR, however I also saw that there is a discussion about which vncservers to support, so I wanted to confirm if my workaround makes sense.I can include more details, if the error description is not clear.
A general remark about configurability:
The configuration can change between the software versions, so a more sustainable solution would be to make the command for starting the VNC session configurable. Currently the config is mostly hardcoded. Another argument that calls for a configuration capability: the newest
vncserver
does not support-xstartup
argument used here:jupyter-remote-desktop-proxy/jupyter_remote_desktop_proxy/__init__.py
Lines 34 to 35 in 024ab7d
I can open a new issue for this if needed.
The text was updated successfully, but these errors were encountered: