Skip to content
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

Let user defines its own xstartup and geometry via ~/.vnc/xstartup #35

Merged
merged 1 commit into from
Sep 14, 2023

Conversation

cmd-ntrf
Copy link
Contributor

@cmd-ntrf cmd-ntrf commented May 9, 2023

User can override the default provided xstartup by providing their own in the standard location ~/.vnc/xstartup. We also remove the prescribed geometry to let the user define its own using vnc config or the session manager.

@github-actions
Copy link

github-actions bot commented May 9, 2023

Binder 👈 Launch a binder notebook on this branch for commit b01c897

Binder 👈 Launch a binder notebook on this branch for commit e89c17e

Binder 👈 Launch a binder notebook on this branch for commit 66fb7a2

Binder 👈 Launch a binder notebook on this branch for commit cf02bd8

Binder 👈 Launch a binder notebook on this branch for commit fb47c59

@consideRatio
Copy link
Member

We remove -geometry, but what happens if nothing is specified now? Are users installing this to expect a change, perhaps a change depending on default config for turbovnc / tigervnc?

I think this makes sense overall, but I think the geometry aspect requires some docs, inline comments, and clarity with regards to if its a breaking change and if so guidance for users handling this breaking change.

@yuvipanda
Copy link
Contributor

I couldn't push to this branch for some reason, so I've amended this and opened #45.

@cmd-ntrf
Copy link
Contributor Author

Regarding the removal of -geometry, based on my experience, when -geometry is left undefined, the desktop is started with a resolution of 1024x768.
This is also what is specified in the manual:
https://github.com/TigerVNC/tigervnc/blob/8d2739fa71eaf7a28d63ac62583e8087c66a5247/unix/xserver/hw/vnc/Xvnc.man#L35
and in Xvnc C code:
https://github.com/TigerVNC/tigervnc/blob/8d2739fa71eaf7a28d63ac62583e8087c66a5247/unix/xserver/hw/vnc/xvnc.c#L77

Any reason why we would want to substitute this low resolution value by another arbitrary default value? I would argue that a lower resolution has higher chance of being the appropriate fit for most screen. Even more, if we consider the desktop is actually displayed in a browser tab.

In any case, the users could change bypass the resolution set on the command-line by specifying the geometry in ~/.vnc/config. They can also dynamically change the resolution settings using Xfce Display application.

@yuvipanda
Copy link
Contributor

Yay, welcome back @cmd-ntrf!

I think mostly people now expect the default to be 1680x1050 because that's what we have been shipping with, and this change would change the default practically to 1024x768. That's the primary reason I'd like that change to not be here as part of this PR. That's a significant drop in resolution!

If you can split that out into a separate PR, we can discuss that, as allowing custom xstartup is simple and useful by itself.

@cmd-ntrf
Copy link
Contributor Author

Alright, let's split this!

User can override the default provided xstartup by providing
their own in the standard location ~/.vnc/xstartup.
@yuvipanda yuvipanda merged commit a016a6d into jupyterhub:main Sep 14, 2023
2 checks passed
@yuvipanda
Copy link
Contributor

Wheeee, thanks @cmd-ntrf!

@cmd-ntrf
Copy link
Contributor Author

Sorry for the long pause... life got busy.

@yuvipanda
Copy link
Contributor

@cmd-ntrf no worries at all! Grateful for your ongoing contributions whenever you can <3

@consideRatio consideRatio changed the title Let user defines its own xstartup and geometry Let user defines its own xstartup and geometry via ~/.vnc/xstartup Sep 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants