Are There Any VNC Servers that Work with Cinnamon DE 3 on Ubuntu 16.04?
Background
I need to remote in from Windows to Ubuntu 16.04, using Cinnamon DE 3.2.2.
However, when I try to get VNC set up, everything fails. After researching, I've found that it's because Cinnamon uses acceleration of some type.
What I've Tried
I've tried RealVNC, TightVNC, TigerVNC. I just get a black screen on the VNC Viewer.
I've tried using RDP, and I was able to get in, but only by using the Gnome Session Flashback, which caused me to just be using Gnome instead of Cinnamon, defeating the purpose.
Teamviewer ... costs money for non-personal use.
Question
Is there any VNC server (or any methods in general of remotely viewing the desktop) that work with the current, accelerated Cinnamon Desktop (3.2.2), running on Ubuntu 16.04?
Edit
Here is a screencap of what is happening. I am using VirtualBox to host the machine, on my Windows 10 computer. On the right is my VNC viewer program, which is Real VNC.
Edit 2
Content of output in Terminal, after VNC makes connection:
22/12/2016 08:49:41 Got connection from client 192.168.10.92
22/12/2016 08:49:41 other clients:
22/12/2016 08:49:41 Normal socket connection
22/12/2016 08:49:41 Disabled X server key autorepeat.
22/12/2016 08:49:41 to force back on run: 'xset r on' (3 times)
22/12/2016 08:49:41 incr accepted_client=1 for 192.168.10.92:56946 sock=12
22/12/2016 08:49:41 Client Protocol Version 3.8
22/12/2016 08:49:41 Protocol version sent 3.8, using 3.8
22/12/2016 08:49:41 rfbProcessClientSecurityType: executing handler for type 1
22/12/2016 08:49:41 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Using ZRLE encoding for client 192.168.10.92
22/12/2016 08:49:41 Pixel format for client 192.168.10.92:
22/12/2016 08:49:41 8 bpp, depth 8
22/12/2016 08:49:41 uses a colour map (not true colour).
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Switching from ZRLE to raw Encoding for client 192.168.10.92
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Switching from raw to hextile Encoding for client 192.168.10.92
22/12/2016 08:49:41 Pixel format for client 192.168.10.92:
22/12/2016 08:49:41 32 bpp, depth 24, little endian
22/12/2016 08:49:41 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
22/12/2016 08:49:41 no translation needed
22/12/2016 08:49:41 client 1 network rate 1891.4 KB/sec (1891.4 eff KB/sec)
22/12/2016 08:49:41 client 1 latency: 0.5 ms
22/12/2016 08:49:41 dt1: 0.0002, dt2: 0.0093 dt3: 0.0005 bytes: 17694
22/12/2016 08:49:41 link_rate: LR_LAN - 1 ms, 1891 KB/s
22/12/2016 08:49:41 client useCopyRect: 192.168.10.92 -1
22/12/2016 08:49:41 client_set_net: 192.168.10.92 0.0042
22/12/2016 08:49:41 created xdamage object: 0x3400040
22/12/2016 08:49:42 cursor_noshape_updates_clients: 0
22/12/2016 08:49:44 cursor_noshape_updates_clients: 0
22/12/2016 08:49:49 cursor_noshape_updates_clients: 0
22/12/2016 08:49:50 created selwin: 0x3400041
22/12/2016 08:49:50 called initialize_xfixes()
22/12/2016 08:49:52 cursor_noshape_updates_clients: 0
remote-desktop vnc cinnamon
asked Dec 21 '16 at 16:42
Andy MercerAndy Mercer
10615
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Background
I need to remote in from Windows to Ubuntu 16.04, using Cinnamon DE 3.2.2.
However, when I try to get VNC set up, everything fails. After researching, I've found that it's because Cinnamon uses acceleration of some type.
What I've Tried
I've tried RealVNC, TightVNC, TigerVNC. I just get a black screen on the VNC Viewer.
I've tried using RDP, and I was able to get in, but only by using the Gnome Session Flashback, which caused me to just be using Gnome instead of Cinnamon, defeating the purpose.
Teamviewer ... costs money for non-personal use.
Question
Is there any VNC server (or any methods in general of remotely viewing the desktop) that work with the current, accelerated Cinnamon Desktop (3.2.2), running on Ubuntu 16.04?
Edit
Here is a screencap of what is happening. I am using VirtualBox to host the machine, on my Windows 10 computer. On the right is my VNC viewer program, which is Real VNC.
Edit 2
Content of output in Terminal, after VNC makes connection:
22/12/2016 08:49:41 Got connection from client 192.168.10.92
22/12/2016 08:49:41 other clients:
22/12/2016 08:49:41 Normal socket connection
22/12/2016 08:49:41 Disabled X server key autorepeat.
22/12/2016 08:49:41 to force back on run: 'xset r on' (3 times)
22/12/2016 08:49:41 incr accepted_client=1 for 192.168.10.92:56946 sock=12
22/12/2016 08:49:41 Client Protocol Version 3.8
22/12/2016 08:49:41 Protocol version sent 3.8, using 3.8
22/12/2016 08:49:41 rfbProcessClientSecurityType: executing handler for type 1
22/12/2016 08:49:41 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Using ZRLE encoding for client 192.168.10.92
22/12/2016 08:49:41 Pixel format for client 192.168.10.92:
22/12/2016 08:49:41 8 bpp, depth 8
22/12/2016 08:49:41 uses a colour map (not true colour).
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Switching from ZRLE to raw Encoding for client 192.168.10.92
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Switching from raw to hextile Encoding for client 192.168.10.92
22/12/2016 08:49:41 Pixel format for client 192.168.10.92:
22/12/2016 08:49:41 32 bpp, depth 24, little endian
22/12/2016 08:49:41 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
22/12/2016 08:49:41 no translation needed
22/12/2016 08:49:41 client 1 network rate 1891.4 KB/sec (1891.4 eff KB/sec)
22/12/2016 08:49:41 client 1 latency: 0.5 ms
22/12/2016 08:49:41 dt1: 0.0002, dt2: 0.0093 dt3: 0.0005 bytes: 17694
22/12/2016 08:49:41 link_rate: LR_LAN - 1 ms, 1891 KB/s
22/12/2016 08:49:41 client useCopyRect: 192.168.10.92 -1
22/12/2016 08:49:41 client_set_net: 192.168.10.92 0.0042
22/12/2016 08:49:41 created xdamage object: 0x3400040
22/12/2016 08:49:42 cursor_noshape_updates_clients: 0
22/12/2016 08:49:44 cursor_noshape_updates_clients: 0
22/12/2016 08:49:49 cursor_noshape_updates_clients: 0
22/12/2016 08:49:50 created selwin: 0x3400041
22/12/2016 08:49:50 called initialize_xfixes()
22/12/2016 08:49:52 cursor_noshape_updates_clients: 0
remote-desktop vnc cinnamon
asked Dec 21 '16 at 16:42
Andy MercerAndy Mercer
10615
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Added output, David.
– Andy Mercer
Dec 22 '16 at 13:53
add a comment |
Background
I need to remote in from Windows to Ubuntu 16.04, using Cinnamon DE 3.2.2.
However, when I try to get VNC set up, everything fails. After researching, I've found that it's because Cinnamon uses acceleration of some type.
What I've Tried
I've tried RealVNC, TightVNC, TigerVNC. I just get a black screen on the VNC Viewer.
I've tried using RDP, and I was able to get in, but only by using the Gnome Session Flashback, which caused me to just be using Gnome instead of Cinnamon, defeating the purpose.
Teamviewer ... costs money for non-personal use.
Question
Is there any VNC server (or any methods in general of remotely viewing the desktop) that work with the current, accelerated Cinnamon Desktop (3.2.2), running on Ubuntu 16.04?
Edit
Here is a screencap of what is happening. I am using VirtualBox to host the machine, on my Windows 10 computer. On the right is my VNC viewer program, which is Real VNC.
Edit 2
Content of output in Terminal, after VNC makes connection:
22/12/2016 08:49:41 Got connection from client 192.168.10.92
22/12/2016 08:49:41 other clients:
22/12/2016 08:49:41 Normal socket connection
22/12/2016 08:49:41 Disabled X server key autorepeat.
22/12/2016 08:49:41 to force back on run: 'xset r on' (3 times)
22/12/2016 08:49:41 incr accepted_client=1 for 192.168.10.92:56946 sock=12
22/12/2016 08:49:41 Client Protocol Version 3.8
22/12/2016 08:49:41 Protocol version sent 3.8, using 3.8
22/12/2016 08:49:41 rfbProcessClientSecurityType: executing handler for type 1
22/12/2016 08:49:41 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Using ZRLE encoding for client 192.168.10.92
22/12/2016 08:49:41 Pixel format for client 192.168.10.92:
22/12/2016 08:49:41 8 bpp, depth 8
22/12/2016 08:49:41 uses a colour map (not true colour).
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Switching from ZRLE to raw Encoding for client 192.168.10.92
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Switching from raw to hextile Encoding for client 192.168.10.92
22/12/2016 08:49:41 Pixel format for client 192.168.10.92:
22/12/2016 08:49:41 32 bpp, depth 24, little endian
22/12/2016 08:49:41 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
22/12/2016 08:49:41 no translation needed
22/12/2016 08:49:41 client 1 network rate 1891.4 KB/sec (1891.4 eff KB/sec)
22/12/2016 08:49:41 client 1 latency: 0.5 ms
22/12/2016 08:49:41 dt1: 0.0002, dt2: 0.0093 dt3: 0.0005 bytes: 17694
22/12/2016 08:49:41 link_rate: LR_LAN - 1 ms, 1891 KB/s
22/12/2016 08:49:41 client useCopyRect: 192.168.10.92 -1
22/12/2016 08:49:41 client_set_net: 192.168.10.92 0.0042
22/12/2016 08:49:41 created xdamage object: 0x3400040
22/12/2016 08:49:42 cursor_noshape_updates_clients: 0
22/12/2016 08:49:44 cursor_noshape_updates_clients: 0
22/12/2016 08:49:49 cursor_noshape_updates_clients: 0
22/12/2016 08:49:50 created selwin: 0x3400041
22/12/2016 08:49:50 called initialize_xfixes()
22/12/2016 08:49:52 cursor_noshape_updates_clients: 0
remote-desktop vnc cinnamon
asked Dec 21 '16 at 16:42
Andy MercerAndy Mercer
10615
Background
I need to remote in from Windows to Ubuntu 16.04, using Cinnamon DE 3.2.2.
However, when I try to get VNC set up, everything fails. After researching, I've found that it's because Cinnamon uses acceleration of some type.
What I've Tried
I've tried RealVNC, TightVNC, TigerVNC. I just get a black screen on the VNC Viewer.
I've tried using RDP, and I was able to get in, but only by using the Gnome Session Flashback, which caused me to just be using Gnome instead of Cinnamon, defeating the purpose.
Teamviewer ... costs money for non-personal use.
Question
Is there any VNC server (or any methods in general of remotely viewing the desktop) that work with the current, accelerated Cinnamon Desktop (3.2.2), running on Ubuntu 16.04?
Edit
Here is a screencap of what is happening. I am using VirtualBox to host the machine, on my Windows 10 computer. On the right is my VNC viewer program, which is Real VNC.
Edit 2
Content of output in Terminal, after VNC makes connection:
22/12/2016 08:49:41 Got connection from client 192.168.10.92
22/12/2016 08:49:41 other clients:
22/12/2016 08:49:41 Normal socket connection
22/12/2016 08:49:41 Disabled X server key autorepeat.
22/12/2016 08:49:41 to force back on run: 'xset r on' (3 times)
22/12/2016 08:49:41 incr accepted_client=1 for 192.168.10.92:56946 sock=12
22/12/2016 08:49:41 Client Protocol Version 3.8
22/12/2016 08:49:41 Protocol version sent 3.8, using 3.8
22/12/2016 08:49:41 rfbProcessClientSecurityType: executing handler for type 1
22/12/2016 08:49:41 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Using ZRLE encoding for client 192.168.10.92
22/12/2016 08:49:41 Pixel format for client 192.168.10.92:
22/12/2016 08:49:41 8 bpp, depth 8
22/12/2016 08:49:41 uses a colour map (not true colour).
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Switching from ZRLE to raw Encoding for client 192.168.10.92
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
22/12/2016 08:49:41 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
22/12/2016 08:49:41 Enabling full-color cursor updates for client 192.168.10.92
22/12/2016 08:49:41 Enabling NewFBSize protocol extension for client 192.168.10.92
22/12/2016 08:49:41 Switching from raw to hextile Encoding for client 192.168.10.92
22/12/2016 08:49:41 Pixel format for client 192.168.10.92:
22/12/2016 08:49:41 32 bpp, depth 24, little endian
22/12/2016 08:49:41 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
22/12/2016 08:49:41 no translation needed
22/12/2016 08:49:41 client 1 network rate 1891.4 KB/sec (1891.4 eff KB/sec)
22/12/2016 08:49:41 client 1 latency: 0.5 ms
22/12/2016 08:49:41 dt1: 0.0002, dt2: 0.0093 dt3: 0.0005 bytes: 17694
22/12/2016 08:49:41 link_rate: LR_LAN - 1 ms, 1891 KB/s
22/12/2016 08:49:41 client useCopyRect: 192.168.10.92 -1
22/12/2016 08:49:41 client_set_net: 192.168.10.92 0.0042
22/12/2016 08:49:41 created xdamage object: 0x3400040
22/12/2016 08:49:42 cursor_noshape_updates_clients: 0
22/12/2016 08:49:44 cursor_noshape_updates_clients: 0
22/12/2016 08:49:49 cursor_noshape_updates_clients: 0
22/12/2016 08:49:50 created selwin: 0x3400041
22/12/2016 08:49:50 called initialize_xfixes()
22/12/2016 08:49:52 cursor_noshape_updates_clients: 0
remote-desktop vnc cinnamon
remote-desktop vnc cinnamon
asked Dec 21 '16 at 16:42
Andy MercerAndy Mercer
10615
asked Dec 21 '16 at 16:42
Andy MercerAndy Mercer
10615
edited Dec 22 '16 at 13:53
Andy Mercer
asked Dec 21 '16 at 16:42
Andy MercerAndy Mercer
10615
asked Dec 21 '16 at 16:42
Andy MercerAndy Mercer
10615
asked Dec 21 '16 at 16:42
Andy MercerAndy Mercer
10615
10615
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Added output, David.
– Andy Mercer
Dec 22 '16 at 13:53
add a comment |
Added output, David.
– Andy Mercer
Dec 22 '16 at 13:53
Added output, David.
– Andy Mercer
Dec 22 '16 at 13:53
Added output, David.
– Andy Mercer
Dec 22 '16 at 13:53
add a comment |
2 Answers
2
active
oldest
votes
Have you tried TeamViewer?
https://www.teamviewer.com/en/download/linux/
I use in my debian with openbox and it works fine.
answered Dec 21 '16 at 17:20
AdonistAdonist
1504
"Teamviewer ... costs money for non-personal use."
– Andy Mercer
Dec 21 '16 at 17:27
Cool, I didn't know your environment.
– Adonist
Dec 21 '16 at 17:42
Have you tried: chmod 775 xstartup ? in the /home/user/.vnc/xstartup file
– Adonist
Dec 21 '16 at 17:42
I'm quoting because I said that in my question. I can't use Teamviewer because my boss doesn't want to pay money. Right now the machine is using Ubuntu 5 or something really old like that. And he is used to having completely free remote access. Teamviewer is hundreds of dollars for a corporate use, unfortunately.
– Andy Mercer
Dec 21 '16 at 18:43
add a comment |
As Cinnamon Desktop is a fork of Gnome Shell and x11vnc works well on my system I'd say the issue on yours is not the window compositor.
When you start the VNC server from an SSH session (or any other terminal session that wasn't spawned from an X11 session) you need to tell it which X11 display to use, e. g.:
x11vnc -display :0
or
DISPLAY=:0 x11vnc
Other VNC server may use different ways to specify the display but they should accept the DISPLAY environment variable by convention.
x11vnc also allows “symbolic” display names based on the account name of the user owning the X session. It can also create new X sessions on a virtual Xfvb display device. For more see the description of the -display option in the x11vnc(1) manual.
You can also try Vino, a GUI configuration interface to provide remote (VNC) access to a currently running desktop session.
answered Dec 21 '16 at 18:25
David FoersterDavid Foerster
28.2k1365111
I went back to my saved image of Cinnamon without any VNC installed, and installed x11vnc. Then I tried both of your lines of code. They don't appear to be changing settings. They launch the server. However, what I see is still just a black screen. I'm updating my question to show a screencap.
– Andy Mercer
Dec 21 '16 at 19:02
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f863118%2fare-there-any-vnc-servers-that-work-with-cinnamon-de-3-on-ubuntu-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Have you tried TeamViewer?
https://www.teamviewer.com/en/download/linux/
I use in my debian with openbox and it works fine.
answered Dec 21 '16 at 17:20
AdonistAdonist
1504
"Teamviewer ... costs money for non-personal use."
– Andy Mercer
Dec 21 '16 at 17:27
Cool, I didn't know your environment.
– Adonist
Dec 21 '16 at 17:42
Have you tried: chmod 775 xstartup ? in the /home/user/.vnc/xstartup file
– Adonist
Dec 21 '16 at 17:42
I'm quoting because I said that in my question. I can't use Teamviewer because my boss doesn't want to pay money. Right now the machine is using Ubuntu 5 or something really old like that. And he is used to having completely free remote access. Teamviewer is hundreds of dollars for a corporate use, unfortunately.
– Andy Mercer
Dec 21 '16 at 18:43
add a comment |
Have you tried TeamViewer?
https://www.teamviewer.com/en/download/linux/
I use in my debian with openbox and it works fine.
answered Dec 21 '16 at 17:20
AdonistAdonist
1504
"Teamviewer ... costs money for non-personal use."
– Andy Mercer
Dec 21 '16 at 17:27
Cool, I didn't know your environment.
– Adonist
Dec 21 '16 at 17:42
Have you tried: chmod 775 xstartup ? in the /home/user/.vnc/xstartup file
– Adonist
Dec 21 '16 at 17:42
I'm quoting because I said that in my question. I can't use Teamviewer because my boss doesn't want to pay money. Right now the machine is using Ubuntu 5 or something really old like that. And he is used to having completely free remote access. Teamviewer is hundreds of dollars for a corporate use, unfortunately.
– Andy Mercer
Dec 21 '16 at 18:43
add a comment |
Have you tried TeamViewer?
https://www.teamviewer.com/en/download/linux/
I use in my debian with openbox and it works fine.
answered Dec 21 '16 at 17:20
AdonistAdonist
1504
Have you tried TeamViewer?
https://www.teamviewer.com/en/download/linux/
I use in my debian with openbox and it works fine.
answered Dec 21 '16 at 17:20
AdonistAdonist
1504
answered Dec 21 '16 at 17:20
AdonistAdonist
1504
answered Dec 21 '16 at 17:20
AdonistAdonist
1504
answered Dec 21 '16 at 17:20
AdonistAdonist
1504
1504
"Teamviewer ... costs money for non-personal use."
– Andy Mercer
Dec 21 '16 at 17:27
Cool, I didn't know your environment.
– Adonist
Dec 21 '16 at 17:42
Have you tried: chmod 775 xstartup ? in the /home/user/.vnc/xstartup file
– Adonist
Dec 21 '16 at 17:42
I'm quoting because I said that in my question. I can't use Teamviewer because my boss doesn't want to pay money. Right now the machine is using Ubuntu 5 or something really old like that. And he is used to having completely free remote access. Teamviewer is hundreds of dollars for a corporate use, unfortunately.
– Andy Mercer
Dec 21 '16 at 18:43
add a comment |
"Teamviewer ... costs money for non-personal use."
– Andy Mercer
Dec 21 '16 at 17:27
Cool, I didn't know your environment.
– Adonist
Dec 21 '16 at 17:42
Have you tried: chmod 775 xstartup ? in the /home/user/.vnc/xstartup file
– Adonist
Dec 21 '16 at 17:42
I'm quoting because I said that in my question. I can't use Teamviewer because my boss doesn't want to pay money. Right now the machine is using Ubuntu 5 or something really old like that. And he is used to having completely free remote access. Teamviewer is hundreds of dollars for a corporate use, unfortunately.
– Andy Mercer
Dec 21 '16 at 18:43
"Teamviewer ... costs money for non-personal use."
– Andy Mercer
Dec 21 '16 at 17:27
"Teamviewer ... costs money for non-personal use."
– Andy Mercer
Dec 21 '16 at 17:27
Cool, I didn't know your environment.
– Adonist
Dec 21 '16 at 17:42
Cool, I didn't know your environment.
– Adonist
Dec 21 '16 at 17:42
Have you tried: chmod 775 xstartup ? in the /home/user/.vnc/xstartup file
– Adonist
Dec 21 '16 at 17:42
Have you tried: chmod 775 xstartup ? in the /home/user/.vnc/xstartup file
– Adonist
Dec 21 '16 at 17:42
I'm quoting because I said that in my question. I can't use Teamviewer because my boss doesn't want to pay money. Right now the machine is using Ubuntu 5 or something really old like that. And he is used to having completely free remote access. Teamviewer is hundreds of dollars for a corporate use, unfortunately.
– Andy Mercer
Dec 21 '16 at 18:43
I'm quoting because I said that in my question. I can't use Teamviewer because my boss doesn't want to pay money. Right now the machine is using Ubuntu 5 or something really old like that. And he is used to having completely free remote access. Teamviewer is hundreds of dollars for a corporate use, unfortunately.
– Andy Mercer
Dec 21 '16 at 18:43
add a comment |
As Cinnamon Desktop is a fork of Gnome Shell and x11vnc works well on my system I'd say the issue on yours is not the window compositor.
When you start the VNC server from an SSH session (or any other terminal session that wasn't spawned from an X11 session) you need to tell it which X11 display to use, e. g.:
x11vnc -display :0
or
DISPLAY=:0 x11vnc
Other VNC server may use different ways to specify the display but they should accept the DISPLAY environment variable by convention.
x11vnc also allows “symbolic” display names based on the account name of the user owning the X session. It can also create new X sessions on a virtual Xfvb display device. For more see the description of the -display option in the x11vnc(1) manual.
You can also try Vino, a GUI configuration interface to provide remote (VNC) access to a currently running desktop session.
answered Dec 21 '16 at 18:25
David FoersterDavid Foerster
28.2k1365111
I went back to my saved image of Cinnamon without any VNC installed, and installed x11vnc. Then I tried both of your lines of code. They don't appear to be changing settings. They launch the server. However, what I see is still just a black screen. I'm updating my question to show a screencap.
– Andy Mercer
Dec 21 '16 at 19:02
add a comment |
As Cinnamon Desktop is a fork of Gnome Shell and x11vnc works well on my system I'd say the issue on yours is not the window compositor.
When you start the VNC server from an SSH session (or any other terminal session that wasn't spawned from an X11 session) you need to tell it which X11 display to use, e. g.:
x11vnc -display :0
or
DISPLAY=:0 x11vnc
Other VNC server may use different ways to specify the display but they should accept the DISPLAY environment variable by convention.
x11vnc also allows “symbolic” display names based on the account name of the user owning the X session. It can also create new X sessions on a virtual Xfvb display device. For more see the description of the -display option in the x11vnc(1) manual.
You can also try Vino, a GUI configuration interface to provide remote (VNC) access to a currently running desktop session.
answered Dec 21 '16 at 18:25
David FoersterDavid Foerster
28.2k1365111
I went back to my saved image of Cinnamon without any VNC installed, and installed x11vnc. Then I tried both of your lines of code. They don't appear to be changing settings. They launch the server. However, what I see is still just a black screen. I'm updating my question to show a screencap.
– Andy Mercer
Dec 21 '16 at 19:02
add a comment |
As Cinnamon Desktop is a fork of Gnome Shell and x11vnc works well on my system I'd say the issue on yours is not the window compositor.
When you start the VNC server from an SSH session (or any other terminal session that wasn't spawned from an X11 session) you need to tell it which X11 display to use, e. g.:
x11vnc -display :0
or
DISPLAY=:0 x11vnc
Other VNC server may use different ways to specify the display but they should accept the DISPLAY environment variable by convention.
x11vnc also allows “symbolic” display names based on the account name of the user owning the X session. It can also create new X sessions on a virtual Xfvb display device. For more see the description of the -display option in the x11vnc(1) manual.
You can also try Vino, a GUI configuration interface to provide remote (VNC) access to a currently running desktop session.
answered Dec 21 '16 at 18:25
David FoersterDavid Foerster
28.2k1365111
As Cinnamon Desktop is a fork of Gnome Shell and x11vnc works well on my system I'd say the issue on yours is not the window compositor.
When you start the VNC server from an SSH session (or any other terminal session that wasn't spawned from an X11 session) you need to tell it which X11 display to use, e. g.:
x11vnc -display :0
or
DISPLAY=:0 x11vnc
Other VNC server may use different ways to specify the display but they should accept the DISPLAY environment variable by convention.
x11vnc also allows “symbolic” display names based on the account name of the user owning the X session. It can also create new X sessions on a virtual Xfvb display device. For more see the description of the -display option in the x11vnc(1) manual.
You can also try Vino, a GUI configuration interface to provide remote (VNC) access to a currently running desktop session.
answered Dec 21 '16 at 18:25
David FoersterDavid Foerster
28.2k1365111
edited Dec 21 '16 at 23:39
answered Dec 21 '16 at 18:25
David FoersterDavid Foerster
28.2k1365111
answered Dec 21 '16 at 18:25
David FoersterDavid Foerster
28.2k1365111
answered Dec 21 '16 at 18:25
David FoersterDavid Foerster
28.2k1365111
28.2k1365111
I went back to my saved image of Cinnamon without any VNC installed, and installed x11vnc. Then I tried both of your lines of code. They don't appear to be changing settings. They launch the server. However, what I see is still just a black screen. I'm updating my question to show a screencap.
– Andy Mercer
Dec 21 '16 at 19:02
add a comment |
I went back to my saved image of Cinnamon without any VNC installed, and installed x11vnc. Then I tried both of your lines of code. They don't appear to be changing settings. They launch the server. However, what I see is still just a black screen. I'm updating my question to show a screencap.
– Andy Mercer
Dec 21 '16 at 19:02
I went back to my saved image of Cinnamon without any VNC installed, and installed x11vnc. Then I tried both of your lines of code. They don't appear to be changing settings. They launch the server. However, what I see is still just a black screen. I'm updating my question to show a screencap.
– Andy Mercer
Dec 21 '16 at 19:02
I went back to my saved image of Cinnamon without any VNC installed, and installed x11vnc. Then I tried both of your lines of code. They don't appear to be changing settings. They launch the server. However, what I see is still just a black screen. I'm updating my question to show a screencap.
– Andy Mercer
Dec 21 '16 at 19:02
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f863118%2fare-there-any-vnc-servers-that-work-with-cinnamon-de-3-on-ubuntu-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Added output, David.
– Andy Mercer
Dec 22 '16 at 13:53