<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div style="color: black;">
<p style="margin: 0 0 1em 0; color: black; font-family: sans-serif;">On 18 September 2017 1:01:15 pm Mark Perkins <perkins1724@hotmail.com> wrote:</p>
<p style="margin: 0 0 1em 0; color: black; font-family: sans-serif;">> On 18 September 2017 9:33:36 am Anthony Giggins <seven@seven.dorksville.net> wrote:<br>
><br>
>> Hi all,<br>
>><br>
>> Does anyone have a current working solution to run mythtv-setup on a<br>
>> headless backend? currently having nvidia display issues on backend<br>
>><br>
>> From <a href="https://www.mythtv.org/wiki/Backend_migration">https://www.mythtv.org/wiki/Backend_migration</a> it suggests<br>
>><br>
>> *Users with headless backends, type: ssh -l mythtv -Y <BackendHost> mythtv-setup<br>
>><br>
>><br>
>> however this causes errors<br>
>><br>
>> I've tried running from a frontend and via putty using Xming server from<br>
>> windows however I'm getting errors from both<br>
>><br>
>> mysql: [Warning] Using a password on the command line interface can be<br>
>> insecure.<br>
>> ERROR 1046 (3D000) at line 1: No database selected<br>
>> xprop: unable to open display ''<br>
>> status: Name "com.ubuntu.Upstart" does not exist<br>
>> xterm: Xt error: Can't open display:<br>
>> xterm: DISPLAY is not set<br>
>> Failed to connect to Mir: Failed to connect to server socket: No such file<br>
>> or directory<br>
>> Unable to init server: Could not connect: Connection refused<br>
>><br>
>> (zenity:27074): Gtk-WARNING **: cannot open display:<br>
>> Failed to connect to Mir: Failed to connect to server socket: No such file<br>
>> or directory<br>
>> Unable to init server: Could not connect: Connection refused<br>
>><br>
>> (zenity:27079): Gtk-WARNING **: cannot open display:<br>
>><br>
>> I've tried exporting DISPLAY to both 0.0 and 127.0.0.1:0 (which should work<br>
>> via putty) but nothing is working<br>
>><br>
>> Cheers,<br>
>><br>
>> Anthony<br>
>><br>
>><br>
>><br>
>> ----------<br>
><br>
> I often use putty and xming from a Windows machine to a headless BE. I had to enable X11 forwarding in putty at the start of the session. I also had to add some IP address details to a putty config file somewhere so that it would accept connections. I will
check later when I am home what the details were.<br>
><br>
><br>
><br>
</p>
<p style="margin: 0 0 1em 0; color: black;"> </p>
<p style="margin: 0 0 1em 0; color: black;">I think this is what I originally needed to do, although I must admit I currently don't see these changes in my x0.hosts file so not sure if it is now no longer needed or I modified my setup in some other way to avoid
the requirement.</p>
<p style="margin: 0 0 1em 0; color: black;"><a href="http://theunixtips.com/xming-client-4-rejected-from-ip/">http://theunixtips.com/xming-client-4-rejected-from-ip/</a></p>
<p style="margin: 0 0 1em 0; color: black;">However if you are having the same problems with both xming and SSH from a separate nix machine then the issue is likely not this.
</p>
<p style="margin: 0 0 1em 0; color: black;"> <br>
<br>
</p>
</div>
</body>
</html>