This is with both 9.2.2 and vpeter’s blu-ray menu build. The disc works fine on my Intel machine. Odroid C2, setup the same as my Ubuntu 20.04 Intel machine, same “~/.config/aacs” folder/contents, Kodi 18.6.
I’m not sure then, as I said encrypted disk work ok for me until I remove KEYDB.cfg from .config/aacs then I get the same error.
The only other thing I can think of is KEYDB.cfg needs to be named exactly uppercase. When I first set my system up I had problems with playback failing because the file was named lowercase keydb.cfg
With nightly though I’ve been trying different configurations and checking the error codes.
If KEYDB.cfg is missing -> error aacs_open() failed: -2!
My old KEYDB.cfg -> error aacs_open() failed: -3!
My new KEYDB.cfg (same as Intel/Ubuntu system) -> aacs_open() failed: -6!
If I copy the ~/.cache/aacs folder over from my Intel/Ubuntu system, then that disc plays.
Now I just need to confirm if the firmware on my USB BluRay drive isn’t messed up as those keys may not have been generated off this drive.
I made few simulated tests and it seems that if even if file KEYDB.cfg exists but keys are bad then it tries to load libmmbd library which doesn’t exist. So I think it is something with your keys and BD disk.
More digging, this time on my Intel/Ubuntu machine. When using the libaacs that is in Kodi, the keys are never generated. However, when opening the disc in VLC, the keys are created!
So the issue is in Kodi, not CoreELEC. Something with the libaacs being used.
Sorry for the noise. I had never considered this possibility.
@roidy Perhaps I’m using the wrong term then. What I’m specifically speaking of is the resulting files in ~/.cache/aacs/vuk and ~/.cache/aacs/vid after the decryption using the host key from KEYDB.cfg