The pinning is holding me back for moving from current version to 20.04. So far the only option I see is to use the beta you pointed me to or switch to google-chrome which looks like there still create debs.
Not being able to pin things and not being able to choose when the snap upgrade is a problem for product system. We use zfs for all the containers in production. We take a snapshot before upgrade the deb packages. And if thing fail we the rollback to the snapshot then clone container into testing area look at what failed. We can then pin the deb we think caused and start testing again. Once the zfs clone work we then apply the pin needed in production and the upgrade the production container. For the time being we are only forced into snap for chromium. If we are force into snap for other packages there a few lib that we have patches for to make sure they can not access share memory for X11 (modify the testing for share memory to allways fail) which make all of Gnome base code work 100% on the time instead of 60% without the patches. Having to modified version of some lib will become a problem if more programs become snap. We can config apt to allow us to handle this. We see now way to handle this under snaps. Also since the source code to build the snap is not there is no way to audit the snaps. Is there a good to post the problem we have with snap to see if something can be done to expand the snap system to handle the problem we see. Snap might work for the standard desktop system but a big problem for server in production. We try to have a tight control over when updates to production happen and why. Once snap has way for us to build them to make sure that they match the source code and allow us to fix problem and submit the fixes upstream they might look better to us. Also snap should have a way to configure ping/holding version and allow us to control when updates happen. It looks like you are taking away control of system with snaps. On 6/15/20 9:56 AM, Olivier Tilloy wrote: > I'm glad that this update fixes the crash, thanks for the feedback. > > I don't have a general solution to the problem you expose (pinning a > specific revision of a snap), but in the description you mention 16.04 > and 18.04, and both offer deb packages for chromium (the chromium deb > was transitioned to a snap starting with 19.10), so at least in this > specific case you can use apt pinning. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877173 Title: Chromium 81.0.4044.122 crashes on remote ssh connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
