need to add CHROME_WRAPPER
environment variable so that the PWA application startup icon gets the correct exec path.
export CHROME_WRAPPER="`readlink -f "$0"`"
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: | 2261 |
Popularity: | 8.10 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2025-02-19 09:28 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 157 Next › Last »
need to add CHROME_WRAPPER
environment variable so that the PWA application startup icon gets the correct exec path.
export CHROME_WRAPPER="`readlink -f "$0"`"
Avoid updating to version 124 if you use Wayland. It doesn't work there since the beta. https://aur.archlinux.org/packages/google-chrome-beta#comment-963012
Edit: here's the upstream report: https://issues.chromium.org/issues/329678163
It only seems to affect if you have set the option from chrome://flags/, if you manually run google-chrome-stable --ozone-platform=wayland
from the command line, it works.
If you only build for yourself, look here: https://bbs.archlinux.org/viewtopic.php?pid=1000549#p1000549
Like others I had noticed the very long time on the final compression in recent months that was taking a minute or so. I looked at the thread at https://www.reddit.com/r/archlinux/comments/1bwyv1q/how_do_you_fix_zstds_slowness/ and decided to change the COMPRESSZST in .config/pacman/makepkg.conf to COMPRESSZST=(zstd -c -T4 -8 -) and now when I run the chrome browser build it takes a second or so to do the compression. The final .zst file is now 130M instead of the 112M when using the standard ultra compression, but for me the file size is less important than the very long compression time. I thought I would pass this on in case others might wish to do something similar.
ibus not works in wayland mode, even set "--gtk-version=4" option.. "--gtk-version=4" option works well in previous version.
In Chrome Stable version 123, the RawDraw option will result in blank screen. This problem has reproduced in my GNOME 45/46 environment with Mutter 45/46, my machine spec is Intel UHD 620 with Mesa 24. Just for a reference.
Has anyone experienced save/open file picker dialogs not opening after updating to 123.0.6312? Same problem on Chrome and Chromium. I have xdg-desktop-portal installed. It's possible I caused this by messing around with something else and not the update. The debug log says:
[145164:145196:0326/161840.429311:VERBOSE1:bus.cc(916)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s
string "org.freedesktop.portal.Desktop"
[145164:145196:0326/161840.522535:VERBOSE1:object_proxy.cc(513)] Signal received: message_type: MESSAGE_SIGNAL
destination: :1.8953
path: /org/freedesktop/portal/desktop/request/1_8953/handle_2
interface: org.freedesktop.portal.Request
member: Response
sender: :1.12
signature: ua{sv}
serial: 220
uint32_t 2
array [
dict entry {
string "uris"
variant array [
]
}
]
@nfs did you install the base-devel
package? It's a requirement for building AUR packages.
When I try to build this, I get:
==> ERROR: Cannot find the debugedit binary required for including source files in debug packages.
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.