Couple things:
1. I've been using the beta and dev versions with pepper flash without openssl098 and no issues, so not sure if that is still needed. (maybe some feature I haven't used)
2. I have the feeling that I'm the only person getting "segmentation fault" errors with the dev version (because I haven't found info about it). It's been happening to me for a past 5 or so versions. Beta and Stable versions work like a charm. I'll try again when this version gets updated.
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.47 |
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 .. 41 42 43 44 45 46 47 48 49 50 51 .. 91 Next › Last »
martincanaval commented on 2013-01-11 03:31 (UTC)
Det commented on 2012-12-19 13:13 (UTC)
LOL. Accident..
captainju commented on 2012-12-14 07:32 (UTC)
error 404
A new version is available
http://googlechromereleases.blogspot.fr/2012/12/dev-channel-update_13.html
Det commented on 2012-12-11 16:00 (UTC)
Mh, what that command does (without the ";" or "&&" in between) is that it tries to remove the non-existing "rm" in addition to the actual files (you're also specifying '-f' twice).
So it's either this:
rm -f "$pkgdir/opt/google/chrome/nacl_irt_x86_64.nexe" "$pkgdir/opt/google/chrome/nacl_irt_srpc_x86_64.nexe"
..or in two lines as t3ddy finally did there.
mamamia88 commented on 2012-12-11 14:22 (UTC)
Don't ask me why but line 45 has to read all one line otherwise it doesn't work
rm -f "$pkgdir/opt/google/chrome/nacl_irt_x86_64.nexe" rm -f "$pkgdir/opt/google/chrome/nacl_irt_srpc_x86_64.nexe"
Det commented on 2012-12-08 19:37 (UTC)
Ooh, it's some "srpc" binary. Yeah. Well. He should do that. Maybe even some asterisk (*) setup to deal with those in the feature versions too.
Flagging.
bb010g commented on 2012-12-08 19:08 (UTC)
I've still got the same problem as ninian (with same error). Fails in both aura and manual building.
Det commented on 2012-12-07 22:35 (UTC)
@ninian, this was fixed back when you posted the same thing for the second time.
ninian commented on 2012-12-07 19:53 (UTC)
Adding this after line 45 in the PKGBUILD seems to do the trick (on my 32-bit system):
rm -f "$pkgdir/opt/google/chrome/nacl_irt_srpc_x86_64.nexe"
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.