← Back to team overview

mythbuntu-bugs team mailing list archive

[Bug 716564] [NEW] MythFrontend only shows theme background

 

Public bug reported:

Binary package hint: mythtv

One of my remote MythFrontends only loads to a grey screen (the theme
background). Every now and then it does load, but then viewing
recordings or LiveTV doesn't show any image and hangs for a while. Both
the backend and the frontend run Ubuntu 10.04.2 LTS, with mythtv
0.23.0+fixes24158-0ubuntu2.

The local frontend on the backend works just fine, as well as two
Mac/Intel frontends I've tried. The problematic frontend used to work
fine.

I will attach a log of a testrun of MythFrontend on the problematic
system, run using `-v most`.

Any steps I can take to troubleshoot this problem will be appreciated. I
have already updated both systems to the latest versions in APT. Also
tried if the MySQL errors were caused by MySQL 5.0, so I updated to 5.1.

** Affects: mythtv (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  MythFrontend only shows theme background

Status in “mythtv” package in Ubuntu:
  New

Bug description:
  Binary package hint: mythtv

  One of my remote MythFrontends only loads to a grey screen (the theme
  background). Every now and then it does load, but then viewing
  recordings or LiveTV doesn't show any image and hangs for a while.
  Both the backend and the frontend run Ubuntu 10.04.2 LTS, with mythtv
  0.23.0+fixes24158-0ubuntu2.

  The local frontend on the backend works just fine, as well as two
  Mac/Intel frontends I've tried. The problematic frontend used to work
  fine.

  I will attach a log of a testrun of MythFrontend on the problematic
  system, run using `-v most`.

  Any steps I can take to troubleshoot this problem will be appreciated.
  I have already updated both systems to the latest versions in APT.
  Also tried if the MySQL errors were caused by MySQL 5.0, so I updated
  to 5.1.





Follow ups

References