Skip to content

Fix missing details with VNC setup #1628

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

Closed
wants to merge 1 commit into from
Closed

Conversation

rugk
Copy link

@rugk rugk commented Jul 22, 2020

  • The /root/.vnc/config.d/vncserver-x11 did not have any Authenticationentries in my case, so we cannot replace, but append a string
  • Add a note on how to restart the vnc server (I hope I am right that I need to restart both vncserver-virtuald.service and vncserver-x11-serviced.service)
  • Add a note on how to open/edit the file.
  • Clarify where to find the "VNC Server dialog".
  • Even if you do not connect it to a screen, you can start (and autologin)

* The `/root/.vnc/config.d/vncserver-x11` did not have any `Authentication`entries in my case, so we cannot replace, but append a string
* Add a note on how to restart the vnc server (I hope I am right that I need to restart both `vncserver-virtuald.service` and `vncserver-x11-serviced.service`)
* Add a note on how to open/edit the file.
* Clarify where to find the "VNC Server dialog". 
* Even if you do not connect it to a screen, you can start (and autologin)
@rugk
Copy link
Author

rugk commented Jul 22, 2020

Note I did not include the workaround for raspberrypi/noobs#599 in here.

@ghost
Copy link

ghost commented Jul 23, 2020

  • Even if you do not connect it to a screen, you can start (and autologin)

Enabling boot to desktop and autologin does not force local display output, nor is it meant to. (You've also added this to the virtual desktop section of the VNC instructions, which is for the case where the user wishes to have the VNC desktop separate from any local display which may or may not be running).

@ghost
Copy link

ghost commented Jul 24, 2020

  • Even if you do not connect it to a screen, you can start (and autologin)

Enabling boot to desktop and autologin does not force local display output, nor is it meant to. (You've also added this to the virtual desktop section of the VNC instructions, which is for the case where the user wishes to have the VNC desktop separate from any local display which may or may not be running).

Sorry, I'm talking rubbish. On Pi Zero, 1, 2 and 3 if there is no screen detected on HDMI, the display will come up on composite: on Pi 4 you get no display.

The fact quite a few folk seem to have trouble with VNC means the documentation could probably do with improving.

@ghost
Copy link

ghost commented Jul 24, 2020

See #1631

@rugk
Copy link
Author

rugk commented Jul 26, 2020

Enabling boot to desktop and autologin does not force local display output, nor is it meant to

Really? In my case it always worked. Do you have a quote/source for this?

@JamesH65
Copy link
Contributor

Has this PR been replaced by #1631? @andrum99

@ghost
Copy link

ghost commented Aug 12, 2020

Has this PR been replaced by #1631? @andrum99

That was the intention originally, but I think I need to verify the proposed additions/corrections in this PR as well, since it seems the docs as currently written may not match the current situation.

@aallan
Copy link
Contributor

aallan commented Jun 7, 2021

In light of #1911 and the lack of progress in a long while I'm marking this PR as 7 day closure.

@aallan
Copy link
Contributor

aallan commented Jun 17, 2021

No one picked this up inside the 7 day closure window. So closing due to #1911.

@aallan aallan closed this Jun 17, 2021
@rugk rugk deleted the patch-1 branch June 19, 2021 08:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants