Package Details: chromium-snapshot-bin 106.0.5203.0.r1028210-1

Git Clone URL: (read-only, click to copy)
Package Base: chromium-snapshot-bin
Description: The open-source project behind Google Chrome (Latest Snapshot)
Upstream URL:
Keywords: browser web
Licenses: BSD
Provides: chromium
Submitter: Det
Maintainer: mrxx
Last Packager: mrxx
Votes: 497
Popularity: 0.105582
First Submitted: 2015-04-20 12:12 (UTC)
Last Updated: 2022-07-26 15:10 (UTC)

Dependencies (11)

Required by (102)

Sources (12)

Pinned Comments

Det commented on 2017-03-30 10:20 (UTC) (edited on 2017-12-13 23:06 (UTC) by Det)

Do not flag this package out-of-date.

It updates automatically on each install.

Latest Comments

DAC324 commented on 2021-10-02 12:32 (UTC)

Looks like this chromium version also does not like --force-device-scale-factor. If set to values greater than 1, maximizing chromium leads to an overscan so that the window borders are outside the visible screen area.

If resized to fit the screen, the window controls at the right (such as minimize, restore, maximize, close) are not working. If you click on these, it is recognized as a click on the desktop background.

Workaround: Do not use --force-device-scale-factor.

DAC324 commented on 2021-09-28 07:33 (UTC) (edited on 2021-09-28 12:48 (UTC) by DAC324)

By the way,this chromium version does not play ANY video, neither on YouTube nor Facebook, nor other pages. If you open any YouTube page, it does not even get displayed in chrome://media-internals at all so I assume that this behavior is intended. Debug information from YouTube:

  "ns": "yt",
  "el": "detailpage",
  "cpn": "e5K7YIOzxQLuTMf4",
  "docid": "8sChEPcm0zM",
  "ver": 2,
  "referrer": "",
  "cmt": "0",
  "ei": "JZVRYdSWGsLdgAf1xan4Aw",
  "fs": "0",
  "rt": "35551.278",
  "of": "pZTO9c9_sFOHP0HjjgMIeg",
  "euri": "",
  "lact": 6,
  "cl": "398834183",
  "mos": 0,
  "state": "80",
  "volume": 100,
  "cbr": "Chrome",
  "cbrver": "96.0.4643.0",
  "c": "WEB",
  "cver": "2.20210924.00.00",
  "cplayer": "UNIPLAYER",
  "cos": "X11",
  "cplatform": "DESKTOP",
  "hl": "de_DE",
  "cr": "DE",
  "len": "523",
  "fexp": "23748146,23858058,23958718,23983296,23986025,24001373,24002022,24002025,24002923,24004644,24007246,24045469,24045470,24064555,24069678,24080738,24082661,24083162,24083163,24083188,24083189,24094715,24101842,24106549",
  "muted": "0",
  "vct": "0.000",
  "vd": "NaN",
  "vpl": "",
  "vbu": "",
  "vpa": "1",
  "vsk": "0",
  "ven": "0",
  "vpr": "1",
  "vrs": "0",
  "vns": "0",
  "vec": "null",
  "vemsg": "",
  "vvol": "1",
  "vdom": "1",
  "vsrc": "0",
  "vw": "1280",
  "vh": "720",
  "debug_error": "{\"errorCode\":\"html5.missingapi\",\"errorMessage\":\"Dieses Videoformat wird nicht unterstützt.\",\"GC\":\"HTML5_NO_AVAILABLE_FORMATS_FALLBACK\",\"ai\":\"\",\"OE\":\"nocodecs.1;a6s.0\"}",
  "ismb": 10650000,
  "relative_loudness": "-1.260",
  "user_qual": 0,
  "release_version": "youtube.player.web_20210922_1_RC1",
  "debug_videoId": "8sChEPcm0zM",
  "0sz": "false",
  "op": "",
  "yof": "true",
  "dis": "",
  "gpu": "ANGLE_(NVIDIA_Corporation,_GeForce_GTX_550_Ti/PCIe/SSE2,_OpenGL_4.5.0_NVIDIA_390.144)",
  "debug_playbackQuality": "unknown",
  "debug_date": "Tue Sep 28 2021 09:32:58 GMT+0200 (Mitteleuropäische Sommerzeit)"

DAC324 commented on 2021-08-31 18:07 (UTC) (edited on 2021-08-31 18:09 (UTC) by DAC324)

@intrnl: Meanwhile, I have switched to pipewire. However, to get audio in chromium working, it might be necessary to start the browser with --disable-features=AudioServiceSandbox

See for additional details.

intrnl commented on 2021-07-24 09:06 (UTC)

@DAC324 I'm curious, are you still having issues with pulseaudio? I'm encountering the same and wonder if it's just a me thing.

mrxx commented on 2021-05-17 13:18 (UTC)

Added quotes to the user flags while stripping comment lines.

DAC324 commented on 2021-05-17 11:47 (UTC)

Current snapshot (92.0.4511.0) has a problem with pulseaudio:

Failed to create secure directory (/run/user/1000/pulse): Operation not permitted
The futex facility returned an unexpected error code.
Received signal 6
#0 0x5638bf3cabf9 (/opt/chromium-snapshot/chrome+0x6523bf8)
#1 0x5638bf3373d3 (/opt/chromium-snapshot/chrome+0x64903d2)
#2 0x5638bf3ca721 (/opt/chromium-snapshot/chrome+0x6523720)
#3 0x7f054d6af960 (/usr/lib/
#4 0x7f054c86bef5 __GI_raise
#5 0x7f054c855862 __GI_abort
#6 0x7f054c8adf38 __libc_message
#7 0x7f054c8adf6a __GI___libc_fatal
#8 0x7f054d6b1960 __futex_abstimed_wait_common64
#9 0x7f054d6ab260 __pthread_cond_wait
#10 0x5638bf3d7a7f (/opt/chromium-snapshot/chrome+0x6530a7e)
#11 0x5638bf3d8351 (/opt/chromium-snapshot/chrome+0x6531350)
#12 0x5638bf3d7faf (/opt/chromium-snapshot/chrome+0x6530fae)
#13 0x5638bf34f516 (/opt/chromium-snapshot/chrome+0x64a8515)
#14 0x5638bf39f097 (/opt/chromium-snapshot/chrome+0x64f8096)
#15 0x5638bf3705bb (/opt/chromium-snapshot/chrome+0x64c95ba)
#16 0x5638bf29dc8b (/opt/chromium-snapshot/chrome+0x63f6c8a)
#17 0x5638bf2d384c (/opt/chromium-snapshot/chrome+0x642c84b)
#18 0x5638bf2d4b02 (/opt/chromium-snapshot/chrome+0x642db01)
#19 0x5638bf2d213d (/opt/chromium-snapshot/chrome+0x642b13c)
#20 0x5638bf2d2add (/opt/chromium-snapshot/chrome+0x642badc)
#21 0x5638bc20e249 ChromeMain
#22 0x7f054c856b25 __libc_start_main
#23 0x5638bc20dfea _start
  r8: 0000000000000000  r9: 00007ffc1b5d89d0 r10: 0000000000000008 r11: 0000000000000246
 r12: 00007ffc1b5d8c30 r13: 0000000000001000 r14: 0000000000000000 r15: 00007f054a16f000
  di: 0000000000000002  si: 00007ffc1b5d89d0  bp: 00007ffc1b5d8cf0  bx: 00007f054b7e2d00
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007f054c86bef5  sp: 00007ffc1b5d89d0
  ip: 00007f054c86bef5 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]

DAC324 commented on 2021-05-17 10:25 (UTC) (edited on 2021-05-17 10:25 (UTC) by DAC324)

@mrxx: Reason why the user agent is so important for me: Google as well as some other services refuse to work properly if the browser's user agent is not recognized.

As for the comments in ~/.config/chromium-flag.conf to be handled correctly: Replace the cat command by grep -v '^#' where the file is read:

# Allow users to override command-line options
if [[ -f ~/.config/chromium-flags.conf ]]; then
   CHROMIUM_USER_FLAGS="$(grep -v '^#' ~/.config/chromium-flags.conf)"

This causes all lines starting with one single # char to be ignored.

DAC324 commented on 2021-05-17 10:06 (UTC)

@mrxx: Indeed, changing the call to Chrome in /usr/bin/chromium-snapshot-bin to

exec /opt/chromium-snapshot/chrome "$CHROMIUM_USER_FLAGS" "$@"

does the trick. With this, I can keep my user agent string in ~/.config/chromium-flags.conf as usual :)

mrxx commented on 2021-05-17 10:01 (UTC)

Please do not call /opt/chromium-snapshot/chrome directly. Use the wrapper and quote the parameter(s):

chromium-snapshot-bin "$TESTFLAG"

DAC324 commented on 2021-05-17 09:54 (UTC) (edited on 2021-05-17 10:02 (UTC) by DAC324)

@mrxx Thanks for updating so quickly. Unfortunately, at least here, it does not help. As soon as I add the user agent line to ~/.config/chromium-flag.conf, I get the same behavior again. The user agent is truncated at the first space, and the remainder is treated as separate commands.

I investigated a little bit further.

The launcher reads ~/.config/chromium-flags.conf and puts its contents into one single variable which is then passed to chrome on the command line. So far, so good, but transferring something like

--user-agent="Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36"

into a variable seems to fail, perhaps because of the presence of double quotes and spaces in the string. When I start Chrome from the command line with

exec /opt/chromium-snapshot/chrome --user-agent="Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36"

the flag is correctly recognized. However, when I first transfer the flag in a variable, let's say like

TESTFLAG="--user-agent=\"Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36\""

I get the correct contents:

--user-agent="Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36"

But when I now try to start Chrome with that variable

exec /opt/chromium-snapshot/chrome $TESTFLAG "$@"

it fails to pass the contents of $TESTFLAG correctly to Chrome but stops at the first space.

Looks like /usr/bin/chromium-snapshot-bin needs to be amended. The line

exec /opt/chromium-snapshot/chrome $CHROMIUM_USER_FLAGS "$@"

has to be amended by double quotes like

exec /opt/chromium-snapshot/chrome "$CHROMIUM_USER_FLAGS" "$@"

mrxx commented on 2021-05-17 09:23 (UTC)

Thanks for pointing this out, DAC324. I've added quotes to the launch parameters.

DAC324 commented on 2021-05-17 08:59 (UTC)

The launcher seems to be unable to handle comments in ~/.config/chromium-flags.conf, and it is also unable to handle spaces in any of the command line flags.

For example,

--user-agent="Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36"

causes the launcher to stop reading the user agent string at the first space and passing everything else to the browser separately. You end up with a user agent string of "Mozilla/5.0 and a bunch of pages opened with all the other parts of this user agent string as URLs to be opened. Escaping the spaces does not help. What can I do to pass the user agent nevertheless to the browser?

ChrisLane commented on 2020-11-12 09:33 (UTC)

Note to anyone using this for the new Wayland support: You'll need to run using the following flags for a native Wayland experience --enable-features=UseOzonePlatform --ozone-platform=wayland

mrxx commented on 2020-05-15 19:14 (UTC) (edited on 2020-05-16 00:51 (UTC) by mrxx)

Thanks, morgenstern. I've changed the opt-dependency to 'flashplugin'.

morgenstern commented on 2020-05-09 23:21 (UTC)

Just a small note - pepper-flash has been moved out of the AUR and is now a part of the flashplugin package in the extra repo.

treeshateorcs commented on 2020-04-20 22:53 (UTC)

okay, found it. to make this your default browser, issue the following commands

xdg-mime default chromium-snapshot-bin.desktop text/html
update-mime-database ~/.local/share/mime

treeshateorcs commented on 2020-04-20 22:32 (UTC)

how do i make this my default browser again?

mrxx commented on 2019-07-27 13:41 (UTC)

Updated to v78, removed gconf as dependency.

shoober420 commented on 2019-07-18 17:43 (UTC)

Awesome, thanks mrxx and Det. Keeping Arch legit and superior.

Det commented on 2019-07-18 11:16 (UTC)

It was either startup, extra's chromium or namcap.

mrxx commented on 2019-07-18 11:08 (UTC)

shoober420, thanks for your suggestion. The dependency was put there from the previous maintainer and I kept it in order to 'not break things'.

I will remove it in the next release.

shoober420 commented on 2019-07-18 06:54 (UTC)

gconf is supposedly a dependency for this package, but I uninstalled gconf and currently typing this without it installed with a functional Chromium. Is there a particular reason its in the dependencies? gconf is deprecated in favor of dconf, so gconf should be faded out.

krnl0138 commented on 2019-02-08 20:29 (UTC) (edited on 2019-02-09 08:15 (UTC) by krnl0138)

Does anyone else have the problems with ffmpegdemuxer? I can't play some videos that are ok in chromium-dev.

Like those:

[16:29:0717/] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}


Any ideas how to fix it? The only solution i find is to build it manually with adding to folder:

proprietary_codecs = true

ffmpeg_branding = "Chrome"

But i do not want to build it by myself

shoober420 commented on 2018-11-02 16:38 (UTC)

Love this package, I used to manually go to "" and get the snapshot from there. It was a pain in the ass. Thank you for making this.

Det commented on 2018-06-04 17:48 (UTC)

How was that there since February 2017, nobody can say (9174f2cc16e5).

madis commented on 2018-06-04 14:10 (UTC)

Pacman complains about ":" being an invalid character, seems like it might be because kdialog has two of them.

Det commented on 2017-12-05 15:36 (UTC) (edited on 2017-12-13 23:07 (UTC) by Det)

Nice syntax in





  • All
  • of
  • this
and even this
  1. Is now
  2. available
  3. to all

whynothugo commented on 2017-12-05 14:15 (UTC) (edited on 2017-12-05 14:16 (UTC) by whynothugo)

Workaround is as simple as running mksrcinfo to regenrate .SRCINFO. This isn't a VCS package, but a snapshot one, and its expected that these files fall out of sync.

ccython commented on 2017-12-05 14:08 (UTC) (edited on 2017-12-05 14:15 (UTC) by ccython)

Doesnt build for me unfortunately...

:: Installing chromium-snapshot-bin package(s)... <br> :: chromium-snapshot-bin package(s) failed to install. <br> :: ensure package version does not mismatch between .SRCINFO and PKGBUILD <br> :: ensure package name has a VCS suffix if this is a devel package

Any fix? Might also be the fact that im using pacaur. Will try finding out more.

whynothugo commented on 2017-09-28 16:02 (UTC)


Det commented on 2017-09-27 18:29 (UTC)


whynothugo commented on 2017-09-27 15:11 (UTC)

Not building for me: ==> Starting package()... -> Creating directory structure... -> Making it nice... -> Moving contents... gzip: chrome-linux/chrome.1: No such file or directory ==> ERROR: A failure occurred in package().

Det commented on 2017-09-22 07:20 (UTC) (edited on 2017-09-22 07:21 (UTC) by Det)

Yeah, they all do, it seems. Some maintenance. I guess. Or phrakture got hacked again.

ZeroBit commented on 2017-09-22 07:19 (UTC)

PKGBUILD is unavailable. On There is error: 502 Bad Gateway nginx/1.12.1

Det commented on 2017-06-15 08:07 (UTC)

Yeah my mistake. Didn't recall there was 2 packages.

RemoteAdmin commented on 2017-06-15 08:06 (UTC)

@Det Yeah your right. Either libcups or cups. libcups might be better though because only the library is required and not the whole dependency tree of cups. But I will leave that to you ;)

Det commented on 2017-06-15 08:02 (UTC) (edited on 2017-06-15 08:04 (UTC) by Det)

lib32? Probably extra/libcups as deps would be appropriate?

RemoteAdmin commented on 2017-06-15 07:52 (UTC)

"makedepends=('lib32-libcups')" must be added to PKGBUILD. Otherwise chrome won't be able to print the current version and exits with: "ERROR: pkgver() generated an invalid version: chrome-linux/chrome: error while loading shared libraries: cannot open shared object file: No such file or directory"

glapa commented on 2017-04-10 20:35 (UTC)

Why can't I play videos with this package? Gtk2 is not required anymore on behalf of Gtk3

Det commented on 2017-04-03 13:04 (UTC)

Just the "curl -s .." is enough.

Ferik commented on 2017-04-03 13:02 (UTC)

To easily know the last build, launch this command (every 2/3 hours) in the terminal: echo $(curl -s "") and use always this package for updates/install. Bye :)

Det commented on 2017-03-30 10:21 (UTC)

> jab2870 flagged chromium-snapshot-bin out-of-date on 2017-03-30 for the following reason: > > The dev chanel is now on 59. > > The git repo's latest is now so surely the snapshot should be ahead of that Have a look at the absolute latest discussion on the comment section...

Det commented on 2017-03-30 10:20 (UTC) (edited on 2017-12-13 23:06 (UTC) by Det)

Do not flag this package out-of-date.

It updates automatically on each install.

Det commented on 2017-03-09 20:14 (UTC)

The major version bump in Chromium is time-based and otherwise meaningless. Pacaur will fail with every new snapshot anyway. Things like firefox-nightly do the major bumps, because the PKGBUILD doesn't automatically handle those. When it does, you get the latest version whenever you chose to update like any VCS package that doesn't do those bumps either.

noxpo commented on 2017-03-09 19:58 (UTC)

@det, sry for wasting your time man, I just didn't understand from what you wrote that pkgver is supposed to change *in PKGBUILD*. If pkgver is in PKGBUILD and .SRCINFO, it could have also been in other places, for what I understood about AUR, which isn't much. I just saw the v. 58 package actually building a v. 59 and thought: that *can't* be right. Honestly just being a dumbass, sry. Would be nice for folks like me if pkgver was updated on major version changes though, doesn't happen too often.

Det commented on 2017-03-09 08:36 (UTC) (edited on 2017-03-09 08:43 (UTC) by Det)

@noxpo, _listen_ what I'm telling you, because when you flag my package for a wrong reason after I've just told you otherwise (twice), that's when my patience runs out. 1) The problem is Pacaur, not Pacman. Pacman doesn't know, care or understand .SRCINFO (in fact, makepkg uses the same "pacman -U", which was your clue right there). 2) The pkgver() function is *supposed* to update the pkgver beyond what is shown here. There is a new snapshot of Chromium multiple times every hour. You want both of us to update your version every 10-15 minutes or whenever you wish? This is the 3rd time I'm explaining it to you. Have a look here: - - - 3) Complain to Pacaur, not here. In fact, this is how we do it in Arch: Google the message: - - -

noxpo commented on 2017-03-09 07:09 (UTC)

It's pacaur, not pacaur-git. And it does build chromium-snapshot-bin, it just refuses to install it via pacman. I tried building the old fashioned way with makepkg: works, builds the latest 59.xx.. and also changes pkgver in PKGBUILD to 59.xx.. Flagged this package out-of-date since pkgver in the original PKGBUILD is lagging behind now.

Det commented on 2017-03-08 13:24 (UTC) (edited on 2017-03-08 13:27 (UTC) by Det)

Is that the -git version? Either way it's broken, as through the pkgver() function is how all the VCS packages (Git, SVN, etc.) update the pkgver, as well as these nightlies. .SRCINFO is synced with mksrcinfo (community/pkgbuild-introspection) and I really can't see why should pacaur start caring about it during build, especially as much as to abort it.

noxpo commented on 2017-03-08 13:11 (UTC)

The error seems to come from pacaur, sry. After buikding the package archive, it says: :: chromium-snapshot-bin package(s) failed to install. Check .SRCINFO for mismatching data with PKGBUILD. pkgver is 58.xx.. in .SRCINFO and 59.xx.. in PKGBUILD. The actual package archive has the version from PKGBUILD. Installing it with pacman -U works. The header of .SRCINFO is: # Generated by mksrcinfo v8 # Thu Feb 2 13:26:13 UTC 2017

Det commented on 2017-03-08 07:55 (UTC)

Pacman doesn't care about the .SRCINFO, which in fact is in sync until you update with the pkgver(). What's the error?

noxpo commented on 2017-03-07 18:58 (UTC)

pacman throws an error because .SRCINFO und PKGBUILD are not in sync. Probably due to two different package versions (58 vs 59).

Det commented on 2017-01-29 16:48 (UTC) (edited on 2017-02-01 07:49 (UTC) by Det) Something was done about the lib lookup a while back so that even replacing the bundled FFmpeg libs with Chrome's own didn't bring back H.264 (related?: So if you want a bleeding edge H.264 "Chromium", that's

Pontorez commented on 2017-01-29 16:35 (UTC)

Hello, Does anyone know is there a way to enable H.264 video codec in chromium snapshot? page says that this browser doesn't supports MSE & H.264 codecs so I can't view live streams at YouTube using chromium snapshot. Thanks

isiachi commented on 2016-11-16 20:52 (UTC)

Hi, You should remove the line 13 from the chromium-snapshot-bin script. Thanks for the package. Keep on

Det commented on 2016-08-13 07:38 (UTC) (edited on 2016-09-09 10:58 (UTC) by Det)

Dropped i686, as it hasn't been updated since May 18th (51.0.2684.0, r382086). You should be on extra/chromium instead (52.0.2743.85).

Det commented on 2016-08-02 16:23 (UTC)

> Your package chromium-snapshot-bin [1] has been flagged out-of-date by samcv [2]: > 52 has been released. It's a manually updateable latest nightly of Chromium, the base of Chrome.

Styx commented on 2016-05-27 00:21 (UTC)

Anyone else get a page crash on video fullscreen? Usually happens a few times and then begins working correctly.

Det commented on 2016-04-06 23:05 (UTC)


isiachi commented on 2016-04-06 21:36 (UTC) (edited on 2016-04-06 21:38 (UTC) by isiachi)

After discover there's no more build of chromium continuos, I switched to this package. I solved the problem of API by adding this to your chromium-snapshot-bin script: export GOOGLE_API_KEY=AIzaSyDwr302FpOSkGRpLlUpPThNTDPbXcIn_FM export export GOOGLE_DEFAULT_CLIENT_SECRET=0ZChLK6AxeA3Isu96MkwqDR4 I took the value from chromium package of arch. For REFS:

irfan commented on 2016-04-06 10:58 (UTC)

Since 18 March 2016, the Continuous repository is discontinued. See:!searchin/chromium-dev/lkgr/chromium-dev/e4lQRKYbRJY/zNebDVTEuwcJ

Det commented on 2016-02-11 05:45 (UTC)

There are other devs besides those from Google, but you should Google that.

xuiqzy commented on 2016-02-11 00:39 (UTC)

Is it correct that this version doesn't include google API keys and why? I get this warning bar on the top. I thought it's binary and from google, it should have these keys.

Det commented on 2016-01-21 17:26 (UTC) (edited on 2016-01-29 04:26 (UTC) by Det)

Oh. Thanks for the video. I'm not on Arch, so can't try right now. E: So everything should work?

puya commented on 2016-01-21 08:27 (UTC)

And just "chromium-snapshot-bin" not working, dunno why but xprop | grep WM_CLASS return me this worked one: WM_CLASS(STRING) = "/usr/bin/chromium-snapshot-bin", "/usr/bin/chromium-snapshot-bin" -- or just "/usr/bin/chromium-snapshot-bin" - try it. In any case it is not critical, thanks.

puya commented on 2016-01-21 08:10 (UTC)

Yea I have plank and there in specific apps no "Keep In Dock", when StartupWMClass not set. Or finally app docked, but when running there is a duplication of icons. I recorded a video, and then you can clearly seen this bug: Here a some explaination: -- Thanks for fast reply.

Det commented on 2016-01-21 04:04 (UTC)

My man. Thanks.

hamilton commented on 2016-01-21 02:26 (UTC)

"for i in 16 22 24 32 36 48 64 128 256; do" Looks like 36 shouldn't be there.

Det commented on 2016-01-20 22:08 (UTC) (edited on 2016-01-29 04:28 (UTC) by Det)

"Double Google Chrome icon"? Anyway, the icon I would have to pack separately. It only comes in 48x48, and the reason you get a more high-resolution one with "Icon=chromium" is because it then uses the ones from [extra]/chromium. The "StartupWMClass" line I assume works with just "chromium-snapshot-bin"? E: Is 48.0.2535.0.r353757-2 satisfactory? E2: I mean 48.0.2535.0.r353757-3.

puya commented on 2016-01-20 22:07 (UTC)

Please update "chromium-snapshot-bin.desktop" need change this: < Icon=chromium-snapshot-bin --- > Icon=chromium --- it is necessary for the proper display of icon because "chromium-snapshot-bin" does not exist in the different sets of icons. And add > StartupWMClass=/usr/bin/chromium-snapshot-bin this one fix double google chrome icon and "Keep in Dock" in docky and plank. here is already complete config: thanks.

ljrk commented on 2015-10-13 19:04 (UTC)

It seems that gconf is required (now?). At least I needed to install it, otherwise chromium would fail with: /opt/chromium-continuous/chrome: error while loading shared libraries: cannot open shared object file: No such file or directory

Det commented on 2015-08-04 22:43 (UTC)

Build it. When you hear a peculiar clicking sound, that's your jaw dropping.

lucianoar commented on 2015-08-04 22:41 (UTC)

@Det isn't that out of date?

Det commented on 2015-08-04 22:30 (UTC)

Ok, so?

lucianoar commented on 2015-08-04 22:29 (UTC)

pkgver=45.0.2454.0.r338261 in the PKGBUILD, while current version in is 46.0.2472.0.r341720

Det commented on 2015-08-03 18:46 (UTC)

@lucianoar, doushite?

Det commented on 2015-06-24 11:47 (UTC)

laurent.treguier commented on 2015-06-23 08:48 (UTC)

I just tried to install the package and it seems the checksums are wrong... I got it working by changing them from : md5sums=('c0febff6875a5c700507d752647f8f4f' '6203259f7a8fe2fa55b64005a202828d' '537e0b52077bf0a616d0a0c8a79bc9d5') to : md5sums=('6203259f7a8fe2fa55b64005a202828d' '3f2bfd12b55b7153b60ad904207599dd' '537e0b52077bf0a616d0a0c8a79bc9d5')

Det commented on 2015-05-17 21:19 (UTC)

No, like I said, there's a new build pretty much every hour [*]. You wouldn't want all of those anyway. Think of it as an hourly nightly. If you want specific releases, try chromium from [extra], or google-chrome(-beta/-dev) here in the AUR:   -   -   -   - [*] Just compare the time stamps on:   -   -   -   -   -

Det commented on 2015-05-17 21:08 (UTC)

Yeah, it fetches the latest one, whenever you try. It won't be bumped here in the AUR every time, because there's a new build practically every hour.

Det commented on 2015-05-17 18:39 (UTC)

Yeah, well, this is just fetching the latest Google-built/tested build from their servers, and if a fix hasn't been committed all the way (or was reverted), then that's not this package's problem. You can flag this package if the build fails (say, source was moved, or file(s) mentioned in package() no longer exist).

deemde commented on 2015-05-17 18:35 (UTC)

I'm sorry for being too brief. I flagged the package out of date, as the aforementioned rendering-issue fix is not included in the current version of it. Possibly, I misunderstood the flags function.

Det commented on 2015-05-16 10:02 (UTC)

Ok, why are you flagging this?

deemde commented on 2015-05-16 09:38 (UTC)

Text blob-rendering issue has been amended in :

Det commented on 2015-04-20 12:21 (UTC)

Just uploaded the following: • (replaces this package) • (replaces: Changes: • No conflicts with each other or [extra]/chromium • Support Pepper Flash:    - /usr/lib/PepperFlash (chromium-pepper-flash-dev)    - /opt/google/chrome-unstable/PepperFlash (google-chrome-dev) • Custom flags are read directly from: ~/.config/chromium-flags.conf (as per [extra]/chromium: Setting CHROMIUM_FLAGS in /etc is now deprecated.

Det commented on 2015-04-19 13:44 (UTC)

@Shrike, why?

Det commented on 2015-04-07 02:54 (UTC)

Chromium*, and you'd need the Ffmpeg libraries to do that: Apparently 'chromium-codecs-ffmpeg-nonfree-bin' was removed two years ago:

tee commented on 2015-04-07 00:10 (UTC)

Note to everyone: This version of Chrome does NOT support the playback of .mp3 or h264/.mp4.

AlK commented on 2015-04-02 11:21 (UTC)

That's awesome, thanks a lot! Being able to install extra/chromium and chromium-browser-bin was a long awaited feature for me. Cheers

Det commented on 2015-04-01 05:46 (UTC)

Happy April Fools v2015-1 everybody! This package is now pretty much re-written for the year 2015, but some visible changes include: - Rename main script from 'chromium' to 'chromium-browser-bin' (doesn't conflict with extra/chromium anymore) - New pkgver - New pkgdesc - Install in /opt, instead of /usr/lib, and remove extra hackery in main /usr/bin script - New Home page - Remove hard-coded "PKGEXT='.pkg.tar'" from PKGBUILD (see: - Remove 'chrome-wrapper.patch' (unnecessary tweaks) and 'chromium.1.gz' (man already provided) - Arch-specific sources (AUR interface) I'd also like to rename this thing to something like 'chromium-continuous(-bin)' or 'chromium-nightly' (same for 'chromium-nightly', which could be 'chromium-snapshot(-bin)'). However, _I_ can't decide, and did what we do best, and started a discussion about in [aur-general]. If you believe you should be a part of it, or are just interested in having a look, come visit us in:

isiachi commented on 2014-10-15 21:57 (UTC)

The "LinuxGit" and "LinuxGit_x64" are not updated. I suggest to change to "Linux" and "Linux_x64"

Det commented on 2014-10-12 18:59 (UTC)

Would you please update the .AURINFO to fix the source link and include a proper pkgver?

swanson commented on 2014-08-29 05:34 (UTC)

How do you find the font rendering? Is there anything to do about it?

Det commented on 2014-08-14 12:43 (UTC)

Doesn't depend on libgcrypt15 anymore.

Ranjak commented on 2014-08-05 10:34 (UTC)

Is there a way to have h264 decoding support for the browser ? Thanks.

SimonSapin commented on 2014-06-27 17:41 (UTC)

Any chance this could install into a different path, so that it does not conflict with the (stable) chromium package?

kendfinger commented on 2014-06-14 03:02 (UTC)

I updated the package to use git hashes instead, which should keep it up-and-running through the big Chromium source git switch.

neverfox commented on 2014-06-05 08:42 (UTC)

@Det - Nevermind. There was a process that wasn't dying so I wasn't getting a true restart of chromium. All's well.

neverfox commented on 2014-06-05 08:38 (UTC)

@Det This version of Chromium cannot find either chromium-pepper-flash (stable or dev) on AUR, nor does the ln -s trick work. Both packages already install libs at /usr/lib/PepperFlash but nothing ever shows in chrome://plugins.

Det commented on 2014-05-05 15:44 (UTC)

NPAPI plugins (such as Java) are no longer supported in the Aura versions: The Pepper Flash works with Chromium - it just needs to find it (Chrome's bundled closed-source Flash they've developed after partnering with Adobe). You could try chromium-pepper-flash-dev: Alternatively, you might just symlink the "PepperFlash/" folder from Chrome's main directory to "/usr/lib/". E.g for Dev Channel: $ sudo ln -s /opt/google/chrome-unstable/PepperFlash/ /usr/lib/

arkeiro commented on 2014-05-05 15:30 (UTC)

How can I enable java and pepper flash plugins? I lost them with this chromium package. Thanks!

kendfinger commented on 2014-04-05 17:58 (UTC)

@pablofiumara please use the chromium-pepper-flash package. :)

pablofiumara commented on 2014-04-04 22:50 (UTC)

@kaendfinger: Thanks for this package! How can I make Flash work? I copied to /usr/lib/chromium but that did not work. Thanks in advance for your answer.

thestinger commented on 2014-02-26 22:43 (UTC)

This needs to be renamed to `chromium-continuous` or `chromium-continuous-bin` and the `pkgdesc` should be updated to specify exactly what it is. The current naming is very unclear.

Det commented on 2014-02-20 05:10 (UTC)

Please use a proper pkgver.

xyproto commented on 2014-02-09 15:48 (UTC)

Please add conflicts=(''). is currently needed by dart-editor.

Scimmia commented on 2014-01-29 18:36 (UTC)

@SlimFox3, because even though the pkgname doesn't say it, this is a -bin package. It's using pre-built binaries that need to be compatible with all of the out of date systems out there.

kendfinger commented on 2014-01-22 21:39 (UTC)

I have added libgcrypt15 as a dependency. Any issues, let me know. This package will always be maintained :P

kendfinger commented on 2014-01-22 15:05 (UTC)

I'll see about making libgcrypt15 a dependency. It's probably because of the slow updates on Debian that the Buildbot builds on the older version.

SimFox3 commented on 2014-01-21 19:26 (UTC)

I needed to install the libgcrypt15 from AUR (e.g: packer -S libgcrypt15), but why is the latest chromium building against an older version?

SimFox3 commented on 2014-01-21 19:23 (UTC)

/usr/lib/chromium/chrome: error while loading shared libraries: cannot open shared object file: No such file or directory

kendfinger commented on 2014-01-19 00:23 (UTC)

This includes my API Key and OAuth information so there is no need to add it.

kendfinger commented on 2014-01-19 00:21 (UTC)

A more ermazing package called 'chromium-nightly' has emerged. It is more up-to-date because it uses the very very latest revisions from

UnCO commented on 2014-01-14 01:10 (UTC)


mr_spuck commented on 2013-12-29 16:31 (UTC)

It seems the latest libgcrypt update broke this package. Chromium won't start anymore complaining about the following. /usr/lib/chromium/chrome: error while loading shared libraries: cannot open shared object file: No such file or directory

Det commented on 2013-07-27 20:49 (UTC)

Pot calling the kettle black. It's not this thing I was talking about.

commented on 2013-07-27 19:11 (UTC)

@Det It's as stupid as is 'Det'

Det commented on 2013-07-27 07:12 (UTC)

What a stupid name for a package.

nagy commented on 2013-07-26 18:04 (UTC)

could you please remove the file /usr/lib/ and use the package "" instead?

Ner0 commented on 2013-06-26 16:11 (UTC)

Okay, i've modified the /usr/bin/chromium to include the CHROME_DEVEL_SANDBOX env and also changed the permissions of chrome and chrome_sandbox.

AlK commented on 2013-06-26 14:29 (UTC)

Since this[1] commit, the sandbox is required by default to run chromium. We could pass the --disable-setuid-sandbox flag to run it without sandbox (put it in the "/etc/chromium/default" file for example) but it is a major security risk as the sandbox is a feature to prevent the chrome process to communicate with other processes. The solution to launch chromium with a sandbox is to compile it with -Dlinux_sandbox_path=/path/to/sandbox The precompiled version does not have a path defined because it is a build targeted for chromium devs. (Note: a sandbox path could be defined with the environment variable CHROME_DEVEL_SANDBOX if and only if the owner of the "chromium" binary is the current user) [1]

Ner0 commented on 2013-06-25 06:24 (UTC)

I've updated the PKGBUILD to retrieve the last working revision (208132) until the issue is fixed.

monoloco commented on 2013-06-24 22:58 (UTC)

I get the same issue I believe that it's an issue with the chromium binary and not the aur package. In the meantime you can just use and older version, I think I use _pkgver=208101

kolos commented on 2013-06-24 22:29 (UTC)

oops, i get [32179:32179:0624/] Running without the SUID sandbox! See for more information on developing with the sandbox on. [1] 32179 abort (core dumped) chromium anyways to fix it?

AlK commented on 2013-04-09 10:09 (UTC)

> The package is now located in /usr/lib/chromium instead od /opt/chromium-browser to be more in sync with chromium from [extra]. I really don't like this change. As a web developer, I like to have both chromium stable and nightly installed side by side. With the old PKGBUILD, I had the "chromium" binary for the stable release, and the "chromium-browser" for the nightly. Now, both packages are conflicting. I'd love to be able to use both versions, as I do with "firefox" and "firefox-nightly".

Det commented on 2013-04-08 14:59 (UTC)

Nice. Here's some more suggestions: Explanations:

Ner0 commented on 2013-04-08 11:56 (UTC)

I've adpoted the package and synced it with the pacman 4.1 changes. The package is now located in /usr/lib/chromium instead od /opt/chromium-browser to be more in sync with chromium from [extra]. The default file is located in /etc/chromium/default.

monoloco commented on 2013-04-05 14:40 (UTC)

Since pacman 4.1 I needed the following changes to build successfully Without these changes i get the following warning ==> WARNING: Using a PKGBUILD without a package() function is deprecated. and the following error ==> Starting build()... -> Downloading the latest 'x86_64/LATEST/'... --2013-04-06 01:11:21-- Resolving (, 2404:6800:4008:c01::84 Connecting to (||:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-04-06 01:11:21 ERROR 404: Not Found. ==> ERROR: A failure occurred in build(). Aborting...

kellerman commented on 2013-03-28 12:24 (UTC)

todays chromium update from arch repo causes laggy youtube (both html5 and flash) and probably other flash videos.

commented on 2013-03-06 12:12 (UTC)

Any way to get H.264 support for YouTube HTML5?

commented on 2013-01-20 15:04 (UTC)

@Det, @jahiy: I totally depend on the users; since I don't use this package any more. And @gendo_12 or all other users of this: I really am looking for a maintainer, but the one who needs to show her/his bash skills. Anyway, please test the updated PKGBUILD; I shall help resolve the issues provided users guide/inform me clearly (please post/send the patches).

jahiy commented on 2013-01-20 11:39 (UTC)

libudev is no longer available in Arch.

Det commented on 2013-01-18 09:51 (UTC)

@bdheeman, if I could I would've fixed this a long time ago. But I let it slide.

commented on 2013-01-18 05:39 (UTC)

@gendo_12, Please check;a=summary Feel free to fork it; test your skills; I shall/can pass the control to you and, or anyone when you people are comfortable to adapt this AUR/PKGBUILD @Det, Please don behave like a dictator.

Det commented on 2013-01-17 21:35 (UTC)

@gendo_12, deep inside he probably does but I feel the spirit has passed away to The Faraway Land and is beyond our reach now, and therefore unable to convey this message.

commented on 2013-01-17 20:48 (UTC)

I am willing to adopt the package for a more updated response to the bugs that show up if bdheeman is willing ??

AlK commented on 2012-12-18 13:11 (UTC)

bdheeman: Could you please fix this libudev issue? it is really annoying.

Det commented on 2012-11-06 22:44 (UTC)

bdheeman you still around?

statenjason commented on 2012-10-10 15:17 (UTC)

In the PKGBUILD add: try_symlink || return $? Below all of the the other try_symlink invocations.

rainux commented on 2012-09-25 13:44 (UTC)

It depends on libudev which no longer available in latest Arch.

burra commented on 2012-08-29 17:24 (UTC)

playing h264 inside chromium used to be possible. Like the following: Do I need to install external codecs for this now? If so, which?

xduugu commented on 2012-08-24 08:41 (UTC)

This package should provide "chromium" instead of "chromium-browser". See

commented on 2012-06-02 17:27 (UTC)

In /usr/lib sudo ln

Ner0 commented on 2012-06-01 22:14 (UTC)

# sed -i 's/' /opt/chromium-browser/chrome works fine.

dolik.rce commented on 2012-05-30 05:31 (UTC)

It seems like the recent switch to systemd-tools in [testing] caused thi package to stop working. The reason is that the chromium is linked against, while systemd-tools provides I know there is not much that can be done about how the binary is linked, but I guess udev should be listed as a dependency of chromium-browser-bin, so that users are not too surprised when the chromium refuses to start all of a sudden...

Det commented on 2012-05-15 12:13 (UTC)

It's not. [extra] follows the stable channel, this one the absolute latest builds there is. The other one updates once every few days, this one once every few hours.

whynothugo commented on 2012-05-15 11:13 (UTC)

What's the difference between this package and the package "chromium" in [extra]? It seems unclear.

Anarconda commented on 2012-05-02 16:02 (UTC)

@w1ntermute, Yes, remove chromium-codecs-ffmpeg.... and try again with

w1ntermute commented on 2012-03-19 00:05 (UTC)

I have both this package and chromium-codecs-ffmpeg-nonfree-bin installed, but I'm still getting the message "Your browser does not support HTML5 video with our site." from YouTube. Any ideas?

commented on 2012-03-15 17:17 (UTC)

@Det, thanks again for testing. Yeah, I just removed linpng12 nothing else.

Det commented on 2012-03-15 16:56 (UTC)

Arranged and checked. Nothing to break anyway, if you just removed libpng12 from the dependencies.

commented on 2012-03-15 16:53 (UTC)

@Det, thanks; I don't use this AUR these days hence am more dependent on users' feedback to maintain it. Plz arrange to check the updated PKGBUILD.

Det commented on 2012-03-15 16:43 (UTC)

Doesn't require libpng12 anymore, btw. └┌(%:~/Desktop)┌- ldd /opt/chromium-browser/chrome|grep png => /usr/lib/ (0x00007f05d02dc000)

commented on 2012-03-05 14:00 (UTC)

@tulio, for non-free codecs you also need to install or a similar package.

commented on 2012-03-05 13:08 (UTC)

I installed this but says my browser doesn't support "Video tag", "h.264", and "WebM". Something I forgot to do, maybe?

commented on 2011-12-05 14:11 (UTC)

Is there any reason why it use instead of ???

Det commented on 2011-12-05 08:12 (UTC)

Seriously. People, read the Wiki before installing this package. @hasardeur, you either build this with "makepkg -s(i)" or just use an AUR helper (eg. yaourt). Simple "makepkg" only tries to build (not even install) the package without installing any of its dependencies.

hasardeur commented on 2011-12-04 16:29 (UTC)

Hi, I just wanted to install this chromium package and failed with this: error: target not found: error: ==> ERROR: 'pacman' failed to install missing dependencies. I had to manually do: pacman -S gconf It is not a big deal and I have no idea why this happens - just wanted to share.

Det commented on 2011-12-03 21:09 (UTC)

As well as not reading stuff is a dependency for bad comments. "Warning: Packages in the AUR assume "base-devel" is installed, and will not list members of this group as dependencies even if the package cannot be built without them. Please ensure this group is installed before complaining about failed builds."

commented on 2011-12-03 11:28 (UTC)

Autoconf/m4 is a dependancy for building libpng12.

ava1ar commented on 2011-11-27 04:16 (UTC)

@bdheeman, Do you actually know, that latest yaourt versions are not correctly handle $pkgver from current PKGBUILD version. Comparison code from yaourt: is_x_gt_y() { [[ $(vercmp "$1" "$2" 2> /dev/null) -gt 0 ]] } returns that LATEST is smaller than current build number. This means that yaourt will never update this package during usual yaourt -Su and yaourt -Su --devel and will be updated only in case you explicitly provide yaourt -S chromium-browser-bin. This means you should avoid using LATEST as a pkgver value - if you don't want specify correct number, replace LATEST with 1:0 - this utilize epoch comparison approach in vercmp utulity and it will always return -1 as expected.

AlK commented on 2011-11-06 21:22 (UTC)

@bdheeman: here it is: As the extra/chromium package do not use "chromium-browser" there is no conflict between the two packages, appart from a man page as aur/chromium-browser-bin creates the "chromium" and "chromium-browser" pages, which provides the same informations. I have not a lot of experience in pkgbuilds, but I think you could safely remove or rename the "provides" section to prevent package conflicts.

commented on 2011-11-06 17:12 (UTC)

@AlK: I fear some of the symlinks and menu or desktop related things won't conflict. Plz test install both the packages after making appropriate, but minimal changes to this PKGBUILD; send me unified diff if everything works as expected, so that I may also incorporate your changes.

AlK commented on 2011-11-06 13:01 (UTC)

I like to have aur/chromium-browser-bin side by side with extra/chromium, as we can do with aur/firefox-nightly and extra/firefox. Those two packages does not conflict at all, could you remove chromium-browser from the conflicts table (and change the provide name...)? Thanks a lot!

Det commented on 2011-10-12 15:23 (UTC)

There's Chrome 15:

dotmagic commented on 2011-10-12 14:34 (UTC)

Is there no chromium 15 build in aur?

eduardosm commented on 2011-09-30 16:53 (UTC)

The PKGBUILD from Det works. It should be uploaded.

Det commented on 2011-09-15 12:16 (UTC)

This is because along with the URL change Google also changed the name of the file showing the latest Chromium version ("LATEST" -> "LAST_CHANGE"). So the "LATEST" variable just needs to be replaced with "LAST_CHANGE" in everywhere else too (also includes other minor fixes, such as removing the redundant 'return' checks and adding quotes to the (src/pkg)dir variables):

einseenai commented on 2011-09-15 08:47 (UTC)

@Xerdomii Just tryed to patch it with your And got the following: /tmp/yaourt-tmp-jason2/aur-chromium-browser-bin/./tmp.1vos5pYC57: line 5: syntax error near unexpected token `esac'

commented on 2011-09-15 06:53 (UTC)

Patch for the PKGBUILD to work with the new URL:

felixonmars commented on 2011-09-15 04:53 (UTC)

Flagged Out-of-date Chromium repo url has an update again and I cannot find the new place.

commented on 2011-09-03 14:19 (UTC)

@w1ntermute, the chromium-browser-ppa is also build but only once per day from an SVN update, which I think is more stable or free of new bugs. As for as chromium-browser-bin is concerned they (the google people) also build it on Ubuntu machines, hence none of these is (or can never be) fully compatible with ArchLinux, but both these just work for us. Both are just *beta builds*, hence we should not expect too much from these; new bugs are being introduced at a same speed as are being fixed everyday. These builds are made available just to seek as much feedback as the upstream developers can.

w1ntermute commented on 2011-09-03 01:58 (UTC)

@bdheeman: What was your reason for moving over? Is chromium-browser-ppa a replacement for chromium-browser-bin?

commented on 2011-08-29 14:08 (UTC)

@tang0th67, I don't use this PKGBUILD since the day I created, hence I totally depend on the users for testing, updates and, or changes. Please do test it before submitting and, or asking for a change.

tang0th67 commented on 2011-08-29 12:11 (UTC)

Oppps best revert that it looks like gconf is a compile flag... :(

tang0th67 commented on 2011-08-28 16:04 (UTC)

Just like to say that chromium DOESN'T need gconf any more, check out and check teh package at it doesn't need gconf. Thanks ^_^

w1ntermute commented on 2011-08-25 23:13 (UTC)

I'm in the same situation as splippity - I tried to downgrade to the 'chromium' package in the repos, but I couldn't. I'm having the same issue as jwhendy - Chromium recently started randomly locking up for a few minutes at a time, preventing me from using my computer at all (mouse moved very slowly, Conky updated sporadically, etc.). I'd appreciate it if someone with a fix would post it!

splippity commented on 2011-08-11 00:17 (UTC)

someone want to update to the latest build from today and tell me if their passwords are currently being stored??? mine arent so I had to go back to official package and that thing sucks... telling me I cannot use my profile because its from a newer version.

jwhendy commented on 2011-08-02 16:28 (UTC)

@bdheeman: unified patch created. Which forum would you suggest? Creating and Modifying Packages or AUR Issues, Discussion & PKGBUILD Requests? I'll post this on the forum and see what others think. I'm starting to wonder if this is a flash deal. I've had several instances of complete computer freeze (conky stops, no response from any keyboard shortcut, but mouse moves) while using chromium. Often I think it's when watching something on youtube. Really sucks, though, so this was a first step in trying to pin it down, but it might prove useful/desirable for others in the process.

commented on 2011-08-02 05:08 (UTC)

@jwhendy, Thanks for the patch; though a unified diff is most preferable, but your patch is still good enough. Yes, using pastebin or other similar public/free services is a better option for sharing small snippets of code and, or patches. As for as testing and, or feedback is concerned, we/you need to (or can) advertise it in the forums. I indeed, rarely use this PKGBUILD these days, hence I prefer feedback from the real/actual or active users of this one, before I accept and merge your changes.

jwhendy commented on 2011-08-01 21:55 (UTC)

@bdheeman: I've not done that before, so thanks for the drive to read through a tutorial on using diff to create patches. Is putting it on pastebin sufficient or is something else entailed in "submitting it"? What's the method of waiting for feedback from others? Should I post in "Try This" in the forums or something? Anyway, if pastebin is sufficient, it is here: Let me know if you need more.

commented on 2011-08-01 21:00 (UTC)

@jwhendy, Plz submit a proper patch so that the users may try it. I, OTOH, shall wait for a positive feedback from the users as well, before I merge your changes. Anyway, thanks for your effort and, or suggestion :)

jwhendy commented on 2011-08-01 14:50 (UTC)

Chromium has been a bit flaky for me lately, and as I was looking into the build page about it, I noticed that they keep a page updated with the latest "green" version. The green version is the last change that produced a successful build and passed various tests, called "green" based on the build results chart here: The version that most recently passed the requirements gets listed as text here: As of about 9:35a on 8/1, LATEST = 94899, while the output from LAST_CHANGE = 84893. Just wondered if there would be any interest in using this version instead of a strict commitment to LATEST? I realize it's a few builds behind, but seemed like it might be a compromise between up-to-dateness and stability? If this is at all interesting, I was able to make this work very easily by a slight change to the PKGBUILD section determining newpkgversion. See here for my change:

felixonmars commented on 2011-06-08 02:29 (UTC)

chromium repo has an update this morning. now the bldarch part should be: case "$CARCH" in i686|i[3-5]86) _bldarch='Linux';; x86_64|amd64) _bldarch='Linux_x64';;

dieghen89 commented on 2011-05-15 19:59 (UTC)

==> Rimozione dei dati superflui in corso... -> Rimozione degli altri file in corso... -> Compressione delle pagine man ed info in corso... -> Rimozione dei simboli non necessari dai binari e dalle librerie in corso... /usr/bin/strip:./opt/chromium-browser/nacl_irt_x86_64.nexe: File format not recognized ==> ERRORE: Makepkg non è riuscito a compilare chromium-browser-bin. "!strip" solves...

commented on 2011-05-15 16:59 (UTC)

Chromium no longer requires ffmpeg to be installed and should be an optional dependency - see

commented on 2011-05-14 18:27 (UTC)

Package depends on gtk2, now that gconf links to gtk3 both are required.

misc commented on 2011-05-11 16:24 (UTC) Turns out my xmarks extension hasn't worked for over a week. Rats. 84985+ is safe again, for now.

Det commented on 2011-05-11 14:34 (UTC)

Is it even necessary to ask whether the bleeding edge builds will sometimes cause trouble ;)?

Anarconda commented on 2011-05-11 14:24 (UTC)

Anybody else whose bookmarks were shredded by a recent build? Yes.

misc commented on 2011-05-11 10:25 (UTC)

Anybody else whose bookmarks were shredded by a recent build?

Det commented on 2011-05-04 19:52 (UTC)

Well, I'm pretty sure :). This one guy's link in the google-chrome-dev's comment section confirms it:

commented on 2011-05-04 19:15 (UTC)

@Det, thanks for the feedback, I'm maintaining this one only because of users like as you and I totally depend on you test it; since I also created a few other PKGBUILDs based on Ubuntu PPA's for chromium-browser. I use an X86_64/amd64 version of so/and can't test this one and, or both the i686 and x86_64 versions of these 'cause I don't have a i[36]86 installation these days. I shall/can update it, provided you're sure that it work for others as well :)

Det commented on 2011-05-04 18:41 (UTC)

Doesn't seem to require libjpeg6 anymore. I removed the whole thing and jpegs still work fine. Libjpeg-turbo doesn't seem to be required either (doesn't show up with lsof).

rickdesantis commented on 2011-05-03 08:39 (UTC)

I can confirm that the fix proposed by @splippity and others works: however, the PKGBUILD is already fixed atm. Just remove the symbolic link if you've still got it: sudo unlink /usr/share/pixmaps/chromium-browser.png I've got my icon back in my taskbar in KDE4 doing that, so I'm sharing the tip. Hope it helped somebody :)

splippity commented on 2011-05-03 01:34 (UTC)

As stated before to fix the icon missing from the tray problem delete the following line: ln -s /opt/${_realname}/product_logo_48.png $pkgdir/usr/share/pixmaps/${_realname}.png or you could modify it to mirror the line above: ln -s /opt/${_realname}/product_logo_48.png $pkgdir/usr/share/pixmaps/product_logo_48.png my tray icon works like a champ... its the new design.

dieghen89 commented on 2011-04-29 12:46 (UTC)

@staticsafe now i'm using (temporarily) chromium-browser-ppa and all works (also icons in kde4)...I hope that also in this package all problems will be solved :)

commented on 2011-04-29 11:22 (UTC)

I am getting the same issue as well, Chromium doesn't load any page.

commented on 2011-04-24 23:38 (UTC)

No fix for icon on KDE4 taskbar yet?

dieghen89 commented on 2011-04-22 20:28 (UTC)

It is since 79??? that chromium doesn't load any page...Only my problem? I've also tried to remove .config/chromium dir, but no results...

commented on 2011-04-22 16:28 (UTC)

@trontonic, I think, the ArchLinux maintainers renamed AUR package "ttf-hannom-usong" as "ttf-hannom" while they accepted/added it to "extra" repository; which I was not aware of. I shall update this PKGBUILD soon.

xyproto commented on 2011-04-22 15:56 (UTC)

I could not find "ttf-hannom-usong", but I did find "ttf-hannom" (optdepends).

commented on 2011-04-22 09:20 (UTC)

@jwhendy, @Det: The makepkg users can use --forcever=<whatever-version-was-working-fine> option to build and install any old/working version available at upstream/build site. @jwhendy: I think, you missed you're playing with a (pre-rlease) beta build, plz don;t expect stability and remained prepared for a bumpy road ahead when using/testing beta/alpha (pre-release) builds. IMHO, I and the upstream are providing these builds for testers only; for feedback, bug reports and, or feature request which users/testers must/should pass directly on to upstream developer's or site.

Det commented on 2011-04-22 05:32 (UTC)

@jwhendy, well, since Chromium gets updated like once every hour (see: are you aiming for to have the absolute latest build or just any build that has a bumped version number (which is done like once a day or so)? What other people do with this package is that whenever they wanna update it they just reinstall it (no need to remove it - just install it 'over' the former one). If you do not need to edit the PKGBUILD when updating you can also use Yaourt's "--noconfirm" flag to automatically pass all the questions and confirmations (be careful with this though - some packages might do bad things when the PKGBUILD is not reviewed beforehand).

jwhendy commented on 2011-04-21 18:29 (UTC)

Is there any way to force an upate whenever chromium is updated? Since this simply points at the LATEST link in their repos, it seems that this package is only updated if the owner does something, for example with the PKGBUILD. To illustrate why this is nice, 12.0.740.0 had broken spell checking (see here: The bug report says that 12.0.742.0 fixed this, but even though I was running 12.0.740.0 and they are now at 12.0.744.0, yaourt showed no updates available with 'yaourt -Syu --aur.' I just did 'pacman -R chromium-browser-bin' and then 'yaourt chromium-browser-bin' to reinstall, and the problem is now fixed. But I wonder if there's a way to automatically flag an update when a new version comes out? This would be helpful for packages that point at a static link and thus can function for months without any changes to PKGBUILD or *.install files. Or are others already doing this somehow and I'm just behind the ball?

jwhendy commented on 2011-04-21 18:28 (UTC)

Is there any way to force an upate whenever chromium is updated? Since this simply points at the LATEST link in their repos, it seems that this package is only updated if the owner does something, for example with the PKGBUILD. To illustrate why this is nice, 12.0.740.0 had broken spell checking (see here: The bug report says that 12.0.742.0 fixed this, but even though I was running 12.0.740.0 and they are now at 12.0.744.0, yaourt showed no updates available with 'yaourt -Syu --aur.' I just did 'pacman -R chromium-browser-bin' and then 'yaourt chromium-browser-bin' to reinstall, and the problem is now fixed. But I wonder if there's a way to automatically flag an update when a new version comes out? This would be helpful for packages that point at a static link and thus can function for months without any changes to PKGBUILD or *.install files. Or are others already doing this somehow and I'm just behind the ball?

tokland commented on 2011-04-08 14:53 (UTC)

Was anyone able to fix the icon problem for gnome/xfce? (I tried the solution proposed for kde, with no luck). I've seen no icon in the taskbar for 2 or 3 weeks (using 80922 now).

misc commented on 2011-03-27 13:07 (UTC)

I see, old habits die hard. :) curl, however, really is more advanced than wget: Thanks for the info on $QUIET.

commented on 2011-03-25 16:57 (UTC)

@misc, ok, that did the trick; I, indeed, am more used to wget (Debian/ArchLinux) and fetch (FreeBSD). I use the same PKGBUILD to repackage chromium-browser for Debian also; the $QUIET was '-q' for wget and can/shall be '-s' for curl :)

misc commented on 2011-03-25 10:41 (UTC)

Ah, you mean the other wget command? I missed that, my bad. Its curl equivalent is: curl -s -o - -L Still, what does the $QUIET mean/contain? I failed to find it in any of Arch's documentation. It's also apparently simply empty?

commented on 2011-03-25 00:00 (UTC)

@misc, curl can/will not serve our purpose; here in this PKGBUILD. try: curl -s -o -

misc commented on 2011-03-24 20:01 (UTC)

Please replace wget with curl. wget's constant "can't resolve host address" are highly annoying for me and curl will replace it in the next release of pacman (google "Replacing wget with curl in makepkg"). Following the changes in makepkg.conf, the new command could be: curl $QUIET -H "Pragma: no-cache" -C - -fLC - --retry 3 --retry-delay 3 -o "$SRCDEST/${_bldname}" "${_bldroot}/$pkgver/${_bldname}" However, I've got no clue what that $QUIET means (curl is muted via -s) and no-cache is (was?) curl's standard already.

splippity commented on 2011-03-21 04:21 (UTC)

Im working good now..... showing the new chromium logo as the logo in the task manager. I deleted that whole line you said was bad and I see what you mean when I look at the code. The line right above it is the correct line. Didnt notice if it was different because it was updated today. But either way mine is good to go now. thanks

archtux commented on 2011-03-20 22:07 (UTC)

I resolved the problem with missing icon in KDE4 this way. The name of the icon file in the link is not correct! ${_realname}.png='chromium-browser.png' and the icon file is 'product_logo_48.png' Change at the end of line '${_realname}.png' -> 'product_logo_48.png' : ln -s /opt/${_realname}/product_logo_48.png $pkgdir/usr/share/pixmaps/${_realname}.png Correct line is : ln -s /opt/${_realname}/product_logo_48.png $pkgdir/usr/share/pixmaps/product_logo_48.png

HNKNTA commented on 2011-03-20 15:28 (UTC)

still nothing changed for me

splippity commented on 2011-03-20 15:25 (UTC)

still not working on mine. I installed the aur package after I read your comment and even rebooted. Still no icon in the traskbar. just the X lets see what other people say.

commented on 2011-03-20 14:54 (UTC)

After today's `pacman -Syu' upgrade Chromium icons shows properly in KDE taskbar.

commented on 2011-03-20 11:50 (UTC)

i think it has nothing to do with new logo; I experienced the problem before the logo was changed.

splippity commented on 2011-03-20 05:59 (UTC)

while I still have no clue I can verify that the product_logo_48.png is in opt/chromium-browser as it should be but its not being used.... wierd. could it be something google did since they are changing logos?? like transitioning but not finished yet? but you would think if its as easy as just adding another png with a different name like product_logo_49.png they would have done it...... Im sure better people then me will figure it out. just figure I would post more info on the issue.

splippity commented on 2011-03-20 05:48 (UTC)

on kde4 I too am experiencing the same problem of no icon.... it is showing an X in my tray like others have described. thanks. maybe its because of chromiums icon changing to the new style??? and theres no proper linking to the image... though Im speculating as I have no clue how you would fix it.

HNKNTA commented on 2011-03-19 14:29 (UTC)

same problem openbox + tint2 panel (with xfce4-panel too)

commented on 2011-03-19 14:05 (UTC)

@cinan, Sorry, I'm unable repeat/test, since I don't use KDE and, or Gnome; BTW, all icons are shown correctly in XFCE4's taskbar here.

commented on 2011-03-19 12:43 (UTC)

the problem still persists.

commented on 2011-03-18 01:57 (UTC)

@cinan,fixed; plz test.

commented on 2011-03-17 20:09 (UTC)

well, in taskbar in KDE is shown wrong icon (as you can see on the picture I attached). I didn't changed pkgbuild. With chromium package from official Archlinux repo there's no problem (correct(/opt/chromium-browser/chromium-browser.png) icon is shown in taskbar).

commented on 2011-03-17 19:06 (UTC)

@cinan, I'm sorry, could get/understand you; plz elaborate a bit.

commented on 2011-03-17 12:10 (UTC)

in KDE chromium icon doesn't show properly ( I changed nothing in PKGBUILD, installed by default. Chromium package in official repo is affected.

xyproto commented on 2011-03-07 14:24 (UTC)

Please depend on libgles and libegl.

mhellwig commented on 2011-01-24 13:09 (UTC)

as described by someone at the bug report, running sudo mkdir /opt/chromium-browser/extensions fixes it. guess that should go into the PKGBUILD.

commented on 2011-01-24 02:22 (UTC)

heya, I get the same issue: [] Check failed: !prefs_->empty() || !base_path_.empty(). Cheers, Victor

ben0mega commented on 2011-01-23 22:01 (UTC)

@mhellwig filed a bug report:

mhellwig commented on 2011-01-23 16:22 (UTC)

well I do have a problem with 72293-1 as well as 72300-1. They both don't start and instead die with "[] Check failed: !prefs_->empty() || !base_path_.empty()." Whatever that is supposed to mean.

Det commented on 2011-01-22 08:44 (UTC)

72271 works again. No need to modify this package after all.

Slash commented on 2011-01-22 04:47 (UTC)

Same for me. When it broke I reverted back to the one prior to 71418 using "makepkg --forcever 71417".

misc commented on 2011-01-21 12:10 (UTC)

Wfm again, for now. That's been the second time I had the dev build of Chromium unusable for more than a week.

Det commented on 2011-01-18 10:17 (UTC)

There seems to be something wrong with the packaging from 71418 onwards. By just downloading the .zip archive and extracting & using everything works fine but with this package pages stop loading. The error is: [] Failed to adjust OOM score of renderer with pid 4558: Permission denied I tried to do some chmod'ing of the installation files and /tmp directory but it didn't help.

LeCrayonVert commented on 2011-01-13 15:30 (UTC)

Adding export CHROMIUM_USER_FLAGS="--password-store=detect" to /etc/profile doesn't work. After each update, I need to manually change the /usr/bin/chromium file to add --password-store=detect"...

Det commented on 2011-01-01 14:59 (UTC)

Please remove 'google-chrome-dev' and 'chromium-os-bin' from "conflicts=()". The other one can be installed side-by-side and the other one doesn't exist anymore, respectively.

commented on 2010-12-06 18:22 (UTC)

I am a robot. This is not an official message. AUR guidelines suggest to not include binaries. Examples: chromium-browser-bin/chromium-browser.1.gz Feel free to disregard this as you would any other comment. This robot will not post here again.

Det commented on 2010-11-24 19:47 (UTC)

@bdheeman, perhaps you misunderstood my comment. Libgnutls13 is no longer needed.

commented on 2010-11-23 23:23 (UTC) Number 6: "Don't use replaces in your PKGBUILD unless you want to rename your package, for example when Ethereal became Wireshark." Also, this package doesn't conflict with chromium in extra. The only problems I found installing two versions were (1) the man page was a file conflict and (2) your profile in /.config/chromium may be incompatible. The PKGBUILD lists conflicts with chromium-browser, provided by chromium in extra.

Det commented on 2010-11-21 11:39 (UTC)


commented on 2010-11-21 02:29 (UTC)

ldd since at least chromium v66883 says that libgnutls13 is no longer needed, am I wrong?

Det commented on 2010-11-20 16:49 (UTC)

You'd need to build your mesa with "--enable-egl" and "--enable-gles2".

commented on 2010-11-14 09:24 (UTC)

Could you help please? [user@myhost ~]$ chromium-browser --enable-accelerated-compositing [8937:8937:31548486361:ERROR:base/] dlopen failed when trying to open cannot open shared object file: No such file or directory [8937:8937:31563962529:FATAL:app/] X Error detected: serial 198, error_code 9 (BadDrawable (invalid Pixmap or Window parameter)), request_code 14 minor_code 0 (X_GetGeometry) [9045:9045:32434587117:ERROR:base/] dlopen failed when trying to open cannot open shared object file: No such file or directory Despite of the above warnings, the browser runs correctly, but, of course there are no hardware acceleration. (I use and to make sure that acceleration is off.)

commented on 2010-10-26 04:33 (UTC)

@bdheeman, if you want to address this problem, the part mentioned by @ChoK can be decoupled from PKGBUILD and live as a separate script on aur.

commented on 2010-10-26 04:02 (UTC)

@ChoK, The ArchLinux does not have/provide a mechanism like Debain, Fedora and, or Ubuntu's /etc/alternatives, so that users may set their own precedence. I knew, many applications use the symlink x-www-browser; so I attempted to address that in a somewhat rude way. Let me devise something better, I shall update the PKGBUILD accordingly.

commented on 2010-10-26 01:38 (UTC)

You shouldn't assume the user wants chromium as the default browser. It's better to display a reminder about that. (And I think it doesn't concern gnome and kde but lxde/openbox uses this symlink) in chromium-browser.install: post_install() { if [ "$(readlink /usr/bin/x-www-browser)" != "chromium-browser" ]; then ln -fs chromium-browser /usr/bin/x-www-browser fi [...] } post_remove() { if [ "$(readlink /usr/bin/x-www-browser)" = "chromium-browser" ]; then if [ -x /usr/bin/arora ]; then ln -fs arora /usr/bin/x-www-browser elif [ -x /usr/bin/firefox ]; then ln -fs firefox /usr/bin/x-www-browser else rm -f /usr/bin/x-www-browser fi fi [...] }

commented on 2010-10-23 17:27 (UTC)

@Phlogiston, Plz use official 'makepkg' tool.

Phlogiston commented on 2010-10-23 11:26 (UTC)

[root@htpc ~]# packer -S chromium-browser-bin /tmp/packertmp-0/chromium-browser-bin.PKGBUILD: line 46: msg: command not found /tmp/packertmp-0/chromium-browser-bin.PKGBUILD: line 49: msg2: command not found /tmp/packertmp-0/chromium-browser-bin.PKGBUILD: line 55: [: : integer expression expected /tmp/packertmp-0/chromium-browser-bin.PKGBUILD: line 60: devel_update: command not found

didi2002 commented on 2010-09-15 22:44 (UTC)

try starting chromium with the "--enable-accelerated-2d-canvas" parameter...Incredibly fast!

commented on 2010-09-04 16:46 (UTC)

Now it works well !

polslinux commented on 2010-09-03 12:32 (UTC)

There's a problem with the wrapper patch!

polslinux commented on 2010-09-03 12:27 (UTC)

same problem

commented on 2010-09-03 10:13 (UTC)

same problem

amirs commented on 2010-09-03 03:39 (UTC)

on latest rev 58455 i get this: -> Extracting Binaries... -> Creating missing symlinks... -> Patching script 'chrome-wrapper'... 1 out of 2 hunks FAILED -- saving rejects to file chrome-wrapper.rej Aborting...

commented on 2010-08-20 13:56 (UTC)

@Banjo, that's a well known bug, not because of chromium and, or gtk2 but ArchLinux's latest gtk2 and, or* :(

commented on 2010-08-20 12:50 (UTC)

Works great , only thing is that when i try to upload jpeg files chromium crash

statenjason commented on 2010-07-24 21:55 (UTC)

@juanpablo, Thanks for the tip.

commented on 2010-07-22 18:33 (UTC)

PROTIP: Edit the libgnutls13 PKGBUILD and change the url from ... to ...

Phlogiston commented on 2010-07-21 10:05 (UTC)

Just a hint: Use --password-store=detect if you want to enable kwallt or gnome-keyring. For permanent setting: export CHROMIUM_USER_FLAGS="--password-store=detect" in profile setting or .bashrc

commented on 2010-07-19 19:25 (UTC)

error with symbol link

commented on 2010-06-25 18:51 (UTC)

@OttoA Plz check and star issue I never ever tested chromium from extra, but there were roughly 10+ PKGBUILD's lurking around here when I submit this heavily refined and, or improved PKGBUILD for repackaging chromium, but from untested, unstable and, or daily builds either ppa or google-build bot.

OttoA commented on 2010-06-25 17:58 (UTC)

Sadly, I can't really use it with the jpeg bug. I don't know if this is a related issue, but on reinstalling chromium from extra, the chromium icons aren't displayed properly in gnome.

commented on 2010-06-25 14:35 (UTC)

New/updated PKGBUILDs/Tarballs based on PPA builds are temporarily available at Plz try: chromium-browser-ppa-*.src.tar.gz chromium-browser-inspector-ppa-*.src.tar.gz chromium-codecs-ffmpeg-extra-ppa-*.src.tar.gz and optionally: chromium-browser-l10n-ppa-*.src.tar.gz I may/shall also submit the same to AUR on receiving feedback.

commented on 2010-06-25 02:17 (UTC)

@OttoA Thanks for the patch, fixed and updated chromium-codecs-ffmpeg-extra-ppa-0.5.50002-2.src.tar.gz The crashes related upload/select jpeg files is known, upstream developers suggested compile/build it from source on ArchLinux; a drudgery I hate for a beta, unstable and, or version under heavy development.

OttoA commented on 2010-06-24 19:06 (UTC)

@bheedman chromium-codecs-ffmpeg PKGBUILD is broken, patch: chromium-browser-ppa crashes when trying to select jpeg file in file dialog html5 videos work

commented on 2010-06-24 17:56 (UTC)

New PKGBUILDs/Tarballs based on PPA builds are temporarily available at Plz try: chromium-browser-ppa-6.0.448.0.50687-1.src.tar.gz chromium-browser-inspector-ppa-6.0.448.0.50687-1.src.tar.gz chromium-codecs-ffmpeg-extra-ppa-0.5.50002-1.src.tar.gz and optionally: chromium-browser-l10n-ppa-6.0.448.0.50687-1.src.tar.gz I may/shall also submit the same to AUR on receiving feedback.

andre.vmatos commented on 2010-06-24 13:09 (UTC)

Running chromium-browser with the option: --password-store=[kwallet|gnome], Chromium will use the system password storage system (Kwallet or Gnome-key-ring) to store your password, moving the existing to it.

commented on 2010-06-20 13:28 (UTC)

@bdheeman Thank you :)

commented on 2010-06-20 06:47 (UTC)

pkgrel=19: update; added dependency 'libgnutls13' Though, I have added above dependency, but I think, it is time to switch using PPA builds; as those seems much more compatible with latest installed ArchLinux libraries. Hope we can/shall get rid of unwanted 'libgnutls13', 'libjpeg6' and 'libpng12' also. I Shell try build/re-package and test PPA builds this week and announce the results ASAP.

commented on 2010-06-19 14:44 (UTC)

@xifs, @bintang I searched for the libgnutls13 weirdness and found a defect report at the Chromium site. I updated it to included that Chromium-50317 doesn't work on Archlinux. Follow the report here:

vehiclee commented on 2010-06-19 10:20 (UTC)

@bintang i install libgnutls13 from AUR. then you can run chromium. you can try it.

commented on 2010-06-18 21:15 (UTC)

/opt/chromium-browser/chrome: error while loading shared libraries: cannot open shared object file: No such file or directory

commented on 2010-05-22 01:28 (UTC)

bdheeman. Thanks. And i have installed it. I got it wrong, the img is jpeg not png. When i click the png img, it will not crash.

commented on 2010-05-21 18:56 (UTC)

speedup2010, 1) Use makepkg to build and, or install 2) Yes, it is a known bug, see See also:

commented on 2010-05-21 16:25 (UTC)

Problem1 qutoe: Sorry, I wanted to update information) I have a trouble with installation. After question if I want to edit PKGBUILD it quites: ==> Edit PKGBUILD ? [Y/n] ("A" to abort) ==> ---------------------------------------------- ==>n [byku@phenya ~]$ Also it quites after close text editor Problem 2 when i upload i png img,i click the img(it will preview the img) and it crashes immediately.i don't know wether it is a bug.

commented on 2010-05-19 21:57 (UTC)

@4ybaka, see

commented on 2010-05-19 20:59 (UTC)

@fackamato I'm sorry, I don't understand what do you mean. Where I can see steps to install? I thinked it all should be in pkgbuild...

commented on 2010-05-19 20:41 (UTC)

Sorry, I wanted to update information) I have a trouble with installation. After question if I want to edit PKGBUILD it quites: ==> Edit PKGBUILD ? [Y/n] ("A" to abort) ==> ---------------------------------------------- ==>n [byku@phenya ~]$ Also it quites after close text editor.

fackamato commented on 2010-05-19 20:39 (UTC)

Use makepkg. Nothing else.

commented on 2010-04-13 15:40 (UTC)

well, this is beta. Bugs may eventually appear. I havent updating for some weeks now. Maybe removing ~/.config/chromium - so all ur settings might help you.

commented on 2010-04-13 14:34 (UTC)

I have a problem with latest google-chrome and chromium with it download manager. If i set in Options "Ask where to save each file before downloading" all files will be downloaded with zero length. If i disable this option and set default download folder everything will be ok. It began some week ago after update.