AUR (en) - chromium-dev

Search Criteria

Package Details: chromium-dev 126.0.6423.2-1

Git Clone URL:	https://aur.archlinux.org/chromium-dev.git (read-only, click to copy)
Package Base:	chromium-dev
Description:	The open-source project behind Google Chrome (Dev Channel)
Upstream URL:	http://www.chromium.org
Keywords:	browser web
Licenses:	BSD
Submitter:	None
Maintainer:	sl1pkn07
Last Packager:	sl1pkn07
Votes:	158
Popularity:	0.005340
First Submitted:	2010-05-17 09:04 (UTC)
Last Updated:	2024-04-21 19:18 (UTC)

Git Clone URL:

https://aur.archlinux.org/chromium-dev.git (read-only, click to copy)

Package Base:

chromium-dev

Description:

The open-source project behind Google Chrome (Dev Channel)

Upstream URL:

http://www.chromium.org

Keywords:

browser web

Licenses:

BSD

Submitter:

None

Maintainer:

sl1pkn07

Last Packager:

sl1pkn07

Votes:

158

Popularity:

0.005340

First Submitted:

2010-05-17 09:04 (UTC)

Last Updated:

2024-04-21 19:18 (UTC)

Latest Comments

« First ‹ Previous 1 .. 132 133 134 135 136 137 138 139 140 141 142 .. 152 Next › Last »

<deleted-account> commented on 2010-12-05 15:47 (UTC)

So, what is the solution of the problem about libGLESv2? Thanks ;) Now, i'm using the package of chromium from official repository :(

Det commented on 2010-12-05 08:31 (UTC)

Ahhh, of course it was _Gles2_ not _Egl_. Ok then, my fault the whole thing then. I dunno how I got the idea that "libGLESv2.so" would suddenly be a Mesa Egl component but no harm done... except for archtaku I guess. Sorry about that ;).

<deleted-account> commented on 2010-12-05 08:19 (UTC)

alphazo problem is with missing libGLESv2.so, not libffmpegsumo.so. I don't know how he managed to pull this dependency though, looking at media/media.gyp, the default backend is x11, not GLES. I have neither of these shared libraries on my system and chromium is running fine (it complains about libffmpegfumo.so, but that's fine). Maybe it has something to do with enabling experimental 3D/acceleration features (I don't use them).

Det commented on 2010-12-05 08:07 (UTC)

So when alphazo said he cannot start chromium because of the two errors - Mesa Egl and libffmpegsumo.so - he actually could?

<deleted-account> commented on 2010-12-05 08:00 (UTC)

Just to clear things up. libffmpegsumo.so is entirely optional and it's absence can't cause any failure.

Koshon commented on 2010-12-04 22:41 (UTC)

to Det: it's not for update, only for who want.

Det commented on 2010-12-04 19:28 (UTC)

Stay in your pants, it's not about being hard to understand. I'm just wondering how can you bypass the Mesa Egl requirement by copying libffmpegsumo.so (Ffmpeg component) to the install folder.

terminalmage commented on 2010-12-04 18:56 (UTC)

Det: Because it _was_ less work. I already had chromium installed, and even if I didn't, installing it and copying the .so _is_ less work than installing one package and recompiling another. I'm fully aware it's not the cleanest method of resolving the issue, which is why I added that it was a dirty hack. Why is this so hard for you to understand?

Det commented on 2010-12-04 18:35 (UTC)

archtaku: Hemm, in that case I _really_ wonder why did you say "but less work than installing an extra package and rebuilding mesa." Koshon: if you mean this package should be updated, you are wrong. Check here the latest stable/beta/_dev_ channel releases: http://googlechromereleases.blogspot.com/