I don't know what the trigger is. I suspect that it is to do with mod time on the file, as I could not just change the output file in the Xconfigure script to be a file other than /etc/X11/xorg.conf, when I tried that it just kept going in to AVwizard reconfiguration at each reboot.
But on my system even the AVwizard would stuff up the X setup halfway through customisation, such that I could not see what was going on. The screen would go a purple-black , with the top half visible, fading down to black at the bottom half of the screen. Think it was because the refresh rate was too high, if I look at the xorg.conf file it was using the freq range for vert refresh (
going from memory here) was far too high. No problem on most LCD displays, as they just "downscale" the signal to 60Hz anyway- my work one gives a warning that "refresh rate is out of range" but displays the picture anyway! On a CRT it is more serious, as they don't really cope as well.
Should I submit a patch so that the default xorg.conf refresh rate is sane? How?
Is there any reason why I can't start changing the scripts so that they respect a global variable (say LMCE_APPLIANCE_MODE), which if set causes the scripts to not overwrite changes? Or should we have a more granular approach where each script would be aware of its own setting (e.g. LMCE_MYTHTV_CORE_STOP_RECONFIGURE=1), or both, scripts obey both a global and a per-script setting.
I am reluctant to even start to change anything due to the warnings by developers, so would want some buy-in on an approach to making LMCE "hacker friendly", without compromising the aim to keep it an "appliance" for most users.
Us tinkerers would like to be able to tinker, tune, and help make LMCE better. Telling LMCE "hands off!" would help in the case of misbehaving hardware and/or misbehaving LMCE and would also help make the process of debugging problems much simpler.