Hi Matthew, The situation reloading the lists would fix this in is when a new version of the package you are trying to install has been released, so the old one has been removed from the mirrors but is still referenced in your local package list. This causes software center (or any package manager) to try to download the old, non-existent file, resulting in the 404. Reloading the package list will get the information about the new package version and try to download that instead, which solves the 404.
This is more likely to happen during a beta as well, since so many packages are being updated so often. -Dan -- 404 from the archive is not handeld well https://bugs.launchpad.net/bugs/451366 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
