Hi, On 08/05/2019 14:57, Alan wrote: > > The system fails to boot after installing bilibop-lockfs and activating it on > a freshly installed Debian (Buster/testing).
Yes, I reproduced it.
> Please note that this was tested on a encrypted LVM created during Debian
> installation.
It doesn't matter. As said in the bug title, mount.lockfs is broken,
you're right. A test against mount path has not been updated, and fails
on buster fresh installs - it doesn't on buster upgraded from stretch.
The culprit test in the script expects /proc/${PPID}/exe points to
/bin/mount (i.e. the parent process of mount.lockfs is /bin/mount). But
on buster, /bin is a symlink to /usr/bin so the actual executable is
/usr/bin/mount instead.
The bug is fixed upstream now, and the fix will be released soon. A
quick workaround (tested) is to turn "/bin/mount" into "/usr/bin/mount"
in /lib/bilibop/lockfs_mount_helper (line 58).
Thank you for the report,
quidame
signature.asc
Description: OpenPGP digital signature
