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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1877173 Title: Chromium 81.0.4044.122 crashes on remote ssh connection Status in chromium-browser package in Ubuntu: New Bug description: Chromium crash on a ssh x forwarding connection It crashes on both 18.04 and 16.04 with the same message. The X forwarding is working for other programs just fine. It was working until last update. Here is the message from the console on the crash [22765:22781:0506/144206.193243:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye. Trace/breakpoint trap (core dumped) Steps to repeat: ssh ltcd-prod chromum-browser ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 81.0.4044.122-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: btrfs xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid veth iptable_filter bpfilter bridge stp llc binfmt_misc intel_powerclamp coretemp kvm_intel kvm irqbypass zfs zunicode zavl icp ipmi_ssif gpio_ich crct10dif_pclmul crc32_pclmul ghash_clmulni_intel zcommon znvpair spl zlua aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate ast drm_vram_helper ttm drm_kms_helper lpc_ich drm joydev input_leds fb_sys_fops syscopyarea sysfillrect sysimgblt ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel lp parport nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 hid_generic igb uas usbhid ahci i2c_algo_bit hid libahci usb_storage dca i2c_ismt ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: modes: 1024x768 800x600 800x600 640x480 Date: Wed May 6 14:37:46 2020 Desktop-Session: 'None' 'None' 'None' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: Load-Avg-1min: 0.55 Load-Processes-Running-Percent: 0.1% Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: Supermicro A1SAi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=UUID=c75e8c2a-b85d-444e-b278-16fd90c327e7 ro usb_storage.quirks=0bc2:331a:u,0bc2:ab31:u,0bc2:ab34:u SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1a dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A1SRi dmi.board.vendor: Supermicro dmi.board.version: 123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 18 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1a:bd08/27/2015:svnSupermicro:pnA1SAi:pvr123456789:rvnSupermicro:rnA1SRi:rvr123456789:cvnToBeFilledByO.E.M.:ct18:cvrToBeFilledByO.E.M.: dmi.product.family: SMC X10 dmi.product.name: A1SAi dmi.product.sku: 081315D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
