mythbuntu-bugs team mailing list archive

[Roger James <1635685@xxxxxxxxxxxxxxxxxx>]

I seem to be having a dialogue with myself here. However, this bug seems
very time critical. If I turn on too much verbose debugging, it goes
away. If I run it via gdb, it goes away. If I run it with strace, it
goes away. I moved the shuttle box it was running on, up to my
workbench, it went away. The only difference in the last case I could
think of was on my workbench it was connected to the same switch the
back end was connected to, when it is sat next to the TV it goes through
another mini switch first.

I am baffled by this and it very hard to debug. Any ideas anyone.

Roger

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1635685

Title:
  mythfrontend exits with status one before gui appears

Status in Mythbuntu:
  New

Bug description:
  Using mythbuntu 16.04 with mythfrontend configured to run via
  .config/autostart when the gui desktop boots. Randomly mythfrontend
  exits before any gui is displayed. Because the shell exit status is
  one (process exit 0x100) the mythfrontend wrapper script does not try
  to restart. This appears to be some kind of race condition in the
  start up environment. Putting a 60 second sleep in the wrapper script
  appears to cure it.

  It appears that mythfrontend main.cpp is getting as far as launching
  the housekeeper but is exiting before the gui is drawn by the message
  loop.

  Has anyone else seen this?

  Roger

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1635685/+subscriptions