mythbox:~$ sudo vim /usr/local/bin/restartmyth.sh
## Automatically restart mythfrontend if it fails.
## Loop the call of mythfrontend.
while [ /bin/true ]
mythfrontend -v playback >> /tmp/mythfrontend.log
mythbox:~$ sudo chmod 755 /usr/local/bin/restartmyth.sh
First enable Automatic login from the gnome Settings panel.
Schedule the script to start after login (using gnome)
mythbox:~$ vim .config/autostart/restartmythtv.desktop
Comment=Restart mythtfrontend when it crashes
Restart the computer
Note: this blog was previously written for XBOX media centre (XBMC). It has been replaced by Kodi since a long time. Please read kodi instead of xbmc below.
In 2010 I wrote:
I recently tried XBMC on one of my mytfrontends. I must say, I was impressed by the user interface.
To run xbmc besides mythfrontend I had to do some tweaking to this mythbuntu frontend. To install, first add these lines to /etc/apt/sources.list
deb http://ppa.launchpad.net/team-xbmc/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu jaunty main
Kodi can nowadays be found in the stable repository of Debian.
# vim /usr/share/mythtv/themes/MythCenter-wide/osd.xml
<fontdef name=”medium” face=”Droid Sans”>
The progress bar will show up on top of the screen. This will keep the subtitles visible when pausing and unpausing recordings.
Using the official mythtv wiki I managed to get my ATI remote working without lirc on one of my boxes running Ubuntu 11.10. Unfortunately the trick, for some reason, didn’t work on 12.04.
I found a solution on the mythtvtalk forum, using evdev.conf file instead of a statement in xorg.conf
We need to install a patched evdev-driver that will understand keys greater than 255 by giving access to the “event_key_remap option”.
It happened me several times:
During updating mythtv-database package the root password is used. The postinstall script will use mysql password stored in the debconf db, but if in the meantime the mysql rootpassword has changed, the update will break.
To reveal the “old” password, this little script might help:
Today I decided to test a brandnew bluetooth transmitter and receiver which were delivered to me shortly. After some googling I was convinced it should not take to long to configure this.
This transmitter can be connected with the 3.5 jack audio plug to a soundcard audio-out interface.
It is also possible to connect the device to a computer with a USB cable which comes within the package for this purpose. Another purpose of the USB connection is delivering power to the device.
I decided to stick with option 2.
I had some difficulties to enable the LCD on this HTPC. Just for reference a couple of
At first I followed the instructions as in: http://www.mythtv.org/wiki/LCDproc
The fresh build imon driver didn’t work for me.
Then I stumbled upon: http://codeka.com/index.php, suggesting me patching the current lcdproc-0.5.2 package to use the imonlcd driver instead.
Update: in the meantime fully documented here. In short in my case:
After upgrading my Debian backend to mythtv 0.23 I had to upgrade one of my clients (running Ubuntu 9.04, Jaunty) to Karmic 9.10 also. Some simple steps.
Upgrading to 9.10:
sudo apt-get install update-manager-core
Sometimes I use VNC to connect to mythboxes, starting mythfrontend from a xterminal to adjust some settings easily. I discovered that, because I set up one of them to use opengl (selected in settings), to draw the screens, the menu’s weren’t visible anymore, causing a lot of message like this:
QGLContext::makeCurrent(): Cannot make invalid context current.
Switching back to “qt” solves this. Another option is running mythfrontend with a commandline option. This overrides the opengl setting for a session:
mythfrontend -O ThemePainter=qt
For some time I’m running mythbuntu on one of my mythtv frontends. This because I could not get my ATI wonder to work with lirc in Debian Lenny. By using a mythbuntu livecd I discovered that this remote just worked. First I decided to copy the correct lirc config files to my Debian box, but that did not solve the problem for some reason. Because I did not have the time to troubleshoot I installed mythbuntu on the harddisk. This mythbuntu version is based on the ubuntu Jaunty distro.