@Nicolas: Yes, actually $HOME/.Private is simply simlinked to /home/.ecryptfs/$USER/.Private - so the result is the same.
After deleting the 24 found zero-length encrypted files, I've not experienced the issue again. No more dmesg errors. This is after several reboots also.
Clearly this is neither the desired solution, nor a clean one, but simply a workaround. Hopefully the root cause can be determined and fixed.
@Nicolas: Yes, actually $HOME/.Private is simply simlinked to /home/. ecryptfs/ $USER/. Private - so the result is the same.
After deleting the 24 found zero-length encrypted files, I've not experienced the issue again. No more dmesg errors. This is after several reboots also.
Clearly this is neither the desired solution, nor a clean one, but simply a workaround. Hopefully the root cause can be determined and fixed.