mythtv-core.25 00.25.2-Fixes-20120918 mythfrontend.app does not exit properly

[ted.rippert@…]

In both OSX 10.5.8 and 10.6.8, the standalone Myth Frontend App works properly when run but does not quit when exit, and must be stopped using force quit. A frontend started from the command line exits properly.

[mf2k (Frank Schima)]

In the future, please Cc the port maintainer(s).

[ctreleaven (Craig Treleaven)]

Sorry for the delay responding.

Thanks for the report. Interesting that you have this problem with 10.5 and 10.6--until now, I thought it primarily affected 10.7. I'm still unsure as the source of the issue. I've found that if you wait a few seconds, the Applescript launcher crashes (and offers a crash report). Is your experience different?

Obviously, the workaround is to start the frontend from the command line. I will continue to look for a better (shortcut) way to start the frontend.

[ted.rippert@…]

On both 10.5 and 10.6 the program just hangs no matter how long you wait. It has to be force quit.

What are the equivalent command line options for your app? Obviously the log path, but do you use other options?

[ctreleaven (Craig Treleaven)]

Assuming your PATH includes /opt/local/bin, the basic command to start the frontend is:

mythfrontend --logpath /opt/local/var/log/mythtv.25 --quiet

"--quiet" is optional; it just prevents the frontend from echoing all its logging to the console.

I've been playing around with Myth's new Airplay function. To enable it, you have to find the key file and save it to

/users/<user>/.mythtv/RAOPKey.rsa

Then add the environment variable that enables it:

export MYTHTV_AIRPLAY="1" mythfrontend --logpath /opt/local/var/log/mythtv.25 --quiet

See the wiki for more info, ​http://www.mythtv.org/wiki/AirTunes/AirPlay

[ted.rippert@…]

I haven't been able to find any errors in the log-file when the App is exited. However, when the command line exits, it always has the same error in the terminal output:

2012-11-03 15:01:25.772559 I  Waiting for threads to exit.
Error: Not all threads were shut down properly: 
Thread AppleRemote is still running

Actually, looking a bit further, the App does produce these errors, but they go to the console instead of the log-file. I don't know if the AppleRemote thread is causing the App to hang when it exits, but it is the last thing that is output on exit by both the App and the command line instance.

[ctreleaven (Craig Treleaven)]

The report about the AppleRemote thread happens under all OS versions. Seems to cause no harm. I believe OS X kills it when the app is shut down.

[pixilla (Bradley Giesbrecht)]

Ted: is this still an issue with mythtv-core.25 @0.25.3-Fixes-20130529?

[ted.rippert@…]

I haven't been using the Macports frontend for a while. I wrote my own simple bash script in an OSX wrapper to start mythfrontend, but I don't really use that much either as I've been using XBMC as a front end. I just played with the new Macports frontend, and it doesn't seem to be doing it anymore, although it was somewhat intermittent previously. I'll keep playing with it and let you know if I see the issue again.

[ctreleaven (Craig Treleaven)]

Port is now obsolete