Package Details: google-chrome-dev 133.0.6876.4-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.04
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-12-05 16:18 (UTC)

Dependencies (12)

Required by (41)

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 .. 52 53 54 55 56 57 58 59 60 61 62 .. 91 Next › Last »

ipha commented on 2012-03-11 08:41 (UTC)

It appears as though it is now linked against libpng15 > ldd chrome | grep libpng libpng15.so.15 => /usr/lib/libpng15.so.15 (0x00007fc5dd9ee000)

Det commented on 2012-03-09 13:50 (UTC)

Yeah. Actually it's somehow managing to use libpng15.

<deleted-account> commented on 2012-03-09 04:23 (UTC)

Why is libpng12 a dependency? I am ignoring that dependency and am having no issues.

xduugu commented on 2012-03-08 14:31 (UTC)

Could you please change the openssl-0.9.8 dependency from openssl-compatibility[1] to openssl098[2], since the former uses a build from 2010 which contains security issues. Thanks. [1] https://aur.archlinux.org/packages.php?ID=36308 [2] https://aur.archlinux.org/packages.php?ID=40574

Det commented on 2012-03-01 13:47 (UTC)

The 64-bit flashplugin optdep should be removed then.

Ner0 commented on 2012-03-01 09:24 (UTC)

Could you add openssl-compatibility as a dependency, as built-in Pepper Flash requires it? ldd /opt/google/chrome/PepperFlash/libpepflashplayer.so libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0x00007f651962f000)

roheim commented on 2012-03-01 01:45 (UTC)

I deleted ~/.cache/google-chrome and ~/.config/google-chrome and it was still failing. As a workaround I went to chrome://plugins/ and disabled PepperFlash as said below.

<deleted-account> commented on 2012-03-01 00:29 (UTC)

for me it crashed upon launch. Deleting ~/.config/google-chrome/ fixed it for me.

Det commented on 2012-02-29 20:09 (UTC)

Dudes. Just disable the 64-bit pepper flash.

t3ddy commented on 2012-02-29 19:27 (UTC)

That's strange, have you tried reinstalling chrome?

« First ‹ Previous 1 .. 52 53 54 55 56 57 58 59 60 61 62 .. 91 Next › Last »