Happened to me yet again, on a new system, running 16.10. Why is this still a thing? It affects every single person who uses the OS since if you don't consciously take steps to prevent it it's guaranteed to happen. And it means Ubuntu is fundamentally unsuited for general use because every layperson who uses it is going to eventually get to a point where they cannot install new packages. It's downright embarrassing. I don't understand, either, how this is only medium importance.
Not to say that subjecting users to an arbitrary timeout (with typos!) is a good thing, but this bug affects way more users than that bug does and it also has the potential to wreck systems for novice users. And undoubtedly has, over the past five-plus years it's been in existence.
Happened to me yet again, on a new system, running 16.10. Why is this still a thing? It affects every single person who uses the OS since if you don't consciously take steps to prevent it it's guaranteed to happen. And it means Ubuntu is fundamentally unsuited for general use because every layperson who uses it is going to eventually get to a point where they cannot install new packages. It's downright embarrassing. I don't understand, either, how this is only medium importance.
I mean, lord, compare it to this high-importance bug: /bugs.launchpad .net/ubuntu/ +source/ initramfs- tools/+ bug/1554795
https:/
Not to say that subjecting users to an arbitrary timeout (with typos!) is a good thing, but this bug affects way more users than that bug does and it also has the potential to wreck systems for novice users. And undoubtedly has, over the past five-plus years it's been in existence.