More > JRiver Media Center 20 for Linux

MC without a GUI

<< < (7/10) > >>

bob:
I think it makes sense that it changed with the gnutls switch. I see that on 64 bit ubuntu 14.10 but it doesn't seem to hurt anything as far as I've seen so far.

InflatableMouse:
Sounds good. Thanks Bob!

astromo:
I'm after some help please. Running Ubuntu 14.04 x64.

First I was stuck with trying to remote in via ssh. I glossed over this bit:

--- Quote from: bob on October 17, 2013, 05:28:04 pm ---What you can do to get it running from the command line without a gui is this:
Install and run once remotely via ssh and X forwarding to get the configuration setup.

--- End quote ---
Then I twigged that I needed to install SSH (you could misread this as "install MC" by the way), so I did a:

--- Code: ---sudo apt-get install ssh
--- End code ---
and then remoted in but got a no-can-do along the lines of errors to do with p11-kit + core dump / seg fault. So, I looked around and gave the info here a bash:
Switching to gnutls from openssl in the next build

Now when I remote in, the p11-kit errors have disappeared but I'm still getting core dump (segmentation fault) when I run the command "mediacenter20" from the remote terminal.

Thoughts?

bob:

--- Quote from: astromo on November 07, 2014, 05:08:41 pm ---I'm after some help please. Running Ubuntu 14.04 x64.

First I was stuck with trying to remote in via ssh. I glossed over this bit:Then I twigged that I needed to install SSH (you could misread this as "install MC" by the way), so I did a:

--- Code: ---sudo apt-get install ssh
--- End code ---
and then remoted in but got a no-can-do along the lines of errors to do with p11-kit + core dump / seg fault. So, I looked around and gave the info here a bash:
Switching to gnutls from openssl in the next build

Now when I remote in, the p11-kit errors have disappeared but I'm still getting core dump (segmentation fault) when I run the command "mediacenter20" from the remote terminal.

Thoughts?

--- End quote ---
You probably don't have x11 forwarding setup.
Try this on the machine that you ssh'd into:
sudo apt-get install xterm
then after it finishes, just type xterm and hit enter. I bet it won't run.
in debian, the config file is in /etc/ssh/sshd_config
enable X11 forwarding
restart: /etc/init.d/ssh restart
logout and ssh back in again.
retry xterm
if it works you should be set, if not logout and ssh back in again using the -X flag arg to ssh, ie
ssh -X someremotemachine.com

mwillems:
And if the -X argument doesn't work, you may need to pass the -Y argument instead (I did, as I recall).

FYI, I had pretty poor luck doing remote admin of an MC instance via normal X-forwarding; I had much better luck using a VNC client over ssh as described in step-by-step detail here: http://yabb.jriver.com/interact/index.php?topic=91227.0

I especially recommend it if you need to use the MC GUI on the server instance (I found it very hard to use the GUI w/ X-forwarding due to lag).  The VNC over SSH method has the added advantage of making your linux MC instance easier to log into from non-linux boxes and android devices.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version