Version 59.0.3067.0 has hi-dpi issues (the text and the overall interface is super tiny)
I don't have this issue on chromium (which is version 57.0.2987.133)
I use google-chrome-dev sparingly, so I just noticed this issue. It didn't happen one or two upgrades ago. Maybe it's a regression? If I find some time I can try to downgrade and see if it still happens.
Does anybody notice this behavior?
Search Criteria
Package Details: google-chrome-dev 132.0.6793.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/google-chrome-dev.git (read-only, click to copy) |
---|---|
Package Base: | google-chrome-dev |
Description: | The popular web browser by Google (Dev Channel) |
Upstream URL: | https://www.google.com/chrome |
Keywords: | chromium |
Licenses: | custom:chrome |
Provides: | google-chrome |
Submitter: | None |
Maintainer: | gromit |
Last Packager: | gromit |
Votes: | 653 |
Popularity: | 1.32 |
First Submitted: | 2009-06-05 21:02 (UTC) |
Last Updated: | 2024-10-24 21:01 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- ttf-liberation (ttf-defenestrationAUR)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- gnome-keyring (gnome-keyring-gitAUR) (optional) – for storing passwords in GNOME keyring
- kdialog (kdialog-gitAUR) (optional) – for file dialogs in KDE
- kwallet5 (optional) – for storing passwords in KWallet
- pipewire (pipewire-gitAUR, pipewire-full-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (41)
- bitwarden-chromium (requires google-chrome) (optional)
- captive-browser-git (requires google-chrome) (optional)
- chrome-extension-bitwarden-git (requires google-chrome) (optional)
- chrome-extension-ocrs-git (requires google-chrome)
- chromedriver (requires google-chrome) (optional)
- chromium-bypass-paywalls (requires google-chrome) (optional)
- chromium-extension-adnauseam (requires google-chrome) (optional)
- chromium-extension-autoscroll (requires google-chrome) (optional)
- chromium-extension-plasma-integration (requires google-chrome) (optional)
- chromium-extension-runet-censorship-bypass (requires google-chrome) (optional)
- chromium-material-icons-for-github-bin (requires google-chrome) (optional)
- chromium-vencord (requires google-chrome) (optional)
- chromium-vencord-bin (requires google-chrome) (optional)
- chromium-vencord-git (requires google-chrome) (optional)
- dedao-dl-bin (requires google-chrome) (optional)
- endpoint-verification-chrome (requires google-chrome)
- endpoint-verification-minimal (requires google-chrome)
- ff2mpv-go-git (requires google-chrome) (optional)
- ff2mpv-rust (requires google-chrome) (optional)
- hub-kids (requires google-chrome) (optional)
- Show 21 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 91 Next › Last »
wil93 commented on 2017-04-19 01:25 (UTC)
sgtpep commented on 2017-04-13 20:40 (UTC)
Missing dependency: gtk3
/opt/google/chrome-unstable/google-chrome-unstable: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory
Det commented on 2017-03-19 21:10 (UTC) (edited on 2017-03-22 20:13 (UTC) by Det)
Well, yes, from: https://www.chromium.org/getting-involved/dev-channel
"Dev channel: [...] There's no lag between major versions, whatever code we've got, you will get. While this build does get tested, it is still subject to bugs, as we want people to see what's new as soon as possible."
It should be taken for granted the Dev might crash. If you want to test, you can try renaming ~/.config/google-chrome-unstable/ and ~/.cache/google-chrome-unstable/, or downgrading ca-certificates-utils through /var/cache/pacman/pkg/ or https://archive.archlinux.org/packages/c/ca-certificates-utils/.
sidrocks123 commented on 2017-03-17 22:18 (UTC)
Also, the beta and the stable versions are working fine.
sidrocks123 commented on 2017-03-17 21:05 (UTC)
Hello, on updating this package from v58 to the latest version, Google Chrome loads homepage successfully, then crashes.
Error message -
--2017-03-18 02:27:17-- https://clients2.google.com/cr/report
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving clients2.google.com... 216.58.220.206, 2404:6800:4002:804::200e
Connecting to clients2.google.com|216.58.220.206|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/fd/4’
0K 808K=0s
2017-03-18 02:27:20 (808 KB/s) - ‘/dev/fd/4’ saved [16]
Crash dump id: 417867e660000000
zsh: segmentation fault (core dumped) google-chrome-unstable
The only reason why I think this may occur is that I recently updated the package "ca-certificates-utils".
Any idea about how I can resolve this issue?
Det commented on 2016-11-21 16:28 (UTC)
Yes. Those are notes, not warnings or errors, I put in there.
theaifam5 commented on 2016-11-21 16:27 (UTC)
(1/1) upgrading google-chrome-dev [######################] 100%
==> NOTE: Custom flags should be put directly in: ~/.config/chrome-dev-flags.conf
==> NOTE: The launcher is called: 'google-chrome-unstable'
Det commented on 2016-10-22 00:35 (UTC)
Fixed.
Flaeme commented on 2016-10-22 00:23 (UTC)
Patch is failing:
==> Making package: google-chrome-dev 56.0.2897.0-1 (Fri Oct 21 18:15:25 MDT 2016)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading google-chrome-unstable_56.0.2897.0_amd64.deb...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 46.1M 100 46.1M 0 0 123k 0 0:06:24 0:06:24 --:--:-- 1019k
-> Downloading eula_text.html...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 53070 0 53070 0 0 317k 0 --:--:-- --:--:-- --:--:-- 317k
-> Found google-chrome-unstable.sh
-> Found StartupWMClass-and-GNOME3-context-menu.patch
==> Validating source files with md5sums...
google-chrome-unstable_56.0.2897.0_amd64.deb ... Passed
eula_text.html ... Skipped
google-chrome-unstable.sh ... Passed
StartupWMClass-and-GNOME3-context-menu.patch ... Passed
==> Extracting sources...
-> Extracting google-chrome-unstable_56.0.2897.0_amd64.deb with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
-> Extracting the data.tar.xz...
-> Moving stuff in place...
-> Fixing Chrome icon resolution and GNOME 3 context menu...
patching file usr/share/applications/google-chrome-unstable.desktop
Hunk #2 FAILED at 113.
1 out of 2 hunks FAILED -- saving rejects to file usr/share/applications/google-chrome-unstable.desktop.rej
==> ERROR: A failure occurred in package().
Aborting...
Pinned Comments
gromit commented on 2023-07-19 17:01 (UTC) (edited on 2023-07-19 17:02 (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 "Dev 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.