Comment 72 for bug 1619188

Even if it works for you with a live seesion, it does not work for me with a persistent live session using a casper-rw partition. starting from the Ubuntu 16.04.1 LTS iso file. I don't think mkusb has anything at all to to with this functionality because it does not touch the mechanism (unless you tell it to do it, and then it will prevent unattended upgrades).

mkusb has a work-around feature, and I think all other tools and manual methods, that create persistent live drives will need some work-around to avoid this problem. For example, if you create a cloned system with the Ubuntu Startup Disk Creator, the cloned result will be exactly like cloning with mkusb. It is possible in such cases to create persistence by using a casper-rw partition (or file) in another drive. I will test tonight, if such a system is also vulnerable to this bug.

I plan to start the test from the Ubuntu 16.04.1 LTS desktop amd64 iso file. I intend to upgrade casper, but no other program package unless you advice what must also be upgraded for your fix to work.

But don't tell me that I must try with the current daily iso file, because then I would have to test for a very long period of time for something to happen. In that case (if you know things have changed to the better, but don't know which program packages are involved) maybe I should zsync today's daily iso file and keep it for some weeks before I start it and let it run for at least 24 hours.

The important thing here is to get something working for the next point release, 16.04.2 LTS, so I think it should be tested thoroughly.