Sergei Slobodov wrote:
> I have changed user email setting from "forward" to "forward and store locally" then pressed "save", then, after getting a response, "q" to quit lynx. I have no custom packages, I have not
touched command line tools, and repeating the change to user settings does not fix the problem. Sounds like a bug to me.
That does sound a lot like a bug. I've taken the liberty to forward your message to bugs@e-smith.com so that it can be looked into and, if necessary, post a fix. I'm uncertain what version of the software you are running but suspect that the problem likely exists in 4.1/4.1.1/4.1.2.
> I must have not made myself clear... I was wondering what do I do to RECOVER from the error, not how I assist e-smith. That would be the next step, once my system is back to normal.
In the meantime, the easiest method to recover is to walk through the console configuration from start to finish, ensuring that the settings are still correct (hitting 'keep'). At the end it will ask if you wish to save the settings and will then automatically process the event console-save, thereby clearing the UnsavedChanges flag.
BTW, as an aside, you can see the problem as it occurs by looking in /var/log/messages.
i.e. grep UnsavedChanges /var/log/messages will return a number of results, but around the time of changing the user settings it will probably have something like:
Apr 22 13:10:38 cr402706-a /etc/e-smith/events/console-save/S95reset-unsavedflag[28329]: /home/e-smith/configuration: OLD UnsavedChanges=no
Apr 22 13:10:38 cr402706-a /etc/e-smith/events/console-save/S95reset-unsavedflag[28329]: /home/e-smith/configuration: NEW UnsavedChanges=yes
Once your machine has been recovered, could you please send /var/log/messages to bugs@e-smith.com so that we can easily find a solution and post a fix?
Thanks for the report.
Regards,
Jay