Does anyone know how to change the startup flags/arguments? I'm trying to get the browser to start with --purge-memory-button
Search Criteria
Package Details: google-chrome-dev 133.0.6847.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: | 654 |
Popularity: | 1.35 |
First Submitted: | 2009-06-05 21:02 (UTC) |
Last Updated: | 2024-11-21 19:42 (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 (40)
- 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-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)
- hub-young (requires google-chrome) (optional)
- Show 20 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 60 61 62 63 64 65 66 67 68 69 70 .. 91 Next › Last »
<deleted-account> commented on 2011-07-11 19:37 (UTC)
Det commented on 2011-06-17 13:39 (UTC)
Nobody's hurt or anything :).
t3ddy commented on 2011-06-17 13:02 (UTC)
you're right, I'm a bit off these days :S
Det commented on 2011-06-17 12:35 (UTC)
The .desktop file says "Icon=google-chrome" - so no icons are needed in the root of /usr/share/icons.
<deleted-account> commented on 2011-06-17 00:51 (UTC)
Dev has been updated to version 14, this needs to be updated.
t3ddy commented on 2011-06-15 12:41 (UTC)
I think this line:
cp -v "$pkgdir/opt/google/chrome/product_logo_256.png" "$pkgdir/usr/share/icons/google-chrome.png"
is needed by .desktop
for the other two, I've replaced them
Det commented on 2011-06-14 21:23 (UTC)
Hey, again. These lines:
install -d "$pkgdir/usr/share/icons/hicolor/${i}x${i}/apps"
cp -v "$pkgdir/opt/google/chrome/product_logo_${i}.png" "$pkgdir/usr/share/icons/hicolor/${i}x${i}/apps/google-chrome.png"
could be replaced with just:
install -D (-v) "$pkgdir/opt/google/chrome/product_logo_${i}.png" "$pkgdir/usr/share/icons/hicolor/${i}x${i}/apps/google-chrome.png"
Also is this really needed?:
cp -v "$pkgdir/opt/google/chrome/product_logo_256.png" "$pkgdir/usr/share/icons/google-chrome.png"
t3ddy commented on 2011-06-14 21:13 (UTC)
I've fixed the formatting, is it working for you now?
anish commented on 2011-06-14 20:34 (UTC)
==> Validating source files with md5sums...
google-chrome-unstable_current_amd64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
This happens to me with every single update, every single time
t3ddy commented on 2011-06-11 15:54 (UTC)
I don't think it's something crucial, although I could fix it... I'll see
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.