You might be running into that same xrandr issue above.
Otherwise if you can give us enough detail to try to duplicate that here we'll look at it.
We have not observed that behavior with a real display or the dummy X server and X forwarding.
The intent is that getting MC running can be done entirely by the headless RPi during boot, running with a virtual frame buffer. Then, if access to the screen by a client is needed for configuration, etc., that can occur without any action on the RPi, just on the client.
The RANDR problem causes immediate MC22 crash on startup when running with tightvncserver with the RANDR extension missing message as others have reported. Running with vnc4server causes an immediate crash but without the RANDR message. Running with the current default Raspbian RealVNC server seems to work on the RPi side, but is not compatible with MacOS' screen sharing client. Thus the attempt to use Xvfb and x11vnc. With this combination, MC22 starts and runs fine, at least overnight, without JRemote communicating with it, and on the shared screen's desktop I can resize the MC22 window without any issue. Desktop performance is not great, but not terrible either.
Here's more detail on my setup. Let me know if you would like something more.
RPi 3 running Raspbian Jessie fully updated as of 1/14/17. MC22 Linux/Debian ARM build 22.0.63, installed following instruction at
https://yabb.jriver.com/interact/index.php?topic=106027.0 up to (and including) the section "Installing MC", i.e. modifications to /boot/config.txt.
My notes on how to set it up once installed are:
On the RPi, one time:
* Set x11vnc password (required by Mac’s Screen Sharing) using x11vnc -storepasswd
On the RPi, each time it boots:
* Check that no leftover x11vnc or Xvfb are running
* Start xvfb: Xvfb :1 -screen 0 1280x768x24 &
* Start an X window manager: DISPLAY=:1 lxsession &
* Start MediaCenter: DISPLAY=:1 mediacenter22 /MediaServer &
On the MacOS client, if want to attach to the MediaCenter display:
* ssh -l pi -L 59000:localhost:5900 <rpi3-hostname> 'x11vnc -localhost -display :1 -forever -usepw -ultrafilexfer’
* Confirm that x11vnc is using port 5900
* Use Finder’s Connect To Server… (cmd-K) and type in vnc://localhost:59000. Password is the one given to x11vnc -storepasswd.
* In this case, the local (MacOS) port 59000 is tunneled to the RPi’s port 5900. All the RPi port numbers and screen numbers have to match (with offset of 5900).
Now, start JRemote (3.23, iOS 10.2) and browse artists or albums. When album art is missing on JRemote, it appears to produce a crash of MC22 pretty much every time, or at least a large fraction of the time. The x11vnc options are verbatim from one of the references I found along the way, and I can't find it at the moment. I'll keep looking in case it's significant.