Vnc - Revision history

M at 23:41, 18 July 2020

2020-07-18T23:41:15Z

← Older revision		Revision as of 23:41, 18 July 2020
Line 58:		Line 58:
	sudo apt-get install remina # VNC client		sudo apt-get install remina # VNC client

	Ubuntu screwed the pooch on vino-server config, ~~wtf you idiots. It's just some fucking app with~~ no systemd support. ~~Well fuck if I'm jumping hoops when the next LTS release is weeks away~~. ~~Fuck~~ you ~~ubuntu~~. ~~Just run the god damned thing directly~~		Ubuntu screwed the pooch on vino-server config, no systemd support baked in? [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-20-04 This] explains how you can set up a service. Geez oh pete.

	# allow local connections		# allow local connections

M at 23:22, 18 July 2020

2020-07-18T23:22:39Z

← Older revision		Revision as of 23:22, 18 July 2020
Line 34:		Line 34:
	* Run it!		* Run it!
	vncviewer & # and enter [localhost:59000]		vncviewer & # and enter [localhost:59000]

			Bah bullshit, I can't get the i3 display to start up properly.

	===== Troubleshooting =====		===== Troubleshooting =====
Line 48:		Line 50:
	vncserver -kill :2 # or .3 or .4...		vncserver -kill :2 # or .3 or .4...
	vncserver -localhost # should start on .2 since X is already running - is that a prob?		vncserver -localhost # should start on .2 since X is already running - is that a prob?


	==== vino & remina ====		==== vino & remina ====

M at 21:28, 18 July 2020

2020-07-18T21:28:38Z

@@ Line 31: / Line 31: @@
 ===== Remote client connect =====
 * On remote machine, install client package (this is actually tightvnc, cmon assholes fix the name):
-  sudo apt install vncviewer
+  sudo apt install xvnctightviewer
 ==== vino & remina ====

M at 21:00, 18 July 2020

2020-07-18T21:00:41Z

← Older revision		Revision as of 21:00, 18 July 2020
Line 5:		Line 5:
	Solid but more work.		Solid but more work.

	===== ~~Installation~~ =====		===== Server installation =====
	* ~~Server~~ install:		* Package install:
	apt install tightvncserver		apt install tightvncserver
			* Update the server config:
	vncserver		vncserver
	# enter pwd		# enter pwd
Line 13:		Line 14:
	# note the result, eg: New 'X' desktop is melange:2		# note the result, eg: New 'X' desktop is melange:2
	# in this case, vnc desktop is running on desktop 2, because 1 was already running 'regular' X		# in this case, vnc desktop is running on desktop 2, because 1 was already running 'regular' X
	* Update the server config:
	cd ~/.vnc		cd ~/.vnc
	cp xstartup xstartup.orig		cp xstartup xstartup.orig
Line 22:		Line 22:
	vncserver -localhost # only allow connections from localhost; we will use ssh tunnel		vncserver -localhost # only allow connections from localhost; we will use ssh tunnel

			===== Network configuration =====
			* Set up an ssh tunnel on the home LAN to the VNC server:
			ssh -L 59000:localhost:5901 -C -N melange
			You can leave this running to enable anytime-connect.
			* Set up an ssh tunnel on remote client (eg. viper) to the home LAN:
			ssh -L 59000:localhost:59000 -C -N bitpost.com

			===== Remote client connect =====
			* On remote machine, install client package (this is actually tightvnc, cmon assholes fix the name):
			sudo apt install vncviewer

	==== vino & remina ====		==== vino & remina ====

M at 20:23, 18 July 2020

2020-07-18T20:23:03Z

← Older revision		Revision as of 20:23, 18 July 2020
Line 6:		Line 6:

	===== Installation =====		===== Installation =====
	* ~~on server~~		* Server install:
	apt install tightvncserver		apt install tightvncserver
	vncserver		vncserver
Line 13:		Line 13:
	# note the result, eg: New 'X' desktop is melange:2		# note the result, eg: New 'X' desktop is melange:2
	# in this case, vnc desktop is running on desktop 2, because 1 was already running 'regular' X		# in this case, vnc desktop is running on desktop 2, because 1 was already running 'regular' X
			* Update the server config:
			cd ~/.vnc
			cp xstartup xstartup.orig
			emacs -nw xstartup # and replace with:
			#!/bin/bash
			xrdb $HOME/.Xresources
			/usr/bin/i3 &
			vncserver -localhost # only allow connections from localhost; we will use ssh tunnel


	==== vino & remina ====		==== vino & remina ====

M: /* tightvnc */

2020-07-18T20:07:26Z

tightvnc

← Older revision		Revision as of 20:07, 18 July 2020
Line 4:		Line 4:

	Solid but more work.		Solid but more work.

			===== Installation =====
			* on server
			apt install tightvncserver
			vncserver
			# enter pwd
			# optionally enter pwd for read-only sharing
			# note the result, eg: New 'X' desktop is melange:2
			# in this case, vnc desktop is running on desktop 2, because 1 was already running 'regular' X

	==== vino & remina ====		==== vino & remina ====

M at 19:22, 18 July 2020

2020-07-18T19:22:05Z

← Older revision		Revision as of 19:22, 18 July 2020
Line 1:		Line 1:
	=== Ubuntu-to-Ubuntu ===		=== Ubuntu-to-Ubuntu ===

	~~Everything~~ is brought together under [mh-ubuntu-settings] Ubuntu Settings > Sharing.		==== tightvnc ====

			Solid but more work.

			==== vino & remina ====
			Using the "Ubuntu way", everything is supposed to be brought together under [mh-ubuntu-settings] Ubuntu Settings > Sharing. (but it's crap, read on...)

	The packages it needs underneath are:		The packages it needs underneath are:

M: Created page with "=== Ubuntu-to-Ubuntu === Everything is brought together under [mh-ubuntu-settings] Ubuntu Settings > Sharing. The packages it needs underneath are: sudo apt-get install vin..."

2020-07-18T19:20:28Z

Created page with "=== Ubuntu-to-Ubuntu === Everything is brought together under [mh-ubuntu-settings] Ubuntu Settings > Sharing. The packages it needs underneath are: sudo apt-get install vin..."

New page

=== Ubuntu-to-Ubuntu ===

Everything is brought together under [mh-ubuntu-settings] Ubuntu Settings > Sharing.

The packages it needs underneath are:
sudo apt-get install vino # VNC server; RESTART GNOME after installation
sudo apt-get install remina # VNC client

Ubuntu screwed the pooch on vino-server config, wtf you idiots. It's just some fucking app with no systemd support. Well fuck if I'm jumping hoops when the next LTS release is weeks away. Fuck you ubuntu. Just run the god damned thing directly

# allow local connections
gsettings set org.gnome.Vino network-interface lo

# see all settings
gsettings list-keys org.gnome.Vino

# run the fucker
/usr/lib/vino/vino-server &

Consider other VNC servers instead that allow startup on boot?