Package Details: google-chrome-dev 128.0.6559.0-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: 649
Popularity: 0.33
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-06-27 21:11 (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 .. 67 68 69 70 71 72 73 74 75 76 77 .. 91 Next › Last »

Det commented on 2011-01-21 14:44 (UTC)

And that mattoufoutu's issue seems to be the cause of updated ffmpeg (which increased the libraries' versions) because Chrome uses the system ffmpeg. There's really nothing to do expect to wait for the next Dev Chrome and see if it's built for the new libavutil. @scio, don't be so short-sighted. There are cases when symlinking is the only available solution and this is one of them (dunno how much libavutil even affects Chrome, though). Another case that happened to me was during the openssl/libgcrypt transition (back in April 2010). Pacman was rendered totally useless because it was built for the former libraries and I (of course) had removed the former versions of libgcrypt/openssl from the pacman cache with 'pacman -Sc' (so I neither could I manually place the files from the tarballs). Well, my browser wasn't working either so fetching the former versions from the internets was also out. So what did I figure to do next? Ah yes, _symlinking_, that's the one. So I temporarily symlinked the new libs to the old ones, updated pacman (along with everything else) and finally removed the symlinks. Not something you'd do in normal circumstances but instead something that you might occasionally do when all other options have gone out.

scio commented on 2011-01-21 14:04 (UTC)

@mattoufoutu: that is a terrible way to fix that problem. That means that the package needs to be rebuilt against your new library. Symlinking a library to a different version number will only cause problems.

Det commented on 2011-01-21 14:02 (UTC)

Maybe some setting or cache in chromium's or xdg-util's side? Eg. you could try moving out the Chromium settings folder and then checking whether the problem persists ~/.config/chromium? The installation files should all be automatically replaced upon updating (leaving no traces of the former installation folder path) so reinstalling this thing shouldn't help for that matter.

<deleted-account> commented on 2011-01-21 14:00 (UTC)

At startup, google-chrome is looking for the libavutil library in "/usr/lib/libavutil.so.49", but the correct file is at "/usr/lib/libavutil.so.50", creating a symlink solves the problem.

t3ddy commented on 2011-01-21 12:57 (UTC)

It seems all right then. I don't know what could cause the problem.

Weegee commented on 2011-01-20 21:51 (UTC)

lrwxrwxrwx 1 root root 32 20. Jan 22:48 /usr/bin/google-chrome -> /opt/google/chrome/google-chrome

t3ddy commented on 2011-01-20 21:27 (UTC)

.desktop is fine "ls -l /usr/bin/google-chrome" what gives you?

Weegee commented on 2011-01-20 21:19 (UTC)

Exec=/opt/google/chrome/google-chrome %U

t3ddy commented on 2011-01-20 21:05 (UTC)

And what about the Exec line in the .desktop?

Weegee commented on 2011-01-20 20:35 (UTC)

Nah, I've built the package with makepkg (using the tarball), but it still didn't work :/

« First ‹ Previous 1 .. 67 68 69 70 71 72 73 74 75 76 77 .. 91 Next › Last »