Summary: | www-client/google-chrome-92.0.4515.107 freezes with sys-apps/systemd-249.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fabio Coatti <fabio.coatti> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christian, eugene.shalygin, harrisl, me, pacho, sam, systemd |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://github.com/systemd/systemd/issues/20111 https://bugs.gentoo.org/show_bug.cgi?id=804324 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Fabio Coatti
2021-07-21 17:33:24 UTC
Have you tried rebooting after upgrading to 249.1? (In reply to Mike Gilbert from comment #1) > Have you tried rebooting after upgrading to 249.1? Yup, sure. It looks like this is a bug in Chrome. Unfortunately, we will have to wait for Google to ship a new build with the fix. In the meantime, I would suggest disabling nss-resolve (remove it from /etc/nsswitch.conf). The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=774d25d68d6fce0e1fc0168f50f515c988e6ebf6 commit 774d25d68d6fce0e1fc0168f50f515c988e6ebf6 Author: Stephan Hartmann <sultan@gentoo.org> AuthorDate: 2021-07-24 09:47:31 +0000 Commit: Stephan Hartmann <sultan@gentoo.org> CommitDate: 2021-07-24 09:48:39 +0000 www-client/chromium: stable channel bump to 92.0.4515.107 Bug: https://bugs.gentoo.org/803167 Bug: https://bugs.gentoo.org/803467 Bug: https://bugs.gentoo.org/769989 Bug: https://bugs.gentoo.org/803260 Package-Manager: Portage-3.0.20, Repoman-3.0.2 Signed-off-by: Stephan Hartmann <sultan@gentoo.org> www-client/chromium/Manifest | 3 +- ...515.80.ebuild => chromium-92.0.4515.107.ebuild} | 16 +++---- .../files/chromium-92-GetUsableSize-nullptr.patch | 46 ++++++++++++++++++++ .../chromium/files/chromium-freetype-2.11.patch | 50 ++++++++++++++++++++++ 4 files changed, 103 insertions(+), 12 deletions(-) (In reply to Mike Gilbert from comment #5) > It looks like this is a bug in Chrome. Unfortunately, we will have to wait > for Google to ship a new build with the fix. > > In the meantime, I would suggest disabling nss-resolve (remove it from > /etc/nsswitch.conf). I can live also with old systemd until the issue is fixed, but my nsswitch conf has no direct reference to nss-resolve: aliases: files ethers: files group: files [SUCCESS=merge] systemd gshadow: files systemd hosts: files mdns_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns netgroup: files networks: files dns passwd: files systemd protocols: files publickey: files rpc: files shadow: files systemd services: files I guess "mdns_minimal" can be at fail here, or maybe "systemd" in group? (admittedly, I have yet to find the time to fiddle around with my config) (In reply to Fabio Coatti from comment #7) > > In the meantime, I would suggest disabling nss-resolve (remove it from > > /etc/nsswitch.conf). > > I can live also with old systemd until the issue is fixed, but my nsswitch > conf has no direct reference to nss-resolve: > > [..] > hosts: files mdns_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] > [..] > I guess "mdns_minimal" can be at fail here, or maybe "systemd" in group? > (admittedly, I have yet to find the time to fiddle around with my config) fyi: actually, it's the »resolve« entry that triggers nss-resolve 'dns' uses /usr/lib/libnss_dns.so. 'resolve' would use /usr/lib/libnss_resolve.so, and so on... (In reply to Fabio Coatti from comment #7) Remove "resolve [!UNAVAIL=return]" from the hosts line. (In reply to Mike Gilbert from comment #9) > (In reply to Fabio Coatti from comment #7) > > Remove "resolve [!UNAVAIL=return]" from the hosts line. Thanks!! The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0c8827bdd3d8723d0d84d79787e6c9f241306385 commit 0c8827bdd3d8723d0d84d79787e6c9f241306385 Author: Stephan Hartmann <sultan@gentoo.org> AuthorDate: 2021-07-26 21:16:01 +0000 Commit: Stephan Hartmann <sultan@gentoo.org> CommitDate: 2021-07-26 21:17:08 +0000 www-client/chromium: dev channel bump to 93.0.4577.8 Bug: https://bugs.gentoo.org/803260 Bug: https://bugs.gentoo.org/769989 Package-Manager: Portage-3.0.20, Repoman-3.0.2 Signed-off-by: Stephan Hartmann <sultan@gentoo.org> www-client/chromium/Manifest | 4 +- ...0.4557.4.ebuild => chromium-93.0.4577.8.ebuild} | 21 ++---- .../files/chromium-93-EnumTable-crash.patch | 79 ++++++++++++++++++++++ 3 files changed, 88 insertions(+), 16 deletions(-) It seems like the fix was approved and submitted to chrome 92. https://bugs.chromium.org/p/chromium/issues/detail?id=1221442#c43 https://bugs.chromium.org/p/chromium/issues/detail?id=1221442#c44 Does 92.0.4515.131 already include the fix? (In reply to therjak from comment #12) > It seems like the fix was approved and submitted to chrome 92. > > https://bugs.chromium.org/p/chromium/issues/detail?id=1221442#c43 > https://bugs.chromium.org/p/chromium/issues/detail?id=1221442#c44 > > Does 92.0.4515.131 already include the fix? Yes. |