Package Details: thorium-browser-bin 130.0.6723.174-1

Git Clone URL: https://aur.archlinux.org/thorium-browser-bin.git (read-only, click to copy)
Package Base: thorium-browser-bin
Description: Chromium fork focused on high performance and security
Upstream URL: https://github.com/Alex313031/Thorium
Licenses: BSD-3-Clause
Conflicts: thorium-browser
Provides: thorium-browser
Submitter: StarterX4
Maintainer: xiota
Last Packager: xiota
Votes: 53
Popularity: 1.27
First Submitted: 2022-08-03 14:39 (UTC)
Last Updated: 2025-02-09 23:57 (UTC)

Pinned Comments

xiota commented on 2024-09-29 22:55 (UTC) (edited on 2024-10-01 10:49 (UTC) by xiota)

This package has been revised to use the variant corresponding to architecture set in some config files. This may cause problems with other packages, so users choosing to do this are (mostly) on their own.

  • makepkg.conf — CARCH="x86_64_v3" (or v2)
  • pacman.conf — Architecture = auto x86_64 x86_64_v2 x86_64_v3
  • /usr/share/devtools/setarch-aliases.d/x86_64_v3 — Contents: x86_64

The default variant is SSE3. This version is the closest available to baseline x86_64, which is currently the only architecture supported by Arch Linux. Other variants have shown no significant performance benefit, while crashing on some users' computers. The default will not be changed unless upstream offerings change or there is no other way to prevent a significant bug. Please refrain from arguing to change default for any other reason.

Alternate PKGBUILDs are available (i386, sse3, sse4, avx, avx2). They may be used by running makepkg -Cp <file>. This is the recommended way to build alternate versions to avoid interfering with other packages.

xiota commented on 2023-10-10 04:01 (UTC) (edited on 2025-02-09 23:58 (UTC) by xiota)

  • This package no longer attempts to autoupdate.

  • Avoid flagging and commenting at the same time for the same issue.

    • Flag for common issues with standard solutions (new version, typos, hash mismatch, etc).
    • Comment for issues requiring explanation or debugging.
    • Use a pastebin for blocks of text more than a few lines.

Latest Comments

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

brauliobo commented on 2025-05-02 03:24 (UTC)

@xiota Indeed, Thorium's biggest and maybe sole issue is its slow (and getting slower) update cycle.

Have you ever tried a merge against upstream, or know the complexities or conflicts that have happened previously?

As a programmer, I'm inclined to try a merge.

xiota commented on 2025-05-02 03:01 (UTC) (edited on 2025-05-02 03:10 (UTC) by xiota)

Choosing what software to use based on features and preferences is valid, but users assume the risk of using an outdated browser. The last release was three months ago, and numerous vulnerabilities have been identified in the Chromium code base during that time.

In terms of performance... Here are Speedometer 3.1 results taken shortly before typing this. The initial run was discarded. Then the next result with error/variance within ±0.5 was recorded.

  • microsoft-edge-stable-bin 136.0.3240.50-1 = 11.0±0.39
  • thorium-browser-avx2-bin 130.0.6723.174-1 = 12.5±0.46
  • thorium-browser-sse3-bin 130.0.6723.174-1 = 12.7±0.50
  • extra/chromium 135.0.7049.114-2 = 13.5±0.31
  • google-chrome 136.0.7103.59-1 = 14.6±0.41

Nothing too surprising. Google engineers with billions at their disposal know how to optimize browser performance. Anyone who still insists the avx2 version is faster is free to use the newly created avx2 package.

brauliobo commented on 2025-05-02 01:42 (UTC) (edited on 2025-05-05 01:03 (UTC) by brauliobo)

The main reason for me to use Thorium is not performance.

It is a fact that Chromium, the open-source Chrome, is becoming less attractive.

They removed the sync. Also, Thorium comes with better defaults, nice flags that make quite a difference (dark mode, hardware accel, unlimited history, etc)

Aftermath commented on 2025-05-01 22:43 (UTC)

Hey @codewithmoss,

I was a user of this program for about a year. I got notified by your comment due to still being subscribed to this package’s notification.

First, I also, was used to believe that AVX2 build of this program is much more performant. But, let me tell you, it doesn’t really provide any significant actual difference.

However, I don’t use thorium any more for the single reason @xiota has mentioned, already.

Also, during a two year of observation, I have found that @xiota is very reasonable and pragmatic. If you can provide enough data and valid arguments to support your opinion, he will be convinced.

xiota commented on 2025-04-30 17:30 (UTC)

@codewithmoss Pinned comment contains instructions to build for different architectures.

The issue has been discussed ad nauseum. No one who has claimed the AVX version is faster than the SSE3 version has bothered to run and interpret benchmarks correctly. Regardless, I recommend against using this browser because upstream does not keep it up to date.

codewithmoss commented on 2025-04-30 16:09 (UTC)

the main problem with you package is it always downloads the SSE3 even my CPU supports AVX2 which one is the latest one and most compatible and FAST therefore try to fix your pkg build file otherwise remove your package i will make my package named as thorium-browser-bin for AVX2 CPU support. and come on bro they people will use SSE3 SSE2 SSE4 if he has installed arch linux in laptop or PC try to be up to date.

That1Calculator commented on 2025-03-19 19:43 (UTC) (edited on 2025-03-19 19:47 (UTC) by That1Calculator)

/usr/share/applications/thorium-shell.desktop has the key Icon=/opt/chromium.org/thorium/thorium_shell.png on line 136, but the file /opt/chromium.org/thorium/thorium_shell.png isn't installed by this package, but the icon thorium-shell is, so the PKGBUILD should probably replace line 136 of thorium-shell.desktop with Icon=thorium-shell.

xiota commented on 2024-12-08 21:39 (UTC)

Checksums in main PKGBUILD are correct. AVX version doesn't use checksums.

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