Closed goekce closed 9 months ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
@goekce this is an amazing issue writeup! Thank you!!!
I think the short term fix at least should be to look if tiger
is in the lower case version of the string, the check works for old/new versions.
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 apt
doesn't show that directly while Turbo does. I've not yet regonized the vncserver
file I've seen for Tiger when installing it via apt
, but I assume its specific to how it was distributed in apt
.
I think we should still check for tigervnc
in a case insensitive way, but I'm hoping to understand this well enough to fix it robustly.
@goekce Is the file you see when doing cat $(which vncserver)
vncserver.in?
docker run -it --entrypoint bash quay.io/jupyterhub/jupyter-remote-desktop-proxy:main-tigervnc -c 'cat $(which vncserver)' > vncserver-tiger.txt
docker run -it --entrypoint bash quay.io/jupyterhub/jupyter-remote-desktop-proxy:main-turbovnc -c 'cat $(which vncserver)' > vncserver-turbo.txt
cat $(which vncserver)
inside tigervnc imagecat $(which vncserver)
inside turbovnc image
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
:https://github.com/jupyterhub/jupyter-remote-desktop-proxy/blob/024ab7d61dbe403dc10b090bde4eb2239b030d8e/jupyter_remote_desktop_proxy/__init__.py#L25
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:https://github.com/jupyterhub/jupyter-remote-desktop-proxy/blob/024ab7d61dbe403dc10b090bde4eb2239b030d8e/jupyter_remote_desktop_proxy/__init__.py#L34-L35
I can open a new issue for this if needed.