Package Details: google-chrome-dev 133.0.6847.2-1

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.44
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-11-21 19:42 (UTC)

Dependencies (12)

Required by (40)

Sources (3)

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:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-unstable" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.

Latest Comments

« First ‹ Previous 1 .. 47 48 49 50 51 52 53 54 55 56 57 .. 91 Next › Last »

xzy3186 commented on 2012-06-20 11:21 (UTC)

The same error for 32bit. An easy way to get this around is adding "rm ./opt/google/chrome/nacl_irt_x86_64.nexe" to the first line of package() in PKGBUILD.

t3ddy commented on 2012-06-20 10:55 (UTC)

Since I don't have a 32-bit machine, can you try this: http://pastebin.com/jVe89qy2 Thanks

<deleted-account> commented on 2012-06-20 10:47 (UTC)

Same problem with new version.

t3ddy commented on 2012-06-16 17:35 (UTC)

For some (strange) reason there's a 64-bit executable into 32-bit rpm. Let's see if in the next release it'll be still present, in that case I'll remove it using the pkgbuild.

<deleted-account> commented on 2012-06-16 11:23 (UTC)

Same error here... strip:./opt/google/chrome/nacl_irt_x86_64.nexe: File format not recognized /usr/bin/fakeroot: line 181: 19557 Segnale 1 definito dall'utente FAKEROOTKEY=$FAKEROOTKEY LD_LIBRARY_PATH="$PATHS" LD_PRELOAD="$LIB" "$@" Is there a workaround?

<deleted-account> commented on 2012-06-13 05:45 (UTC)

-> Stripping unneeded symbols from binaries and libraries... strip:./opt/google/chrome/nacl_irt_x86_64.nexe: File format not recognized /usr/bin/fakeroot: line 181: 13402 User defined signal 1 FAKEROOTKEY=$FAKEROOTKEY LD_LIBRARY_PATH="$PATHS" LD_PRELOAD="$LIB" "$@" ==> ERROR: Makepkg was unable to build google-chrome-dev.

<deleted-account> commented on 2012-06-13 01:21 (UTC)

pacman -Q | grep yaourt yaourt 1.1-1 ==> ERROR: An unknown error has occurred. Exiting... /usr/lib/yaourt/pkgbuild.sh: line 200: 2757 User defined signal 1 PKGDEST="$YPKGDEST" makepkg "${MAKEPKG_ARG[@]}" -s -f -p ./PKGBUILD ==> ERROR: Makepkg was unable to build google-chrome-dev.

t3ddy commented on 2012-06-02 14:08 (UTC)

I've added the workaround to the pkgbuild, thanks rememberthemer.

<deleted-account> commented on 2012-06-02 13:05 (UTC)

A better solution to the udev issue is to put the link in /opt/google/chrome. ln -sf /usr/lib/libudev.so.1.0.1 /opt/google/chrome/libudev.so.0 Less chance of spurious junk being left behind + no chance of programs being built with an rpath to the wrong libudev soname. Even better - add this to the package please.