[mythtv-users] remote ssh to run mythtv-setup ( ssh -X mythtv at server mythtv-setup ) hangs on exit

[Tom Dexter]

On Sun, Jul 15, 2018 at 2:45 PM, Tom Dexter <digitalaudiorock at gmail.com> wrote:
> On Sat, Jul 14, 2018 at 5:33 PM, Brent Bolin <brent.bolin at gmail.com> wrote:
>> Issue I've seen lately is it just hangs after changes are made on a headless
>> mythtv install
>>
>> Get the dialog box that says: If you added or altered channels please run
>> mythfilldatabase on the master backend to populate the database with guide
>> information
>>
>> At that point I need to open another screen and kill the mythtv-setup
>> process.  Thought it has something to do with systemd not enabled but
>> appears to be something more
>>
>> NAME="Ubuntu"
>> VERSION="16.04.4 LTS (Xenial Xerus)"
>> mythtv-backend-master                2:0.28.2+fixes
>>
>> sudo systemctl stop mythtv-backend.service (works fine)
>> Also edited /etc/sudoers
>> mythtv ALL=(ALL) NOPASSWD: ALL
>>
>> Input would be appreciated hate crashing all the time
>> Brent Bolin
>>
>
> That's interesting, as I ran into almost identical hard lockups using
> ssh -X -Y when trying to use programs that use imlib2, specifically
> after upgrading to a version that had apparently added support for X11
> shared memory file descriptors(??). See the details here:
>
> https://bugs.gentoo.org/660828
>
> The symptoms were identical, requiring a kill -9 on the process. My
> guess is that someone forgot that X might not even be running on that
> local system and is attempting to to something that can't possibly
> work with X via ssh. I don't see any sign that MythTV uses imlib2 in
> any way, though I can't be 100% sure. Possibly something else has a
> similar mistake.
>
> Tom

One thing you can check: If something somewhere is attempting that,
unless you have a very new version of x11-server, you'd probably see
lines in your Xorg.0.log file (on the *client* from which you're using
ssh) that may look something like this:

[1944940.082] Using O_TMPFILE

Like I said...it appears that X on the client side may be trying to
access something that's really on the server side.

A slight rant here: This gives me concern that developers may be
forgetting that X can and does do this, especially with the wayland
fanboys out there who seem to think this is an unnecessary feature
that nobody uses, making arguments against it as though we're all back
on 10base T networks or something. Don't get me started. I love X11
forwarding and use it all the time.

Tom