[16:04] <superm1> cyphermox: have you noticed any "interesting" interactions with mokutil changing states and current kernel not working?
[16:04] <superm1> i ask because: https://github.com/torvalds/linux/commit/ed8b0de5a33d2a2557dce7f9429dca8cb5bc5879 seems to muck around pretty poorly
[16:05] <superm1> and at least on my box i was having a hard time making mokutil even work until i changed immutable state on any existing Mok* variables
[16:05] <cyphermox> heh, I suppose that could be why mokutil says it fails to request state, I don't know
[16:05] <superm1> yep that's exactly what i saw
[16:05] <superm1> change immutable status on variables and it starts to work
[16:06] <superm1> well Work.  i haven't seen it work yet, just the variables write out more properly
[16:07] <superm1> I first noticed it affecting fwupdate on a fresh ubuntu install unable to clear old variables, so had to do this: http://anonscm.debian.org/cgit/uefi/fwupdate.git/commit/?id=b5e8c41e679ac0c6966771881e10f8b89021770e
[16:17] <cyphermox> right
[16:17] <cyphermox> I think fwupdate and mokutil need an update to handle this correctly
[16:41] <superm1> well fwupdate seems to handle in usage, it was only in the fresh install scenario (clear out old variables) that it failed
[16:41] <superm1> mokutil seems to fail all over the place