ISTM that irexec startup could happen in at least two places, either through a user logging (or being logged) in or through an "STB" startup type method.
It may be that there is overlap between the STB startup and a user logging in, however unless a user logging in means an automatic launch of mythfrontend, maybe not. Back to the irexec start up... perhaps a generic script to start it and a few "launchpoints", guarded with "mode" (STB, user_login, etc.) conditionals is the way to go. For STB mode (the way I run my mythbuntu) the Power button on a remote should restart both the X server and mythfrontend as it's probably not entirely reliable to be able to just restart mythfrontend in the case of some kind of lock up. This probably contravenes what a logged in user would want the power button to do. So to summarize, for "STB Mode" I'd like to see (and in fact have) a script which starts X, applied nvidia settings and starts mythfrontend (and nothing else -- no window managers, login managers, etc.). This same script will stop mythfrontend, and X if called again. This makes it a good "toggle switch" for the UI. On system startup the script executes to have the UI operational on "boot". irexex is also started (which I hack the lirc initscript to add, but it could very well be it's own initscript) and should bind the "Power" key on a remote to the above "toggle" script. That's about it. That's how simple and "bare bones" an STB mode needs to be. Cheers, b. -- startup script does not start irexec https://bugs.launchpad.net/bugs/224208 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
