Garrett LeSage

I'm trying to figure out the context of this. I think we talked about this before, but I can't find it. I don't know what this was like before compared...

OK, so the current UI is this?  Where we have a bogus path to a file that doesn't work by default and is so long you can't see where...

OK, now I've switched branches, did a git clean, and make devel-install, and I get this:  It's better, as I can actually see the location. But it still fails...

System VMs seem better, though, as they at least have a working path: 

> These are bugs in our FileAutocomplete component. There is usually some way of getting around them with creative clicking around. > > It's not a regression in this PR,...

OK, that was a local VM problem. Disks were removed somehow, perhaps resetting VM states before vacation for testing some issue with VMs for Anaconda test machines or something. Apologies!

Instead of: - 117 GB available at this location. About 1.09 GB are needed to save the memory state of the machine. What about this? - Each memory snapshot will...

> Thus, disk snapshots don't take any appreciable amount of space at the time of creating the snapshot. Right, but this modal isn't for the first time only, and people...

> Sooooo... you want Cockpit to show the current sizes of snapshots in the list of snapshots? > > I think we can do that as a total, like "XXX...

Generally, it's better to prefer non-jargon text when possible and to avoid exposing implementation details. However, if we are going to do this bonkers thing to let people shoot themselves...