[Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
Your concerns are valid. May I suggest you take them to a new thread on https://forum.snapcraft.io/ ? There will be many more eyes on it, and I'm sure you will get more elaborate and constructive answers there, than in this bug report. Regarding the source code to build the snaps, in the case of chromium it is available there for everyone to audit: https://code.launchpad.net /~chromium-team/chromium-browser/+git/snap-from-source/+ref/stable. -- 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
Re: [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
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
[Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
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
Re: [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
that fixes the --no-sandbox but still needs the QT_X11_NO_MITSHM=1 also the --no-xshm works now. This whole bug report shows my big problem with snaps. In production I have a pin a version of chromium that works so that I can use webdriver to access a number of site that I need to submit data to. Once snap become in place I do not see any way to lock/pin a version of chromium that works while the bug get fix. How can problems like this be dealt with ? On 6/12/20 10:52 AM, Olivier Tilloy wrote: > https://bugs.chromium.org/p/chromium/issues/detail?id=1039560#c14 > suggests that this should be fixed in the latest 83 stable update. > > Would you mind testing that update from https://launchpad.net > /~canonical-chromium-builds/+archive/ubuntu/stage and reporting whether > the issue persists? > > I'd recommend disabling that PPA after the test, the updates will > eventually be available in the Ubuntu archive. > -- 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
[Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
https://bugs.chromium.org/p/chromium/issues/detail?id=1039560#c14 suggests that this should be fixed in the latest 83 stable update. Would you mind testing that update from https://launchpad.net /~canonical-chromium-builds/+archive/ubuntu/stage and reporting whether the issue persists? I'd recommend disabling that PPA after the test, the updates will eventually be available in the Ubuntu archive. -- 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
Re: [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
it need the no-sandbox to work. On 6/11/20 10:57 AM, Olivier Tilloy wrote: > Thanks for the upstream report Mike. I see it has been marked as a > duplicate of > https://bugs.chromium.org/p/chromium/issues/detail?id=1035803, and > comment #19 there suggests the following: > > tldr; manually turn off shared memory by using the "--no-xshm" flag, > setting the environment variable "QT_X11_NO_MITSHM=1" or > "J2D_USE_MITSHM=0". > > Does this address your crash? > -- 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
[Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
Thanks for the upstream report Mike. I see it has been marked as a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=1035803, and comment #19 there suggests the following: tldr; manually turn off shared memory by using the "--no-xshm" flag, setting the environment variable "QT_X11_NO_MITSHM=1" or "J2D_USE_MITSHM=0". Does this address your crash? -- 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
Re: [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
I have reported the bug. Here is the url. https://bugs.chromium.org/p/chromium/issues/detail?id=1085136 On 5/20/20 8:24 AM, Olivier Tilloy wrote: > Indeed, it appears to be the same problem. I think an actual bug report > (as opposed to a support thread) would be useful if we want upstream > developers to look into the issue. > -- 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
[Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
Indeed, it appears to be the same problem. I think an actual bug report (as opposed to a support thread) would be useful if we want upstream developers to look into the issue. -- 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
Re: [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
It look like https://support.google.com/chrome/thread/41722791?hl=en On 5/19/20 8:48 AM, Olivier Tilloy wrote: > Ack, thanks Mike. In light of this information, I have removed the > duplicate status. > > Is there an upstream bug report for the crash? If not, would you mind > filing one at crbug.com ? > > ** This bug is no longer a duplicate of bug 1857252 > chromium 79 remote display broken > -- 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
[Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
Ack, thanks Mike. In light of this information, I have removed the duplicate status. Is there an upstream bug report for the crash? If not, would you mind filing one at crbug.com ? ** This bug is no longer a duplicate of bug 1857252 chromium 79 remote display broken -- 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
[Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
*** This bug is a duplicate of bug 1857252 *** https://bugs.launchpad.net/bugs/1857252 Sorry about last comment. (ignore last comment) The workaround in bug 18752 fixes the blank screen. (This is also my bug report) export QT_X11_NO_MITSHM=1 export _X11_NO_MITSHM=1 export _MITSHM=0 This work until 81.0.4044.122 which causes a crash (chromium exit) with FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye The --no-sandbox is a work around loosing process isolation. Which disabling the sandbox is not recommended, The --use-gl=swiftshader was a work around for the blank screen not the crash and --use-gl option does nothing in 81.0.4044.138. Summary so far: This is not same bug as 18752 but a new problem on a new version of chromium (Have not removed 18752 work around) There exists a work around --no-sandbox but is not recommended to use. -- 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
Re: [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
*** This bug is a duplicate of bug 1857252 *** https://bugs.launchpad.net/bugs/1857252 Can no long test this bug as chromium has moved on to 81.0.4044.132 and now has a different set of problems. Thing crash on on gpu problems. Look at Bug 1877173. On 5/15/20 7:58 AM, Olivier Tilloy wrote: > *** This bug is a duplicate of bug 1857252 *** > https://bugs.launchpad.net/bugs/1857252 > > Ack. What about the suggestion in comment #12 in the upstream bug report > (https://bugs.chromium.org/p/chromium/issues/detail?id=1026950) ? > Does this work around the crash? > -- 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
[Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
*** This bug is a duplicate of bug 1857252 *** https://bugs.launchpad.net/bugs/1857252 Ack. What about the suggestion in comment #12 in the upstream bug report (https://bugs.chromium.org/p/chromium/issues/detail?id=1026950) ? Does this work around the crash? -- 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
Re: [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
*** This bug is a duplicate of bug 1857252 *** https://bugs.launchpad.net/bugs/1857252 This is not the same problem. The --use-gl=swiftshader work for chrome before 81.0.4044.138. Without the --use-gl option it only had a blank (gray) screen but did not crash. On 81.0.4044.138 it crashes (exits). This is 2 different problems. With the end result being the same that chrome does not work on x-forward connection. On 5/14/20 11:45 AM, Olivier Tilloy wrote: > *** This bug is a duplicate of bug 1857252 *** > https://bugs.launchpad.net/bugs/1857252 > > Disabling the sandbox is not recommended, you're loosing process > isolation. > > Another suggested workaround in > https://bugzilla.redhat.com/show_bug.cgi?id=1786306 is to run chromium > with "--use-gl=swiftshader". Can you try that and let us know whether > this works? > > I'm marking this as a duplicate of bug #1857252 because they appear to > be the same issue. > > ** Bug watch added: Red Hat Bugzilla #1786306 > https://bugzilla.redhat.com/show_bug.cgi?id=1786306 > > ** This bug has been marked a duplicate of bug 1857252 > chromium 79 remote display broken > -- 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
[Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
*** This bug is a duplicate of bug 1857252 *** https://bugs.launchpad.net/bugs/1857252 Disabling the sandbox is not recommended, you're loosing process isolation. Another suggested workaround in https://bugzilla.redhat.com/show_bug.cgi?id=1786306 is to run chromium with "--use-gl=swiftshader". Can you try that and let us know whether this works? I'm marking this as a duplicate of bug #1857252 because they appear to be the same issue. ** Bug watch added: Red Hat Bugzilla #1786306 https://bugzilla.redhat.com/show_bug.cgi?id=1786306 ** This bug has been marked a duplicate of bug 1857252 chromium 79 remote display broken -- 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
Re: [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
That did work for both 18.04 and 16.04 Any idea what i lose by not having the sandbox ? On 5/7/20 4:38 AM, Sebastien Bacher wrote: > Seems similar to https://support.google.com/chrome/thread/41722791?hl=en > , does it work if you use --no-sandbox ? > -- 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
[Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
Seems similar to https://support.google.com/chrome/thread/41722791?hl=en , does it work if you use --no-sandbox ? -- 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
