You are not logged in.
I upgraded chromium from 91.0.4472.114-1 to 92.0.4515.107-1
When launching it appears to hang, with the startup page not loading and no controls working at all.
In the terminal this is the error
[28281:28281:0721/075221.077039:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
[28281:28281:0721/075222.728852:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
[28281:28281:0721/075226.016628:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
[0721/075227.775891:ERROR:scoped_ptrace_attach.cc(37)] process not stopped
[0721/075227.776105:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
[28281:28281:0721/075227.789484:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
[28281:28281:0721/075234.743521:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
This is the same with a new profile in .config.
If I revert to the old version it works without error. I did a search and no results, so maybe it is just me.
Thanks for any pointers.
Offline
Not just you. Both Chromium and Chrome hang on any attempt to load a page.
[ 120.623581] ThreadPoolForeg[2904]: segfault at 101e ip 000055c3263ea472 sp 00007f21a055afc0 error 4 in chromium[55c320023000+8c58000]
[ 120.623594] Code: 02 cc 0f 0b cc cc cc cc 55 48 89 e5 48 89 f1 48 81 e1 00 00 e0 ff 48 c1 ee 09 81 e6 e0 0f 00 00 48 8d 04 31 48 05 00 10 00 00 <0f> b6 94 31 1e 10 00 00 48 89 d1 48 f7 d9 48 c1 e2 05 48 89 c6 48
[ 120.623618] audit: type=1701 audit(1626849273.044:362): auid=1000 uid=1000 gid=1000 ses=1 pid=2900 comm="ThreadPoolForeg" exe="/usr/lib/chromium/chromium" sig=11 res=1
[ 120.631477] audit: type=1334 audit(1626849273.051:363): prog-id=120 op=LOAD
[ 120.631559] audit: type=1334 audit(1626849273.051:364): prog-id=121 op=LOAD
[ 120.631590] audit: type=1334 audit(1626849273.051:365): prog-id=122 op=LOAD
[ 120.632463] audit: type=1130 audit(1626849273.054:366): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@31-2908-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 127.108799] logitech-hidpp-device 0003:046D:406A.0004: HID++ 4.5 device connected.
[ 133.856334] show_signal_msg: 4 callbacks suppressed
[ 133.856337] ThreadPoolForeg[2727]: segfault at 101e ip 000055ea91488b32 sp 00007ff1b0727320 error 4 in chrome[55ea89aa9000+822b000]
[ 133.856360] Code: 83 c4 08 5b 5d c3 cc cc 55 48 89 e5 48 89 f1 48 81 e1 00 00 e0 ff 48 c1 ee 09 81 e6 e0 0f 00 00 48 8d 04 31 48 05 00 10 00 00 <0f> b6 94 31 1e 10 00 00 48 89 d1 48 f7 d9 48 c1 e2 05 48 89 c6 48
[ 133.856387] audit: type=1701 audit(1626849286.278:371): auid=1000 uid=1000 gid=1000 ses=1 pid=2720 comm="ThreadPoolForeg" exe="/opt/google/chrome/chrome" sig=11 res=1
[ 133.862587] audit: type=1334 audit(1626849286.284:372): prog-id=123 op=LOAD
[ 133.862653] audit: type=1334 audit(1626849286.284:373): prog-id=124 op=LOAD
[ 133.862690] audit: type=1334 audit(1626849286.284:374): prog-id=125 op=LOAD
Downgrading to 91.0.x helps indeed.
Offline
I did a search and no results, so maybe it is just me.
https://bugzilla.redhat.com/show_bug.cgi?id=1973461
https://forum.endeavouros.com/t/after-t … d/15797/13
https://vivaldi.com/blog/desktop/a-quic … ot-2355-3/
Seems betweem chromium, nss and systemd
Online
Hi,
I can confirm this problem.
This morning after update of chromium to version 92.0.4515.107-1, I get
ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
on every start and network connection is broken.
It seems to be related to existing settings. When I clean folder .config/chromium/ the problem is gone.
But my settings are gone, too.
Last edited by botux (2021-07-21 07:20:49)
Offline
Hi,
It seems to be related to existing settings. When I clean folder .config/chromium/ the problem is gone.
But my settings are gone, too.
This didn't work for me.
This has got the new version working, I am not sure what it will break though.
systemctl disable systemd-resolved.service
Last edited by SimonJ (2021-07-21 07:32:28)
Offline
This has got the new version working, I am not sure what it will break though.
systemctl disable systemd-resolved.service
Thanks, this workaround works.
I will test and check what impact a disabled resolved has on my system.
Offline
Update, you can just edit the order in /etc/nsswitch.conf to
hosts: files mymachines dns myhostname resolve [!UNAVAIL=return]
and then
systemctl restart systemd-resolved.service
Offline
IMO don't bother with /etc/nsswitch.conf; instead, stop systemd-resolved and then put something like "nameserver 1.1.1.1" into /etc/resolv.conf and wait until the issue is fixed if you want to re-enable resolved.
Edit: chromium 92.0.4515.107-2 (w/ use_allocator="none") should avoid this issue until it's properly fixed upstream (either systemd or chromium).
Last edited by foutrelis (2021-07-21 10:18:08)
Offline
Same issue, indeed chromium 92.0.4515.107-2 does avoid the issue for now.
Offline
yes, i'm facing too, here on my pc.
Offline
Hi, facing with it with starting of Vivaldi. It seems that I resolved it without changing config files. After installing "nss" package browser starts work correctly.
UPD: sorry, that's wrong)) problem is actual
Last edited by heaveaxy (2021-08-02 07:43:24)
Offline
After installing "nss" package browser starts work correctly.
Are you using archlinux?
nss is a hard dependency for vivaldi. https://archlinux.org/packages/communit … 4/vivaldi/
You *cannot* have installed it afterwards.
You're either conducting partial upgrades or the outcome is purely coincidental.
Online
You right, didn't notice about "reinstalling" thing
Offline
Update, you can just edit the order in /etc/nsswitch.conf to
hosts: files mymachines dns myhostname resolve [!UNAVAIL=return]
and then
systemctl restart systemd-resolved.service
This "resolved" the error in Vivaldi.
Offline
That's equivalent to not using resolved and in any event myhostname should™ be before dns.
It also probably means that systemd-resolved returns a bogus status (I guess "notfound") for uncached domains.
Online
That's equivalent to not using resolved and in any event myhostname should™ be before dns.
It also probably means that systemd-resolved returns a bogus status (I guess "notfound") for uncached domains.
Not only that, page loading became quite choppy, so I went back to the old way until the issue is fixed.
systemctl disable systemd-resolved.service
Offline