Package Details: chromium-snapshot-bin 124.0.6313.0.r1262951-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: 498
Popularity: 0.010861
First Submitted: 2015-04-20 12:12 (UTC)
Last Updated: 2024-02-21 18:34 (UTC)

Dependencies (11)

Required by (112)

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

1 2 3 4 5 6 .. 31 Next › Last »

korimitsu commented on 2023-11-25 17:52 (UTC)

Doesn't build anymore:

Building chromium-snapshot-bin...
==> Making package: chromium-snapshot-bin 121.0.6149.0.r1228979-1 (Sat 25 Nov 2023 04:50:27 PM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found
  -> Found
  -> Found chromium-snapshot-bin.desktop
  -> Found chromium-snapshot-bin_16.png
  -> Found chromium-snapshot-bin_22.png
  -> Found chromium-snapshot-bin_24.png
  -> Found chromium-snapshot-bin_32.png
  -> Found chromium-snapshot-bin_48.png
  -> Found chromium-snapshot-bin_64.png
  -> Found chromium-snapshot-bin_128.png
  -> Found chromium-snapshot-bin_256.png
  -> Found LICENSE
==> Validating source files with sha1sums... ... Skipped ... Passed
    chromium-snapshot-bin.desktop ... Passed
    chromium-snapshot-bin_16.png ... Passed
    chromium-snapshot-bin_22.png ... Passed
    chromium-snapshot-bin_24.png ... Passed
    chromium-snapshot-bin_32.png ... Passed
    chromium-snapshot-bin_48.png ... Passed
    chromium-snapshot-bin_64.png ... Passed
    chromium-snapshot-bin_128.png ... Passed
    chromium-snapshot-bin_256.png ... Passed
    LICENSE ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting with bsdtar
==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
  -> Creating directory structure...
  -> Making it nice...
chmod: cannot access 'nacl_*': No such file or directory
==> ERROR: A failure occurred in package().

zrhoffman commented on 2023-01-23 04:37 (UTC) (edited on 2023-01-23 04:38 (UTC) by zrhoffman)

chromium-snapshot-bin should include the contents of, IMO, because

  • The chromium extra package includes chromedriver

  • the chromedriver AUR package rightly conflicts with chromium

  • chromium-snapshot-bin provides chromium only includes the chromedriver binary and a license

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 :)