Thank you for your response. > It's unclear why > this is so different when it appears that apt is just calling the snap > installation?
Indeed, the deb hook is just calling snap install chromium, so it is also beyond me why this problem occurs and so I assumed this wasn't part of the issue. But given you report of it being a consistent and recurring issue with a specific 20 min timeout, I'll ask around, maybe it is a dpkg thing. > 2. If the apt installation of chromium-browser fails, it should do so in > a way that the system doesn't now believe that it is installed, From the bug description, the system does not believe the package is installed: > Errors were encountered while processing: > > /var/cache/apt/archives/chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) Can you clarify what leads you to conclude that the system thinks the package is installed? The commands dpkg -l chromium-browser snap info chromium-browser are one way to find out whether that is correct. > the package should handle it's own failure > scenarios appropriately. I'm not sure about that. Suppose the snap really can't be downloaded right now, let's say, store is down. Then the installation failing is the only right outcome as far as I can see. Am 06/11/2024 um 13:51 schrieb [email protected]: > Thank you for taking this bug on. If it was just a case of the snap > taking a long time it would be tolerable, but in some scenarios it just > hangs with the snap partially installed. This means the application > isn't installed, and now installing it isn't possible without resetting > snap to a consistent state. > > So to answer your question of what a good user experience would be: > > 1. Ideally, the snap would just install regardless of whether apt or > snap initiated it. If I do `snap install chromium-browser` it works, but > `apt install chromium-browser` is hit and miss and takes considerably > longer to the point of timing out after 20 minutes. It's unclear why > this is so different when it appears that apt is just calling the snap > installation? > > 2. If the apt installation of chromium-browser fails, it should do so in > a way that the system doesn't now believe that it is installed, even > though the snap isn't available to run. As a result, the user could > simply try the installation again with the hope it succeeds the next > time, without needing to figure out how to get their system back into a > state where the installation can be reattempted. > > I haven't tested the proposed solution, but if it works then I feel > giving the user prompts to deal with the issue appropriately is helpful, > but really is just a workaround. Ideally users shouldn't need to take > the steps mentioned and the package should handle it's own failure > scenarios appropriately. > -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
