[mythtv-users] How can I trace a problem with the theme downloader

Paul Gardiner lists at glidos.net
Wed Jan 29 13:49:14 UTC 2014


On 29/01/2014 03:19, Michael T. Dean wrote:
> On 01/28/2014 09:12 AM, Paul Gardiner wrote:
>> On 28/01/2014 14:04, Michael T. Dean wrote:
>>> On 01/28/2014 08:52 AM, Paul Gardiner wrote:
>>>> I've been experimenting with a system called kiwi to build a new
>>>> image for my diskless frontend. It's mostly working - perhaps all
>>>> except the theme downloader. When I enter it, the initial scan
>>>> for updates returns immediately and I see just a list of three,
>>>> which I assume are held locally. The network is fine, as far as
>>>> I know. I can ping various things and the urls are resolved.
>>>> There seems to be no relevant warnings in the frontend log. I'm
>>>> wondering how I can trace the failure. I could easily have a
>>>> relied-upon package missing, but I'm not sure how I'd go about
>>>> finding out. First step, if possible - it would be nice to get
>>>> an error report from somewhere.
>>>
>>> The Theme Downloader relies on version information.  What's the
>>> output of:
>>>
>>> mythbackend --version
>>
>> Thanks for the help Mike. Here's the output:
>>
>>
>> Please attach all output as a file in bug reports.
>> MythTV Version : 317d5b7
>> MythTV Branch : tag: v0.27
>> Network Protocol : 77
>> Library API : 0.27.20131221-1
>> QT Version : 4.8.5
>> Options compiled in:
>>  linux release use_hidesyms using_alsa using_jack using_oss
>> using_pulse using_pulseoutput using_backend using_bindings_perl
>> using_bindings_python using_bindings_php using_dvb using_firewire
>> using_frontend using_hdhomerun using_ceton using_hdpvr using_ivtv
>> using_joystick_menu using_libcrypto using_libdns_sd using_libfftw3
>> using_libxml2 using_libudf using_lirc using_mheg using_opengl
>> using_opengl_video using_qtwebkit using_qtscript using_qtdbus
>> using_taglib using_v4l2 using_x11 using_xrandr using_xv
>> using_mythlogserver using_bindings_perl using_bindings_python
>> using_bindings_php using_mythtranscode using_opengl using_vaapi
>> using_vdpau using_ffmpeg_threads using_mheg using_libass using_libxml2
>> using_libudf
>
> I think that should work.  Try running mythfrontend with -v file,gui
> --loglevel debug

Mysterious! Firstly, because the themes have always refreshed
automatically, I hadn't realised that there was a menu option to
do it. That worked. And then strangely, it worked automatically
as it did before thereafter, that being particulary strange because
this is a diskless frontend using overlayfs (for which I've yet to
create a persistent version of .mythtv), so it goes back to to
its vanilla state on each reboot.

Before this I didn't find anything particularly odd in the logs. Here
they are (just in case you are interested - which I'd assume not, but
just in case): http://pastebin.com/h3WhbwPn

These are the only suspicious lines AFAICT:
2014-01-29 10:59:12.625289 I [2339/2339] CoreContext 
xmlparsebase.cpp:685 (LoadWindowFromXML) - XMLParseBase: Loading window 
themechooser from /usr/share/mythtv/themes/Terra/settings-ui.xml
2014-01-29 10:59:12.626057 E [2339/2339] CoreContext 
xmlparsebase.cpp:693 (LoadWindowFromXML) - XMLParseBase: No theme file 
/usr/share/mythtv/themes/Terra/settings-ui.xml
2014-01-29 10:59:12.626080 I [2339/2339] CoreContext 
xmlparsebase.cpp:685 (LoadWindowFromXML) - XMLParseBase: Loading window 
themechooser from /usr/share/mythtv/themes/default-wide/settings-ui.xml
20

Anyway thanks again for helping, I think I'm past this hiccup and nearly
have the thing working as I want.

Cheers,
	Paul.


More information about the mythtv-users mailing list