This one is tricky, since I can't just identify the package and file a bug concerning the package, because it's not a problem concerning its behaviour in a regular desktop environment.
Actually the problem is that the live system keeps /var/crash and /var/log mounted on the support. Not quite read-only any more huh ?
Because of this :
- The live image is modified (failing further checksum-based integrity checks one would want to make before booting)
- It's not possible to load to RAM and eject
Actually it's possible to load to RAM and eject (what's impossible with Linux after all ?), but that requires more steps :
# umount /var/crash
# fuser -m -k -TERM /var/log ; umount /var/log # repeat until it works (usually once is enough)
And then eject, the usual way, e.g. from the Nautilus interface.
But it's not supposed to be a place to report bugs here, hence my question : how shall I report ?
EDIT : I found out that persistence is enabled by default. One has to pass the nopersistent parameter at boot to prevent the live system from creating an additional r/w partition on the support. This is annoying...
dd if=/dev/my_usb_stick count=imgblocknum | shasum -a 256, I don't get what I should get. In the present case (current 19.10 live image), imgblocknum is 4812192 blocks. I tried before booting it, and it was giving me the correct value. No persistence is activated, I only passed the "locale=fr_FR.UTF-8" and "toram" parameters to the kernel. I tried without passing anything, and the problem is the same. Anyway, just try for yourself and you will see. I had no problems with the 19.04 imagenopersistentparameter prevents the live image from creating an additional r/w partition on the support.