Package Details: chromium-snapshot-bin 133.0.6838.0.r1383276-1

Git Clone URL: https://aur.archlinux.org/chromium-snapshot-bin.git (read-only, click to copy)
Package Base: chromium-snapshot-bin
Description: The open-source project behind Google Chrome (Latest Snapshot)
Upstream URL: https://build.chromium.org
Keywords: browser web
Licenses: BSD
Provides: chromium-snapshot
Submitter: Det
Maintainer: mrxx
Last Packager: mrxx
Votes: 498
Popularity: 0.58
First Submitted: 2015-04-20 12:12 (UTC)
Last Updated: 2024-11-15 11:35 (UTC)

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

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 .. 31 Next › Last »

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.

<deleted-account> 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: http://pastebin.com/je02NYBt. Let me know if you need more.

<deleted-account> 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: http://build.chromium.org/p/chromium/waterfall. The version that most recently passed the requirements gets listed as text here: http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE. 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: http://pastebin.com/GDy8dP9J