Package Details: google-chrome-beta 132.0.6834.46-1

Git Clone URL: https://aur.archlinux.org/google-chrome-beta.git (read-only, click to copy)
Package Base: google-chrome-beta
Description: The popular web browser by Google (Beta Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Provides: google-chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 357
Popularity: 0.68
First Submitted: 2009-12-08 19:09 (UTC)
Last Updated: 2024-12-11 20:27 (UTC)

Dependencies (12)

Required by (42)

Sources (3)

Pinned Comments

gromit commented on 2023-11-30 17:09 (UTC)

When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Beta updates" tag in Release blog for this.

You can also run this command to obtain the version string for the latest chrome beta version:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-beta" | \
     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 .. 7 8 9 10 11 12 13 14 15 16 17 .. 27 Next › Last »

WoefulDerelict commented on 2014-06-03 23:59 (UTC)

Package is broken by updating to usb_modeswitch2.2.0-1. Chrome exits with an error stating it is unable to find libudev.so.O Package flagged out of date.

obfu commented on 2014-05-27 20:13 (UTC)

Current Version and MD5 sums: beta: 36.0.1985.32 fdd314798af0fdcf48c4fa2a7003109f google-chrome-beta_current_amd64.deb 9c7307a5f3fe4edfa83ab566dfbd0d0e google-chrome-beta_current_i386.deb

bulletmark commented on 2014-04-27 06:56 (UTC)

OK, found the answer to my own question below. This is a bug in the current debian package. The issue and simple fix is shown at https://code.google.com/p/chromium/issues/detail?id=363358.

bulletmark commented on 2014-04-27 06:19 (UTC)

Anybody else using chrome-beta on Arch x64 - does google-talk-plugin currently work for you? It doesn't even appear in chrome://plugins/ for me.

bond0087 commented on 2014-04-25 17:07 (UTC)

For anyone else out there using Docky as a taskbar and having Google Chrome show up with the Google Keep icon rather than the correct icon: I fixed it by adding the following line to /usr/share/applications/google-chrome-beta.desktop : StartupWMClass=google-chrome-beta

kerberizer commented on 2014-04-18 12:05 (UTC)

@Det, thanks for taking the time to explain it. I haven't quite realized a few things and they are certainly good to know -- I'll keep them in mind.

Det commented on 2014-04-18 11:55 (UTC)

No, I didn't think you were being ungrateful, it's just the best way to make sure the maintainer gets notified. In case a package doesn't build (even with special instructions), you are allowed to flag it out-of-date, since that's still the only button we got: https://bugs.archlinux.org/task/18829 I usually, if I get a lot of comment notifications from many different packages, just delete all of them and take care of the packages that have been flagged anyway. So feel free to flag it, if it doesn't work. E: Don't think of it as lazy just because we've made it such a simple function.

kerberizer commented on 2014-04-18 11:35 (UTC)

@Det, if that comment was directed me: flagging a package out-of-date, especially when the package is in fact not outdated, is IMHO a rather non-descriptive and even confusing (not to mention lazy) way to notify the maintainer of some technical problem. My only desire was to be as helpful as possible, and I'm sorry if I might have offended or otherwise annoyed you somehow -- this certainly has not been my intention. In any case, many thanks indeed for maintaining these packages -- I know too well from my own experience how this can be a rather ungrateful task. ;)

Det commented on 2014-04-18 09:26 (UTC)

If there really was a problem with it, why couldn't you just _flag_ it out-of-date?