Opened 3 years ago

Closed 2 years ago

#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
Severity: Normal Keywords:
Cc: Blocked By:
Blocking: Platform: All


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:

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.

Change History (3)

comment:1 Changed 3 years ago by fernandovg

Possible a feature request but I agree with it.

comment:3 Changed 2 years ago by Martijn

  • Milestone Future / Pending deleted
  • Resolution set to Obsolete
  • Status changed from new to closed

see PR

Note: See TracTickets for help on using tickets.