I've tested this again just now and in typically I cannot get it to fail again on my computer. I've asked someone else to test and although it took about 10 minutes compared to the 10 seconds it took me, it did complete. This is despite us being sat next to each other on the same network and their device being a higher specification than mine.
After replicating this bug during the Ubuntu Summit, then me replicating the failure on a Canonical employees device in the same way, I'm certain in some scenarios it fails and leaves the device with a partially installed snap. Perhaps this is down to the snap taking a long time to download then hitting a timeout whilst the install is occurring? You can see a report of this in the linked bug #1891373. To clarify when I say the package should handle its own failure scenarios, I don't mean that it shouldn't fail, just that it should put the system back into the state it was in before the failure rather than leave something behind that could cause problems with future installations. I appreciate that it may be difficult to do this if I appreciate that this may be a difficult one to get to the bottom of and appreciate your patience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886414 Title: the chromium snap takes a long time to install without visible user feedback, seems stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1886414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
