[mythtv-users] Infinite "Please Wait" watching recordings

[Peter Bennett (cats22)]

I have two remote front ends. Both of them have displayed this problem
occasionally.
When selecting a recording to play and starting play, the screen
displays "Please Wait ..." for ever. At this point keyboard actions have
no effect. Killing the user that runs the front end and logging on again
does not resolve the problem. After restarting the front end the same
thing happens. Rebooting the front end Ubuntu system does resolve the
problem. I do not understand why rebooting works while killing the front
end does not.
In the front end log the following are the last messages displayed
before the hang.

2015-05-19 21:30:28.334431 I  TV: Creating TV object
2015-05-19 21:30:28.542888 N  Suspending idle timer
2015-05-19 21:30:28.571196 I  TV: Created TvPlayWindow.
2015-05-19 21:30:28.696754 I  TV: Attempting to change from None to
WatchingPreRecorded
g_dbus_connection_real_closed: Remote peer vanished with error:
Underlying GIOStream returned 0 bytes on an async read
(g-io-error-quark, 0). Exiting.

On the back end the following log entries appear
May 19 21:30:06 serenity mythbackend: mythbackend[2614]: I
ProcessRequest mainserver.cpp:1443 (HandleAnnounce) MainServer::ANN Playback
May 19 21:30:06 serenity mythbackend: mythbackend[2614]: I
ProcessRequest mainserver.cpp:1445 (HandleAnnounce) adding: panther as a
client (events: 0)
May 19 21:30:06 serenity mythbackend: mythbackend[2614]: I
ProcessRequest mainserver.cpp:1443 (HandleAnnounce) MainServer::ANN Monitor
May 19 21:30:06 serenity mythbackend: mythbackend[2614]: I
ProcessRequest mainserver.cpp:1445 (HandleAnnounce) adding: panther as a
client (events: 1)

Normally they would be followed by backend messages "adding: panther as
a remote file transfer" but those do not appear.

I think the "g_dbus_connection_real_closed" has something to do with it,
but I do not know what that means. That message seems to only appear in
the log after killing the front end. (looking at the front end log while
hung does not show this message). Possibly this error is caused by the
action of killing the front end.

Peter