After upgrading to 205 yesterday evening, I discovered this morning that the Guardian interface has become shattered. Un- and reinstalling Guardian with dependencies seems to have fixed that.
Having the same issue with WIO, I suppose that some addons have relations to the kernel.
Am I right, that with the build of CU205 the addons are rebuilt, also. Linked with the new kernel libs.
Because CU205 is a security build, to supply the patched kernel, dependencies of addons are not considered. These would have produced a new version number.
In this situation, if I am right, the best solution is an uninstall/install process for affected addons.
BTW, I can not see the shattered WUI for Guardian. Maybe the reinstall of WIO changed something for the whole system.
No, this is incorrect.
The kernel is the only thing that has been touched and it does not influence what is being shown in the browser. So I would recommend to add screenshots here, and if people can reproduce the behaviour to file a bug report.
A screenshot of the WIO page can be found in WIO is not working properly after updating to CU202 - #23 by kuni
I must apologize, that I haven’t looked at the errors in the httpd logs.
Fact is, that two addons have the same remedy.
Furthermore it is not unexpected, that such a very quick (thanks!) update bears little issues.
EDIT: A short investigation of /var/log/httpd/error_log shows messages about lines not found in my actual sources ( wio.cgi and wio.pl ). Is it possible, that the CU205 build incorperated some corrections dedicated for CU205 testing ( now CU206 testing )?
Already been reported in a bug.
https://bugzilla.ipfire.org/show_bug.cgi?id=14663
A fix has been mentioned in that bug report but I want to clarify that the fix has not yet been merged into any of the IPFire branches and it has not yet been decided which Core Update it will end up in.
CU206 and CU207 are both looking quite large so we will have to be careful what we put into which Core Update.
Once decided it will be mentioned in that bug report.
This was also nothing to do with moving from CU204 to CU205 as the problem was reported from CU204.
Some investigation shows the language file isn’t uptodate.
I did an upgrade with a VM from CU203 to CU205, only WIO installed.
After reboot the WIO page was shattered, the error file showed missing $Lang::tr(…) entries. A rebuild of the language cache solved the problem.
The rebuild is done by a reinstall also.
Seems a temporary problem of the quick release of CU205.


