[mythtv-commits] Ticket #10209: Mythfrontend fails to find mysql.txt when the home directory path contains non-ASCII
MythTV
noreply at mythtv.org
Sat Dec 17 20:25:22 UTC 2011
#10209: Mythfrontend fails to find mysql.txt when the home directory path contains
non-ASCII
-------------------------------------------------+-------------------------
Reporter: Göran Uddeborg <goeran@…> | Owner:
Type: Bug Report - General | Status: new
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.24.1
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------------------+-------------------------
Comment (by mdean):
This is due to the line:
fstream fin(pszFile.toAscii(), ios::in);
which is used by the (old) Settings class to read the mysql.txt and
settings.txt files in Settings::ReadSettings().
There is no need to have multiple MythTV configuration files with
overlapping functionality. I plan to remove mysql.txt and leave only
config.xml (where config.xml allows specifying everything in mysql.txt and
more), and ideally when doing so will remove all of the old Settings
class. This will leave us with only one configuration file, config.xml,
and in so doing will remove the (extremely) old, ASCII-only, non-Qt, low-
level C++ code that's causing the failure you've noticed.
However, since config.xml provides the same information as mysql.txt,
there is no need for mysql.txt if you have a config.xml file (and provide
a <SecurityPin> value that matches your "Security PIN (required)" setting,
as specified in mythtv-setup). Therefore, your system can work with just
config.xml (I use only config.xml on my 0.24-fixes system). If you need
help getting it to work, please ask for help on the mythtv-users list.
Note that on 0.24-fixes and below, if you have no mysql.txt and you have
multiple independent MythTV systems (using different databases and
different master backends) on the same network--with multiple master
backends running at the same time--a bug will prevent MythTV from finding
the proper master backend automatically, so you would have to select the
proper backend on each mythfrontend restart. This has since been fixed in
unstable/development code (will be a part of 0.25).
Note, also, that for some reason, the Qt code creates a
.config/Trolltech.conf file in both the ASCII-/latin-1-ized version of the
HOME directory and in the UTF-8 version of the HOME directory; however,
the one in the proper HOME directory is lacking the SQL driver and image
format/image handler information (having only the text CODEC information--
seemingly as if it uses the ASCII-ized version of the HOME directory name
until it loads the text CODECs, which allow it to use the proper directory
name). Therefore, you may still need to have an ASCII-ized version of
your HOME directory specifically for .config/Trolltech.conf. This,
however, is an upstream bug (as we don't use Trolltech.conf directly--it's
only used in so far as it supports the Qt code that we use).
--
Ticket URL: <http://code.mythtv.org/trac/ticket/10209#comment:1>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list