[mythtv-users] BE3 - Issues with installation and database

Stephen Worthington stephen_agent at jsw.gen.nz
Tue Jun 4 05:42:47 UTC 2019


On Mon, 3 Jun 2019 11:01:07 -0500, you wrote:

>
>Hi Stephen!
>
>
><my font errors>
>
>When I installed that for testing, they turned up here:
>
>//usr/local/mythtv-testing/share/mythtv/fonts//
>
>    That directory does not exist. ...Well, I have to go down to
>    /usr/local/.

I would not have expected it to exist on your system.  It is where I
put a second copy of MythTV when I am testing new versions prior to
using them in real life.

>So I have put them on my web server:
>
>http://www.jsw.gen.nz/mythtv/mythtv-fonts.tar.bz2
>
>You can install them by running this:
>
>sudo su
>cd /usr/share/mythtv/fonts
>wget -chttp://www.jsw.gen.nz/mythtv/mythtv-fonts.tar.bz2
>rm -v Droid*
>tar xvf mythtv-fonts.tar.bz2
>rm mythtv-fonts.tar.bz2
>exit
>
>If you want to keep the fonts in case there are problems
>
>    Hahaha: “if” and “in case”!! <G> Actually I do not expect any
>    problem after we get this figured out but backups are good!
>
>
>    Well this is interesting: prior to step 2 I did an ls to make
>    certain that directory was present; listed:
>
>
>    root at Backend-3:/home/barry# ls /usr/share/mythtv/fonts
>
>    DroidSans-Bold.ttf FreeSansBold.ttf
>
>    DroidSansMono.ttf FreeSans.ttf
>
>    DroidSans.ttf Purisa.ttf
>
>    DroidSerif-BoldItalic.ttf texgyrechorus-mediumitalic.otf
>
>    DroidSerif-Bold.ttf 'Tiresias Infofont Bold.ttf'
>
>    DroidSerif-Italic.ttf 'Tiresias Infofont Italic.ttf'
>
>    DroidSerif-Regular.ttf 'Tiresias Infofont.ttf'
>
>    FreeMono.ttf
>
>    root at Backend-3:/home/barry#

Not present - those "files" are just links to a place where the files
are not actually present - the same links you saw before.  They should
be coloured red if you have colouring enabled, showing that they are
bad links.  My command "rm -v Droid*" in the install instructions
above should have deleted all the bad links.

>
>    So present but ?? (Just my usual curiosity.)
>
>
>    After ‘exit’:
>
>
>    barry at Backend-3:~$ ls /usr/share/mythtv/fonts
>
>    DroidSans-Bold.ttf FreeSerifBoldItalic.ttf
>
>    DroidSansMono.ttf FreeSerifBold.ttf
>
>    DroidSans.ttf FreeSerifItalic.ttf
>
>    DroidSerif-BoldItalic.ttf FreeSerif.ttf
>
>    DroidSerif-Bold.ttf Purisa.ttf
>
>    DroidSerif-Italic.ttf README-droid.txt
>
>    DroidSerif-Regular.ttf README-freefont-20120503.txt
>
>    FreeMonoBoldOblique.ttf README-purisa.txt
>
>    FreeMonoBold.ttf README-TeX-Gyre-Chorus.txt
>
>    FreeMonoOblique.ttf texgyrechorus-mediumitalic.otf
>
>    FreeMono.ttf tiresias_gpl3.txt
>
>    FreeSansBoldOblique.ttf 'Tiresias Infofont Bold.ttf'
>
>    FreeSansBold.ttf 'Tiresias Infofont Italic.ttf'
>
>    FreeSansOblique.ttf 'Tiresias Infofont.ttf'
>
>    FreeSans.ttf
>
>    barry at Backend-3:~$
>
>
>    So several missing originally for some reason.

If faginbagin is right, the bug report he gave us a URL for says it is
a packaging issue that has happened in v30's Ubuntu packages.  The
packages do not install the fonts.  I know from my test builds of v30
that the fonts were in v30 when I downloaded and built it from the
source code - that was how I had them in my
/root/projects/mythtv-master/mythtv/mythtv/themes/fonts/ directory.

>    Did ‘mythfrontend’ (via Terminal, half-habit, half easier to get out
>    of if a problem), the text is a little small but does look
>    cleaner/nicer and no ugly overlapping. Realize some of that is
>    Theme-dependent but they (should) all draw from the same font
>    library, so thanks for fixing that error!

Yes, using the MythCentre-wide theme, everything just does not feel
right until those fonts are installed.

[snip]
>    OK - - copy in the ‘short form” config.xml from BE3 to the RPI and
>    reboot.
>
>    Well poo: that should teach me to question an expert! Now get the
>    ‘preview picture’ and the actual video file plays. Slow and jerky
>    and no sound but haven’t configured those yet. Also using (5 GHz)
>    WiFi which may or may not be a sufficient quick transfer avenue
>    compared to Ethernet. (Sort of doing two experiments in one: where
>    I’d like to use this RPi eventually installing a wire not overly easy.)
>
>
>    Will post this so far, see about the audio and video and the other
>    replies.
>
>
>    THANK YOU!!
>
>    Barry

Yes, copying the backend's config.xml and just changing the IP address
is the best way to make sure it will work.  However, it does rely on
each frontend box having a different hostname.  That is usually the
case, as the install process for every version of Linux I know of gets
you to select a hostname for the box.  But just to make sure, you can
run this command on the RPi:

hostname

to see what the hostname is set to.  If is vitally important that all
PCs on a network have different hostname settings.

When you set a <LocalHostName> value in a config.xml file, that value
gets used to look up the frontend settings in the backend's database,
instead of using the actual hostname of the PC.  That is a specialised
use of MythTV - you can make multiple different frontends use the same
settings.  But it can also cause problems.  So I am surprised that the
RPi version of MythTV seems to either set the <LocalHostName> value,
or tell you to do it.  It is usually a bad idea unless you know
exactly what you are doing.


More information about the mythtv-users mailing list