Brave Version 1.25.68 on Xubuntu 16.04.
I have another desktop with Manjaro that updated to the current stable version yesterday. Today, I wanted to update my 16-04 via command line, but the result of sudo apt dist-upgrade said all packages are up to date.
I searched the web and tried a few solutions, but nothing worked.
The only thing I can think of is because 16.04 is no longer supported by Ubuntu/Canonical, it somehow prevents Brave from updating.
I installed Brave on this machine thinking it would still get updates beyond the system’s eol.
Thanks in advance for any help/advice.
1 Like
1.25.68 is currently the latest version:
The Brave browser is a fast, private and secure web browser for PC, Mac and mobile. Download now to enjoy a faster ad-free browsing experience that saves data and battery life by blocking tracking software.
@fmarier
opened 05:48PM - 02 Jun 21 UTC
closed 08:25PM - 03 Jun 21 UTC
OS/Desktop
QA/No
release-notes/exclude
Feel free to copy this into an issue if you want to keep track of items per-mile… stone.
Be super sure that <version> is replaced with the version you wish to use.
### Prerequisites
- [x] Check that Brave is pulling the correct Tor executable listed under https://github.com/brave/tor_build_scripts/blob/master/env.sh#L6
- [x] macOS
- [x] Windows
- [x] Linux
- [x] Double check the previous release/milestone and ensure everything has been QA'd
- **Note:** If there's issues that need to be checked, create a `master` GH issue that lists the issues that need to be QA'd
- [x] Consult with the security team to ensure that all security issues have been included.
- [x] Consult with PR team (@catherinecorre) and provide heads up on release timing, screenshots, other deliverables.
### Release Notes to Staging
- [x] Mark closed issues in github as release-notes/exclude or release-notes/include.
- [x] Commit release notes to [CHANGELOG_DESKTOP.md](https://github.com/brave/brave-browser/blob/master/CHANGELOG_DESKTOP.md) in brave-browser master branch, must be completed before release to production Jenkins build job is run.
- [x] Stage release notes to https://github.com/brave/brave-browser/releases/
### Certification and Builds
- [x] Upload builds to Omaha test channels (`86-r-test`, `64-r-test`, `test`(mac))
- [x] Log into Fastly, clear CDN cache for: `updates-cdn.bravesoftware.com`, `updates.bravesoftware.com`
### Test Staging for Updates
- [x] Install a prior version of Brave and update via `test` channels (`86-r-test`, `64-r-test`, `test`(macOS))
- [x] Confirm version matches expectations
- [x] QA summary and sign off report under #release via Slack.
### Release to production download locations
- [x] Publish github release (remove 'pre-release' checkmark)
- [x] Upload Mac/Win build to Omaha production channels (`x86-rel`, `x64-rel`, `stable`(mac))
- [x] Sign Linux builds and upload to S3 repositories
- [x] Upload Mac `.dmg` and `.pkg` to S3 bucket (i.e. `aws s3 cp ./Brave-Browser-Dev.dmg s3://brave-browser-downloads/latest/Brave-Browser-Dev.dmg --acl public-read`)
- [x] Upload Windows stub and silent installer to S3 bucket using similar command to Mac dmg above (i.e `BraveBrowserSetup.exe`, `BraveBrowserSetup32.exe`, `BraveBrowserSilentSetup.exe`, `BraveBrowserSilentSetup32.exe`)
### Clear Production Fastly cache
- [x] Clear Fastly cache for: `brave-browser-downloads.s3.brave.com`, `brave-browser-apt-release.s3.brave.com`, `brave-browser-rpm-release.s3.brave.com`
### Updates Testing on Production
- [x] Wait for confirmation that Windows live update works
- [x] Ensure that `delta` upgrades are working on `Win x64` platforms
- Save the [`configuration`](https://github.com/brave/brave-browser/wiki/(WIP)-Desktop-Release-Checklist#example-of-delta-upgrade-occurring) into a file named `BraveUpdate.ini` and move into `C:\`
- Upgrade and you should see `C:\Omaha log.txt`. Confirm that a [`delta`](https://github.com/brave/brave-browser/wiki/(WIP)-Desktop-Release-Checklist#example-of-delta-upgrade-occurring) upgrade has occurred.
- [x] Wait for confirmation that macOS live update works
- [ ] Wait for confirmation that Linux live update works
### Download & Install Binaries from Brave.com
- [x] download binary from https://brave.com on `Win x64` - `https://laptop-updates.brave.com/latest/winx64`
- [x] download binary from https://brave.com on `Win x86` - `https://laptop-updates.brave.com/latest/winia32`
- [x] download binary from https://brave.com on `macOS` - `https://laptop-updates.brave.com/latest/osx`
### Announcements
- [x] Publish the release notes to `GitHub`
- [x] Publish the release notes to `https://www.brave.com/latest`
- [x] Announce release on https://community.brave.app/ (@Hollons)
- [x] Announce release on https://www.reddit.com/r/brave_browser/ (@Hollons)
- [x] Notify #announcements of the latest release with a link to the release notes
### Closing milestones
- [x] Set a release date (if missing) and close the appropriate milestone under https://github.com/brave/brave-browser/milestones
- [x] Set a release date (if missing) and close the appropriate milestone under https://github.com/brave/brave-core/milestones
---------
##### BraveUpdate.ini
```
[LoggingLevel]
LC_CORE=5
LC_NET=4
LC_PLUGIN=3
LC_SERVICE=3
LC_SETUP=3
LC_SHELL=3
LC_UTIL=3
LC_OPT=3
LC_REPORT=3
[LoggingSettings]
EnableLogging=1
LogFilePath="C:\Omaha log.txt"
MaxLogFileSize=10000000
ShowTime=1
LogToFile=1
AppendToFile=1
LogToStdOut=0
LogToOutputDebug=1
[DebugSettings]
SkipServerReport=1
NoSendDumpToServer=1
NoSendStackToServer=1
```
##### Example of delta upgrade occurring
```
<response protocol="3.0" server="prod">
<daystart elapsed_seconds="58705" elapsed_days="5042"/>
<app appid="{AFE6A462-C574-4B8A-AF43-4CC60DF4563B}" status="ok">
<updatecheck status="ok">
<urls>
<url codebase="https://updates-cdn.bravesoftware.com:443/delta/Brave-Release/x64-rel/win/86.1.15.76/86.1.15.75/"/>
</urls>
<manifest version="86.1.15.76">
<packages>
<package name="brave_installer-delta-x64.exe" required="true" size="1886888" hash="/NhWY/HKtoNx0o90SWy3c8GfeJk=" hash_sha256="6e3c96c67b286b4fb13fd69550ef76bc0480516575ced1dd15f8157e99591439"/>
</packages>
<actions>
<action event="install"/>
<action event="update"/>
</actions>
</manifest>
</updatecheck>
<ping status="ok"/>
</app>
</response>
```
The latest version is 1.25.70, I’m currently using it.
You’re right for Windows & Mac but that version has not been published for Linux because https://github.com/brave/brave-browser/issues/16204 is still not fixed on that platform. We are working on another point release which will be published on all platforms.
So on Linux, 1.25.68 is still the latest version.
It’s my mistake then, apologies.
I thought the release (milestone) passing the manual tests over here:
opened 08:30PM - 02 Jun 21 UTC
closed 03:57PM - 03 Jun 21 UTC
OS/Desktop
OS/Linux
QA Pass-Linux
QA/Yes
release-notes/exclude
tests
### Installer
- [x] Check signature: If OS Run `spctl --assess --verbose /Ap… plications/Brave-Browser-Beta.app/` and make sure it returns `accepted`. If Windows right click on the `brave_installer-x64.exe` and go to Properties, go to the Digital Signatures tab and double click on the signature. Make sure it says "The digital signature is OK" in the popup window
### Widevine
- [x] Verify `Widevine Notification` is shown when you visit Netflix for the first time
- [x] Test that you can stream on Netflix on a fresh profile after installing Widevine
- [x] Verify `Widevine Notification` is shown when you visit HBO Max for the first time
- [x] Test that you can stream on HBO Max on a fresh profile after installing Widevine
## Update tests
- [x] Verify visiting `brave://settings/help` triggers update check
- [ ] Verify once update is downloaded, prompts to `Relaunch` to install update
#### Startup & Components
- [x] Verify that Brave is only contacting `*.brave.com` endpoints on first launch using either `Charles Proxy`, `Fiddler`, `Wireshark` or `LittleSnitch` (or a similar application)
- [x] Delete Adblock folder from browser profile and restart browser. Visit `brave://components` and verify `Brave Ad Block Updater` downloads and update the component. Repeat for all Brave components
### Upgrade
- [x] Make sure that data from the last version appears in the new version OK
- [x] Ensure that `brave://version` lists the expected Brave & Chromium versions
- [x] With data from the last version, verify that
- [x] Bookmarks on the bookmark toolbar and bookmark folders can be opened
- [x] Cookies are preserved
- [x] Installed extensions are retained and work correctly
- [x] Opened tabs can be reloaded
- [x] Stored passwords are preserved
- [x] Sync chain created in previous version is retained
- [x] Social media blocking buttons changes are retained
- [x] Rewards
- [x] Wallet balance is retained
- [x] Auto-contribute list is retained
- [x] Both Tips and Monthly Contributions are retained
- [x] Wallet panel transactions list is retained
- [x] Changes to rewards settings are retained
- [x] Ensure that Auto Contribute is not being enabled when upgrading to a new version if AC was disabled
- [x] Ads
- [x] Both `Estimated pending rewards` & `Ad notifications received this month` are retained
- [x] Changes to ads settings are retained
- [x] Ensure that ads are not being enabled when upgrading to a new version if they were disabled
- [x] Ensure that ads are not disabled when upgrading to a new version if they were enabled
And the issue receiving the “QA Pass” label over here:
opened 05:14PM - 02 Jun 21 UTC
closed 02:43AM - 03 Jun 21 UTC
OS/Desktop
QA Pass-Linux
QA Pass-Win64
QA Pass-macOS
QA/Yes
feature/wallet
release-notes/include
release/blocking
https://github.com/chromium/chromium/commit/07ef8d73c7b010a549c9bb960c6f7c73f134… 6fe5 breaks the U2F support of Ledger.
This is a problem with the transport being used to send arbitrary data, our wallet and other wallets still use the Ledger U2F transport though. So this issue is to track a temporary revert as we work out how to communicate over webhid instead.
means that the version could be released for the specified platform. Duly noted.
Carson
June 5, 2021, 11:56am
6
Maybe it’s different for Arch vs Ubuntu?
[keith@vug ~]$ lsb_release -dc
https://aur.archlinux.org/packages/brave-bin/
Change log for updates to Brave Browser
Unless you’re using Brave from the snap version, yeah, if you depends on the repository, it’s no long will work for the average user, unless you pay for more support.
16.04 was released on April, 2016 and ended support on April, 2021. I recommend you to switch to a new version of Ubuntu, e.g. the latest LTS which is 20.04.
Or you can switch to another distribution which is more up-to-date, like Manjaro.
I also have Brave on Xubuntu 18.04, and that one did not update.
For my 16.04 this is understandable, but why won’t it update on my 18.04?
After reading the current events here in the community, I’d guess the update/upgrade issue that brought me here will be a low priority for a while.
So, what the heck…it still works.
Since I won’t be getting any updates, I reverted back to version 1.24.86, just to get rid of that “tab-search” thing.
Carson
system
July 6, 2021, 9:32pm
10
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.