- removed issue_status
Files missing from Backup Settings
Some relevant files are missing from the default Backup Settings list, there may be others.
- /etc/samba/smb.conf has the samba workgroup setting.
- /etc/auto.network has the current list of active automounts.
- /etc/fstab has the current list of boot time mounts.
The last 2 reflects the settings in /etc/enigma2/automounts.xml, so a visit Mount Manager can put them back but it is stuffing around that a user should not need to do.
Need to review factory settings for etc/enigma2/settings -> config.plugins.configurationbackup.backupdirs
Reproduction steps
- Setup > Software Manager > Backup settings
- Install new firmware from USB
- Yes, restore settings.
- Oh Dear! Default samba workgroup setting.
- Oh Dear! Boot time mounts do not happen.
- Oh Dear! Automounts are not active.
Comments (7)
-
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Confirmed to Implemented.
-
reporter Not in 20140508.
-
The complete fix will be in firmware release after 20140508
However, to actually get the benefits of the fix, you need to either not restore your settings backup or delete the config.plugins.configurationbackup.backupdirs entry from /etc/enigma2/settings
This is because the old set of files will be already present in your config, so the new defaults won't be used.
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Implemented to Testing.
-
- removed issue_category
The issue was updated with the following change(s):
- The category has been updated, from Not determined to Application / User Interface.
-
- removed issue_resolution
- removed issue_percent
- removed issue_close
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Testing to Closed.
- This issue has been closed
- This issue's progression has been updated to 100 percent completed.
- The resolution has been updated, from Not determined to Fixed.
- Log in to comment
The issue was updated with the following change(s):