My private build of iodéOS-4.2 boots on lynx and seems mostly working but the blocker app is stuck on initializing. The settings page is accessible and I’ve logged in OK. Taking a log and a bit of research suggested a temporary fix by setting SELinux to permissive. This makes the app work but seems a bit of a hack and probably ill-advised. Rebooting wipes the changes.
I’m wondering if there is a suitable permanent fix for this?
From the logcat, many lines of :
07-01 09:17:21.632 4107 4107 W 1.ui : type=1400 audit(0.0:430): avc: denied { write } for name=“iode-snort-control” dev=“tmpfs” ino=1070 scontext=u:r:untrusted_app_30:s0:c179,c256,c512,c768 tcontext=u:object_r:iodesnortcontrol_socket:s0 tclass=sock_file permissive=0 app=com.iode.app
I just pushed a commit in vendor/extra that should work. Sync again (all repos or just vendor/extra, also with git-lfs).
@petefoth : the iodé app must be resigned to be allowed to access a system socket. You had apparently some trouble with it in your iodé 2 builds, but this resigning is necessary.
We relaxed some settings that block accounts after several failed attempts. There is no reason that you could not manage to log in.
I could log in ok, no problem.
I will do the repo sync stuff again later. 
That worked, but not first time because I seemed to get in a right mess and thought it simplest to start again with a cleaned out directory. Thanks for your help; it’s great to have the blocker back on a solid footing. Everything else on the device seems to be working well as far as I can tell in the few hours of use I’ve had since installing.