- removed issue_update
T3 settings file damaged
Issue #208
resolved
I have had 2 occurrences of the settings file being written to by some process and the next time a reboot happened or a GUI restart the T3 is left unable to restart enigma.
In both cases the same information was written into the enigma settings file
Excerpt from damaged /etc/enigma2/settings file: ... config.networkbrowser.automountpoll=true config.networkbrowser.automountpolltimer=1 config.softwareupdate.checktimer=1 config.softwareupdate.updateisunstable=<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /feeds/3.0/status was not found on this server.</p> <p>Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.</p> </body></html>
config.recording.filename_composition=short config.recording.margin_before=1 config.recording.keep_timers=2 config.recording.margin_after=15 ...
Reproduction steps
There is no specific steps to reproduce.
I had done the things below during the weekend.
Run a setup > software manager > update configure plugins - airplayer + EPGrefresh
Comments (8)
-
Account Deleted
-
Account Deleted
- removed issue_update
A file was uploaded. reference to attachment settings (Damaged settings file)
-
- removed issue_reproducability
- removed issue_update
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from New to Confirmed.
- This issue's description has been changed
- The reproducability has been updated, from Not determined to Rarely.
-
- removed issue_status
Fixed both the source of the problem and the code that eventually parses the corrupt file.
The issue was updated with the following change(s):
- The status has been updated, from Confirmed to Implemented.
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Implemented to Closed.
-
- removed issue_status
20140508 survives deliberate corruption of the /etc/enigma2/settings file.
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Closed to Testing.
-
- 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):