Connect to root display ( :0 ) via VNC
#1
I want to setup VNC so that I can configure stuff remotely from my room when I don't have physical access to the TV that it's connected to. I installed x11vnc and ran it via x11vnc -display :0 -nopw -ncache 10 and it opens successfully. Here's the output:

Code:
03/06/2012 23:51:02 x11vnc version: 0.9.12 lastmod: 2010-09-09  pid: 2971
03/06/2012 23:51:02 Using X display :0
03/06/2012 23:51:02 rootwin: 0xd0 reswin: 0xe00001 dpy: 0x954c4e8
03/06/2012 23:51:02 Default visual ID: 0x23
03/06/2012 23:51:02 Read initial data from X display into framebuffer.
03/06/2012 23:51:02 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/7680
03/06/2012 23:51:02
03/06/2012 23:51:02 X display :0 is 32bpp depth=24 true color
03/06/2012 23:51:02
03/06/2012 23:51:02 Autoprobing TCP port
03/06/2012 23:51:02 Autoprobing selected port 5900
03/06/2012 23:51:02 Listening also on IPv6 port 5900 (socket 10)
03/06/2012 23:51:02
03/06/2012 23:51:02 Xinerama is present and active (e.g. multi-head).
03/06/2012 23:51:02 Xinerama: number of sub-screens: 1
03/06/2012 23:51:02 Xinerama: no blackouts needed (only one sub-screen)
03/06/2012 23:51:02
03/06/2012 23:51:02 fb read rate: 271 MB/sec
03/06/2012 23:51:02 fast read: reset wait  ms to: 10
03/06/2012 23:51:02 fast read: reset defer ms to: 10
03/06/2012 23:51:02 The X server says there are 10 mouse buttons.
03/06/2012 23:51:02 screen setup finished.
03/06/2012 23:51:02

The VNC desktop is:      xbmcbuntu:0
PORT=5900

When I try and connect from another Linux box it connects successfully but all I get is a black screen with a cursor. Here's the console output from the box running XBMC

Code:
03/06/2012 23:51:10 Got connection from client 192.168.1.114
03/06/2012 23:51:10   other clients:
03/06/2012 23:51:10 Disabled X server key autorepeat.
03/06/2012 23:51:10   to force back on run: 'xset r on' (3 times)
03/06/2012 23:51:10 incr accepted_client=1 for 192.168.1.114:44697  sock=11
03/06/2012 23:51:10 Client Protocol Version 3.8
03/06/2012 23:51:10 Protocol version sent 3.8, using 3.8
03/06/2012 23:51:10 rfbProcessClientSecurityType: executing handler for type 1
03/06/2012 23:51:10 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
03/06/2012 23:51:10 Pixel format for client 192.168.1.114:
03/06/2012 23:51:10   32 bpp, depth 24, little endian
03/06/2012 23:51:10   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
03/06/2012 23:51:10 no translation needed
03/06/2012 23:51:10 Using compression level 1 for client 192.168.1.114
03/06/2012 23:51:10 Using image quality level 6 for client 192.168.1.114
03/06/2012 23:51:10 Enabling X-style cursor updates for client 192.168.1.114
03/06/2012 23:51:10 Enabling full-color cursor updates for client 192.168.1.114
03/06/2012 23:51:10 Enabling cursor position updates for client 192.168.1.114
03/06/2012 23:51:10 Enabling LastRect protocol extension for client 192.168.1.114
03/06/2012 23:51:10 Using tight encoding for client 192.168.1.114
03/06/2012 23:51:11 client_set_net: 192.168.1.114  0.0312
03/06/2012 23:51:11 created   xdamage object: 0xe00040
03/06/2012 23:51:14 set_ncache_xrootpmap: trying root background
03/06/2012 23:51:14 snapshotting background...
03/06/2012 23:51:14 done.
03/06/2012 23:51:14 client 1 network rate 2702.6 KB/sec (45482.2 eff KB/sec)
03/06/2012 23:51:14 client 1 latency:  0.5 ms
03/06/2012 23:51:14 dt1: 0.3636, dt2: 0.0016 dt3: 0.0005 bytes: 986460
03/06/2012 23:51:14 link_rate: LR_LAN - 1 ms, 2702 KB/s
03/06/2012 23:51:17 client_count: 0
03/06/2012 23:51:17 Restored X server key autorepeat to: 1
03/06/2012 23:51:17 viewer exited.
03/06/2012 23:51:17 deleted 60 tile_row polling images.

How can I get it to display the XBMC interface?


edit: I had a feeling that the reason I was getting a black screen was because there wasn't a Display Manager active, I logged out and logged back in using XBMCbuntu as the login option and it works perfectly Big Grin
Reply
#2
Install and configured NXSERVER.

Your TV displays XBMC (DISPLAY:0)

NXServer is basically a new session on the same computer running a different Window Manager (Gnove, KDE,etc)
Reply
#3
You may want to explain exactly how you made it work. I have seen other people asking for this.


Yes, NX is very nice but that is not what he is after.
Reply
#4
All I did to get it to work was use the login option that would bring up the DM (the XBMCbuntu option from the dropdown box on the login screen), start the VNC server from the console using x11vnc -display :0 -nopw -many and then connected to it from my other box by running vncconnect 192.168.1.115. The resolution is off a little but I think that's because I have a xinerama setup and the nouveau drives are acting goofy because one display is 1680x1050 and the other is 1920x1080, which is what my TV is that I'm connecting to.

Here's a good breakdown from the Arch Linux Wiki, it's the same process: https://wiki.archlinux.org/index.php/X11vnc

I'm going to assume that to get this work constantly one would have to constantly login via XBMCbuntu and have XBMC autostart. You could also probably have XBMC standalone running but connect to display :1 and have a separate instance of XBMC running that you could configure but I haven't tried that yet.
Reply
#5
ah, you mean the only difference was that you selected xbmcbuntu in the dm. Got you. I asked because I thought you had to supply it as a parameter...
Reply
#6
Nope, it was actually pretty easy to do, I just tried it on a whim when I was messing around with something else.
Reply
#7
I lied, it still displays a black screen when xbmc is running in the foreground :-(
Reply
#8
try xmdcp
Reply

Logout Mark Read Team Forum Stats Members Help
Connect to root display ( :0 ) via VNC0