Ticket #13819 (closed Bugs: Obsolete)
guisettings.xml file restore
|Reported by:||robweber||Owned by:|
|Priority:||4 - Normal||Milestone:|
|Component:||Other (un-categorized if does not fit anywhere else)||Version:||12.0 "Frodo" RC2|
Not sure this is even bug, it appears to be more along the lines of "just the way xbmc works" but wanted to log it anyway.
I am currently maintaining an addon for backup/restoration of xbmc files. There have been issues from users when restoring regarding settings that are stored in the guisettings.xml file. A brief synopsis of the conversation/testing can be found here: http://forum.xbmc.org/showthread.php?tid=129499&pid=1272902#pid1272902
The guts of the issue appear to be that guisettings.xml is read in by xbmc on startup, written to periodically while xbmc is running as needed, and written again just as the system shuts down. This makes it basically impossible to restore the file while xbmc is running as it will overwrite the file upon closing xbmc anyway.
For people running "appliance" type version of xbmc, like OpenELEC, this leaves them with almost no way of restoring this file, unless they know how to ssh into the system, kill xbmc, do a manual file restore, and then restart xbmc. Other systems can more easily restore the file while xbmc is not running, but it is still a more comprehensive process than it really needs to be.
An example solution that has been thrown out include a simple check for guisettings.xml.restore (or whatever) during the startup sequence to allow xbmc to register a guisettings restore file to replace the original (this could be copied over while the system is running with an addon, then restart xbmc to take effect).
I understand this is not something that will change for Frodo, or even maybe at all, but wanted to bring it up.