Even if I'm not affected by this exact bug the lack of proper environment settings (like $HOME) are making my mythfilldatabase fail:
...
2010-04-09 13:16:53.430 Using runtime prefix = /usr
2010-04-09 13:16:53.446 Using configuration directory = /.mythtv
2010-04-09 13:16:53.446 Unable to read configuration file mysql.txt
2010-04-09 13:16:53.446 Empty LocalHostName.
...
I believe this comes from how the mythbackend process is launched in /etc/init/mythtv-backend.conf which executes the process without setting the environment. This said I was able to resolve the problem by launching mythbackend after a switch user to mythtv with "--login" option.
The modified version of /etc/init/mythtv-backend.conf is attached.
Even if I'm not affected by this exact bug the lack of proper environment settings (like $HOME) are making my mythfilldatabase fail:
...
2010-04-09 13:16:53.430 Using runtime prefix = /usr
2010-04-09 13:16:53.446 Using configuration directory = /.mythtv
2010-04-09 13:16:53.446 Unable to read configuration file mysql.txt
2010-04-09 13:16:53.446 Empty LocalHostName.
...
I believe this comes from how the mythbackend process is launched in /etc/init/ mythtv- backend. conf which executes the process without setting the environment. This said I was able to resolve the problem by launching mythbackend after a switch user to mythtv with "--login" option.
The modified version of /etc/init/ mythtv- backend. conf is attached.