ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
Same here at systemd 249 (249-2-arch)
Using Chromium for now
Git Clone URL: | https://aur.archlinux.org/google-chrome.git (read-only, click to copy) |
---|---|
Package Base: | google-chrome |
Description: | The popular web browser by Google (Stable Channel) |
Upstream URL: | https://www.google.com/chrome |
Keywords: | chromium |
Licenses: | custom:chrome |
Submitter: | None |
Maintainer: | gromit |
Last Packager: | gromit |
Votes: | 2237 |
Popularity: | 7.89 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-09-17 21:41 (UTC) |
« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 157 Next › Last »
ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
Same here at systemd 249 (249-2-arch)
Using Chromium for now
Google Chrome stopped working after updating systemd to 249-3, the error is:
ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
Seems like the issue is related to DNS resolving, as browser can still open simple pages if I use IP address.
Downgrading to systemd 248-3 resolves the issue. Meanwhile Chromium works totally fine with systemd 249-3.
On KDE desktop environment, F11 hotkey for entering in the fullscreen mode and exiting the fullscreen mode isn't working.
Man I missed google-chrome 2000 votes.
You are right. It works now.
@simontunnat: That looks more like a hiccup in the AUR git repo… Just try again…
I get the following error message when trying to update to version "":
" error fetching google-chrome: fatal: unable to access 'https://aur.archlinux.org/google-chrome.git/': Received HTTP code 502 from proxy after CONNECT "
Is there something wrong with the package definition?
@Parintachin:
Thanks for the help. Yes, --force-device-scale-factor=2 does fix the problem.
Thank you. -Jack
@Jackcode01:
Yup; apparently it's a bug further up the chain? It came up again when Brave was updated yesterday; the guy maintaining that package was good enough to answer me.
A fix is to run Chrome with --force-device-scale-factor=2, as described here: https://wiki.archlinux.org/title/HiDPI#Chromium_/_Google_Chrome
On Manjaro KDE with 200% scale setting, Everything is HUGE!
Pinned Comments
gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (UTC) by gromit)
When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Stable updates" tag in Release blog for this.
You can also run this command to obtain the version string for the latest chrome version:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.