Yeah, as I said, I tried the (latest) Stable/Beta/Dev Channel Chromes and it didn't work with any of them. Does it work for you or anybody else? I mean my system is (of course) up-to-date and every time I tried with a _clean_ settings directory (.config/chromium).
Search Criteria
Package Details: google-chrome-dev 133.0.6876.4-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.04 |
First Submitted: | 2009-06-05 21:02 (UTC) |
Last Updated: | 2024-12-05 16:18 (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-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)
- ice-ssb (requires google-chrome) (optional)
- ice-ssb-git (requires google-chrome) (optional)
- kget-integrator-chrome (requires google-chrome) (optional)
- lastpass (requires google-chrome) (optional)
- marp-cli (requires google-chrome) (optional)
- nfauthenticationkey (requires google-chrome) (optional)
- pearson-reader-plus-full-lang (requires google-chrome) (optional)
- pennywise-bin (requires google-chrome) (optional)
- pt-plugin-plus-bin (requires google-chrome) (optional)
- pt-plugin-plus-git (requires google-chrome) (optional)
- python-nativemessaging-ng (requires google-chrome) (optional)
- python-webdriver-manager (requires google-chrome) (check)
- quick-n-easy-web-builder-10 (requires google-chrome) (optional)
- sshcode-bin (requires google-chrome) (optional)
- uget-integrator-chrome (requires google-chrome) (optional)
- upload-gphotos (requires google-chrome) (optional)
- vlc-protocol (requires google-chrome) (optional)
- web-media-controller-mpris (requires google-chrome) (optional)
- web-media-controller-mpris-git (requires google-chrome) (optional)
- webchanges (requires google-chrome) (optional)
- webui-aria2-git (requires google-chrome) (optional)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 73 74 75 76 77 78 79 80 81 82 83 .. 91 Next › Last »
Det commented on 2010-12-22 16:24 (UTC)
scio commented on 2010-12-22 16:02 (UTC)
@Det: I'm not sure what your problem is, as of 5.0.375.9[1] flash is built in and enabled by default. There is no need to add command line arguments (which have also been replaced with about:flags).
You don't need to do anything to make flash work. Install google-chrome-dev, and it should work out of the box. If your version of chrome is using flashplugin, you either have a very old version or something is not built correctly.
[1]http://googlechromereleases.blogspot.com/2010/04/dev-channel-update_12.html
Det commented on 2010-12-22 15:34 (UTC)
@scio, I didn't really get the ending of your message and the other part was mostly repeating your former one but ok, then. I get that. It's just that now that I try viewing (for the second time) anything 'flashy', I just keep getting the "Missing Plug-in" message (whether Chrome was started with "--enable-internal-flash" or not). I get this with the Beta and Stable Channel Chrome's too.
So if you could just elaborate on how Chrome's builtin Flash works instead of saying how it does "NOT" work, then that'd be great.
scio commented on 2010-12-22 15:04 (UTC)
@Det: google-chrome-dev has built in flash, it does NOT use flashplugin and thus doesn't need flashplugin as an optdepends.
I can't say for the others, I don't remember which versions have it or not. You are posting this on the google-chrome-dev package so that is what I am referring to.
scio commented on 2010-12-22 14:37 (UTC)
@Det: flash does come with the linux version of chrome, it does NOT use flashplugin.
scio commented on 2010-12-10 13:13 (UTC)
@x-demon: You could try asking bdheeman, he maintains the chromium packages.
<deleted-account> commented on 2010-12-10 12:49 (UTC)
anyone want to maintain chrome packages? Please write to me at lex.io
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.