> So is there still a bug with 20.04 as you suggest? At the time I posted my comment, yes there absolutely was.
A regression had been introduced in the daily 20.04 builds, that made persistence consistently fail on some machines. This was confirmed by other people too. Now, since I added my reports onto it, the most problematic aspect of this issue has now been fixed, though there still exist a non-breaking corollary issue (introduction of a new 'writable' name for persistent partitions) that a few of us would like to see addressed. It's all in the bug report(s) I linked to. > If the bug was only squashed with 19.10 are you going to give up on persistence for Rufus and just wait for the bug to get fixed? That was a consideration I had, since, at the time, it looked to me like Ubuntu made little effort to backport the bugfix into 18.04 (which, I will assert, they should have if they actually cared about their LTS users) and had suddenly broken persistence for 20.04 again. But with 20.04 being somewhat usable for persistence again, the only major issue that persists is that 18.04 hasn't been fixed, which is the precise reason we are having this "discussion". > Perhaps another five years. And that is exactly my issue. People who should have made a bigger deal of this issue (including asking for a 18.04 backport) appear to have just been content to declare, as you are attempting to do, that the manner in which Rufus and other methods that happen to create persistent partitions that trigger this bug, are "unnatural", which is simply ridiculous since it is really the most straightforward way to do it. Therefore, instead of helping raise heat so that maintainers realised that this was a problem for many many users, helped ensure that the issue was left unaddressed for years instead, leading us precisely into the situation we are now, with user after user reporting `mount: mounting /cow on /root failed: Invalid argument` issues when they try to use 18.04 with persistence. > Seems better to me to work with what we have rather that wait for a perfect world. Seems better to me to have people understand the ramification of trying to brush an issue under the carpet and/or the negative impact that an unaddressed bug can have for Ubuntu users. I'm pretty sure that, if the bug was with Rufus, we'd see quite very different tune from you, with something along the line of "How can you pretend to care about your users if you are going to leave this Rufus bug unaddressed for years?". So maybe you want to make an attempt to review the situation a bit more objectively at last. Plenty of users of Ubuntu are affected by this issue still, since 18.04 has not backported this bugfix. And you should really know this, because you've been seeing that issue pop up in askubuntu over and over again. So, if you actually care about Ubuntu users, you might want to stop this charade of trying to point the finger at anything but the actual bug, and instead, contribute to this report to help the maintainers realize that, maybe, the fix for this is something that they should have backported to 18.04, because it has been ending up affecting many many first time users of Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489855 Title: Change to mount sequence order breaks persistence on casper-rw partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
