Remote setup of kodi

kamaradclimber · 2015-11-22 13:58:05

Hello,

I am trying to setup kodi remotely. kodi runs on a raspberrypi connected to a projector.

kodi is launched via

/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7

and works correctly (I have launched the projector to confirm).

I have tried to use vnc (on LAN) to connect to the existing X session remotely but I can only see a black screen (as many others).

My question is: what solutions do I have to connect remotely in order to configure kodi ? Should I stick to vnc or try another solution?t

EDIT:
- The reason I am launching kodi directly via xinit is to save resource on the raspberry which will be used only to launch kodi. I'd like to avoid using a DM if possible
- This post could have been written in the arch raspberry forum but I think the issue is more related to X config and/or vnc
- I have tried with x11vnc and tightvnc for the server part with exactly the same behavior.
- command used to laucn vnc is the most simple one:

x11vnc

EDIT2: if relevant here is the output of x11vnc

###############################################################
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@ @#
#@ ** WARNING ** WARNING ** WARNING ** WARNING ** @#
#@ @#
#@ YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!! @#
#@ @#
#@ This means anyone with network access to this computer @#
#@ may be able to view and control your desktop. @#
#@ @#
#@ >>> If you did not mean to do this Press CTRL-C now!! <<< @#
#@ @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@ @#
#@ You can create an x11vnc password file by running: @#
#@ @#
#@ x11vnc -storepasswd password /path/to/passfile @#
#@ or x11vnc -storepasswd /path/to/passfile @#
#@ or x11vnc -storepasswd @#
#@ @#
#@ (the last one will use ~/.vnc/passwd) @#
#@ @#
#@ and then starting x11vnc via: @#
#@ @#
#@ x11vnc -rfbauth /path/to/passfile @#
#@ @#
#@ an existing ~/.vnc/passwd file from another VNC @#
#@ application will work fine too. @#
#@ @#
#@ You can also use the -passwdfile or -passwd options. @#
#@ (note -passwd is unsafe if local users are not trusted) @#
#@ @#
#@ Make sure any -rfbauth and -passwdfile password files @#
#@ cannot be read by untrusted users. @#
#@ @#
#@ Use x11vnc -usepw to automatically use your @#
#@ ~/.vnc/passwd or ~/.vnc/passwdfile password files. @#
#@ (and prompt you to create ~/.vnc/passwd if neither @#
#@ file exists.) Under -usepw, x11vnc will exit if it @#
#@ cannot find a password to use. @#
#@ @#
#@ @#
#@ Even with a password, the subsequent VNC traffic is @#
#@ sent in the clear. Consider tunnelling via ssh(1): @#
#@ @#
#@ http://www.karlrunge.com/x11vnc/#tunnelling @#
#@ @#
#@ Or using the x11vnc SSL options: -ssl and -stunnel @#
#@ @#
#@ Please Read the documention for more info about @#
#@ passwords, security, and encryption. @#
#@ @#
#@ http://www.karlrunge.com/x11vnc/faq.html#faq-passwd @#
#@ @#
#@ To disable this warning use the -nopw option, or put @#
#@ 'nopw' on a line in your ~/.x11vncrc file. @#
#@ @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
###############################################################
22/11/2015 14:11:57 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 5296
22/11/2015 14:11:57 XOpenDisplay("") failed.
22/11/2015 14:11:57 Trying again with XAUTHLOCALHOSTNAME=localhost ...
22/11/2015 14:11:57
22/11/2015 14:11:57 *** XOpenDisplay failed. No -display or DISPLAY.
22/11/2015 14:11:57 *** Trying ":0" in 4 seconds. Press Ctrl-C to abort.
22/11/2015 14:11:57 *** 1 2 3 4
22/11/2015 14:12:01 *** XOpenDisplay of ":0" successful.
22/11/2015 14:12:01
22/11/2015 14:12:01 Using X display :0
22/11/2015 14:12:01 rootwin: 0x1aa reswin: 0x800001 dpy: 0x1a9cfc8
22/11/2015 14:12:01
22/11/2015 14:12:01 ------------------ USEFUL INFORMATION ------------------
22/11/2015 14:12:01 X DAMAGE available on display, using it for polling hints.
22/11/2015 14:12:01 To disable this behavior use: '-noxdamage'
22/11/2015 14:12:01
22/11/2015 14:12:01 Most compositing window managers like 'compiz' or 'beryl'
22/11/2015 14:12:01 cause X DAMAGE to fail, and so you may not see any screen
22/11/2015 14:12:01 updates via VNC. Either disable 'compiz' (recommended) or
22/11/2015 14:12:01 supply the x11vnc '-noxdamage' command line option.
22/11/2015 14:12:01
22/11/2015 14:12:01 Wireframing: -wireframe mode is in effect for window moves.
22/11/2015 14:12:01 If this yields undesired behavior (poor response, painting
22/11/2015 14:12:01 errors, etc) it may be disabled:
22/11/2015 14:12:01 - use '-nowf' to disable wireframing completely.
22/11/2015 14:12:01 - use '-nowcr' to disable the Copy Rectangle after the
22/11/2015 14:12:01 moved window is released in the new position.
22/11/2015 14:12:01 Also see the -help entry for tuning parameters.
22/11/2015 14:12:01 You can press 3 Alt_L's (Left "Alt" key) in a row to
22/11/2015 14:12:01 repaint the screen, also see the -fixscreen option for
22/11/2015 14:12:01 periodic repaints.
22/11/2015 14:12:01
22/11/2015 14:12:01 XFIXES available on display, resetting cursor mode
22/11/2015 14:12:01 to: '-cursor most'.
22/11/2015 14:12:01 to disable this behavior use: '-cursor arrow'
22/11/2015 14:12:01 or '-noxfixes'.
22/11/2015 14:12:01 using XFIXES for cursor drawing.
22/11/2015 14:12:01 GrabServer control via XTEST.
22/11/2015 14:12:01
22/11/2015 14:12:01 Scroll Detection: -scrollcopyrect mode is in effect to
22/11/2015 14:12:01 use RECORD extension to try to detect scrolling windows
22/11/2015 14:12:01 (induced by either user keystroke or mouse input).
22/11/2015 14:12:01 If this yields undesired behavior (poor response, painting
22/11/2015 14:12:01 errors, etc) it may be disabled via: '-noscr'
22/11/2015 14:12:01 Also see the -help entry for tuning parameters.
22/11/2015 14:12:01 You can press 3 Alt_L's (Left "Alt" key) in a row to
22/11/2015 14:12:01 repaint the screen, also see the -fixscreen option for
22/11/2015 14:12:01 periodic repaints.
22/11/2015 14:12:01
22/11/2015 14:12:01 XKEYBOARD: number of keysyms per keycode 7 is greater
22/11/2015 14:12:01 than 4 and 51 keysyms are mapped above 4.
22/11/2015 14:12:01 Automatically switching to -xkb mode.
22/11/2015 14:12:01 If this makes the key mapping worse you can
22/11/2015 14:12:01 disable it with the "-noxkb" option.
22/11/2015 14:12:01 Also, remember "-remap DEAD" for accenting characters.
22/11/2015 14:12:01
22/11/2015 14:12:01 X FBPM extension not supported.
22/11/2015 14:12:01 X display is capable of DPMS.
22/11/2015 14:12:01 --------------------------------------------------------
22/11/2015 14:12:01
22/11/2015 14:12:01 Default visual ID: 0x21
22/11/2015 14:12:01 Read initial data from X display into framebuffer.
22/11/2015 14:12:01 initialize_screen: fb_depth/fb_bpp/fb_Bpl 16/16/2560
22/11/2015 14:12:01
22/11/2015 14:12:01 X display :0 is 16bpp depth=16 true color
22/11/2015 14:12:01
22/11/2015 14:12:01 Autoprobing TCP port
22/11/2015 14:12:01 Autoprobing selected port 5900
22/11/2015 14:12:01 Listening also on IPv6 port 5900 (socket 10)
22/11/2015 14:12:01
22/11/2015 14:12:01 Xinerama is present and active (e.g. multi-head).
22/11/2015 14:12:01 Xinerama: number of sub-screens: 1
22/11/2015 14:12:01 Xinerama: no blackouts needed (only one sub-screen)
22/11/2015 14:12:01
22/11/2015 14:12:01 fb read rate: 147 MB/sec
22/11/2015 14:12:01 fast read: reset -wait ms to: 10
22/11/2015 14:12:01 fast read: reset -defer ms to: 10
22/11/2015 14:12:01 The X server says there are 10 mouse buttons.
22/11/2015 14:12:01 screen setup finished.
22/11/2015 14:12:01
22/11/2015 14:12:01 WARNING: You are running x11vnc WITHOUT a password. See
22/11/2015 14:12:01 WARNING: the warning message printed above for more info.
22/11/2015 14:12:01
The VNC desktop is: alarmpi:0
PORT=5900
******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?
The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval. It should work with any VNC viewer. Try it by running:
x11vnc -ncache 10 ...
One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.htm … nt-caching
22/11/2015 14:12:12 Got connection from client 192.168.0.15
22/11/2015 14:12:12 other clients:
22/11/2015 14:12:12 Disabled X server key autorepeat.
22/11/2015 14:12:12 to force back on run: 'xset r on' (3 times)
22/11/2015 14:12:12 incr accepted_client=1 for 192.168.0.15:33464 sock=11
22/11/2015 14:12:12 Client Protocol Version 3.8
22/11/2015 14:12:12 Protocol version sent 3.8, using 3.8
22/11/2015 14:12:13 rfbProcessClientSecurityType: executing handler for type 1
22/11/2015 14:12:13 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
22/11/2015 14:12:13 Pixel format for client 192.168.0.15:
22/11/2015 14:12:13 32 bpp, depth 24, little endian
22/11/2015 14:12:13 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
22/11/2015 14:12:13 Using compression level 1 for client 192.168.0.15
22/11/2015 14:12:13 Using image quality level 6 for client 192.168.0.15
22/11/2015 14:12:13 Enabling X-style cursor updates for client 192.168.0.15
22/11/2015 14:12:13 Enabling full-color cursor updates for client 192.168.0.15
22/11/2015 14:12:13 Enabling cursor position updates for client 192.168.0.15
22/11/2015 14:12:13 Enabling LastRect protocol extension for client 192.168.0.15
22/11/2015 14:12:13 Using tight encoding for client 192.168.0.15
22/11/2015 14:12:13 client useCopyRect: 192.168.0.15 -1
22/11/2015 14:12:13 client_set_net: 192.168.0.15 0.0224
22/11/2015 14:12:13 created xdamage object: 0x80002c
22/11/2015 14:12:15 client_count: 0
22/11/2015 14:12:15 Restored X server key autorepeat to: 1
22/11/2015 14:12:15 viewer exited.
22/11/2015 14:12:15 deleted 40 tile_row polling images.

Last edited by kamaradclimber (2015-11-22 14:13:40)

Malkymder · 2015-11-22 19:37:21

I sometimes use nomachine nx to access remote machines that have kodi on and don't have real issues ... mind you those are PC's, have not tried on a rasp ... i use kodi remote app on android for those.

graysky · 2015-11-22 19:39:59

I do not believe you can use vnc with rpi. As you pointed out, the lightest way to use kodi on that hardware is with the included kodi.service.

Last edited by graysky (2015-11-22 19:40:24)

kamaradclimber · 2015-11-22 20:13:57

Thanks both for your answers.

@Malkymder, nomachine does not install cleanly on raspberry. I also use the remote app to pilot kodi when watching a movie but it only act as a remote not as a screen replacement, as far as I know.

@graysky, can you give me some links explaining why vnc cannot be used on raspberry ? I'd like to be convinced before I stop following this lead.
Regarding the kodi.service, it does not start X.

Arch Linux

#1 2015-11-22 13:58:05

Remote setup of kodi

#2 2015-11-22 19:37:21

Re: Remote setup of kodi

#3 2015-11-22 19:39:59

Re: Remote setup of kodi

#4 2015-11-22 20:13:57

Re: Remote setup of kodi

Board footer