>I'm wondering exactly what the effect of "with persistence" is, for example.
Persistence is a very useful feature, whereby a certain amount of storage is reserved on the media that is used when a change is made from the .iso , so that when it is again booted, that change is still there. For example: I use a live session to back up my hard drive to another drive. The back up program is not part of the .iso, so it must be installed. Without persistence, each time I back up the drive, I must again install that program. With persistence, after the first time installed, it is as if it were part of the .iso, and is usable immediately after boot. Also, for instance, I happen to like the main panel on the top of the screen, not the bottom, and my window-control buttons on the left, not on the right. With persistence, after I first change these preferences, every time I boot, the panel is at the top, and the window buttons on the left. In effect, one can make a "custom" live session. It is, of course, more useful, the more packages one needs to install, and the more customizations one makes to the UI. >Could you try again without that and see if that makes a difference for you, >please? Yes... well... booting the live-usb without persistence solved the problem. I can only speculate, that Calamares (or something Calamares calls) refers to /run/live/medium/live/filesystem.squashfs two different ways in two (or more) different locations of the code. Without persistence, the two ways point to the same place, and all is good. With persistence, the two ways point to two different places, and it fails. Perhaps a symlink is involved...?
