Description of the issue: When connecting to my company site, the authentification phase is stuck in a loop (all scripts and cookies allowed, no shield).
I don’t expect any help on this specific problem (my company site could be the problem), but I temporarily need to go back to the previous version and I haven’t found enough information to do this. How can this issue be reproduced? non applicable (You must have an account) Expected result: authorization to connect
Brave Version( check About Brave):v1.73.89 (Nov 13, 2024)
Additional Information: I need to return to the previous stable version (1.71.123), until the problem is fixed from either side (my company site or the browser). I’ve downloaded the .rpm from the github site, but I don’t know which procedure I should follow and which command lines I should use.
I’ve already read several posts about the problem of reinstalling old versions but there is no usefull information (except for the github address of old releases). Here are some of these posts:
This is something you should do via your package manager. For example, on Fedora the command would be sudo dnf downgrade brave-browser. When I run that I get the following information and a prompt to continue or cancel.
The problem is that I can’t find the debian package for intel x64 architechture on the dowload page of the previous stable version:
Only rmp package is listed, which is not convenient for ubuntu. Debian packages are only proposed for arm and amd.
And I’d be glad to know how to safely proceed with my profile (since I don’t want to use share it with the sync servers). Although it is a minor issue since I’ve a backup from last month.
I am really surprised, is there anything I’m missing ?
@289wk Thank you for the link, I used this way to install Brave in the first place on ubuntu. Unfortunately it does not explain how to install old releases.
I solved the problem, thank you both @289wk , @Mythical5th for your support. I describe here what I did so that people having the same problem (Brave malfunctionning after an update) can temporaly overcome the problem.
Find the first previous stable release (very tedious , as others have already mentionned). You have to scroll all the way back and all pages until you find the first release that is NOT nightly, NOT Beta, NOT a pre-release. Even if you know the number the release search engine of the page can’t find it !
When you’ve find it, scroll the Assets list on the page (here the first previous stable release, v1.71.123, is 2 weeks old), to find the package corresponding to your OS and architecture
If your OS is ubuntu and you have an intel x64 architecture, there is no specific debian package for you but you can use the AMD64 debian package brave-browser_1.71.123_amd64.deb, it will work. Download it with the signature file. You can check that the download is correct with command sha256sum
sha256sum brave-browser_1.71.123_amd64.deb
Remove the malfunctionning version with your package manager
You can then install it either with your package manager or with dpkg
sudo dpkg -i brave-browser_1.71.123_amd64.deb
My profile was preserved.
Happy ending !
P.S. I like this browser, I am sure this is only temporary
Why do they make is so hard to find previous releases ??
The latest version (very) often has defects. Being able to fall back to a working version is needed - frequently.
A list of release versions is needed. A list of -just- the released versions. Add to the list every time a release is done (an extra 15 seconds in the release process)
@289wk ,
Very useful indeed ! Exactly what I was looking for - together with a number of other people.
Unfortunately this is not the link you can find on the official website. The Github site is mentionned with the link https://github.com/brave/brave-browser/releases
with the problem I mentionned (hard to find the previous stable release). Could it be possible to mention also the changelog ? It will be very usefull.
Thank you for the search examples. I’ve been wandering on the list of issues and I think that every thing is about the code of the browser itself (code, bugs, issues, organisation, releases, check, etc.)
There is actualy a label “reports/site-issues” with very few issues (4).
I’ve created a gitHub account for this Brave problem (I don’t like mixing professional activities with personal matters).
I’ve created a new issue #42435, but I can’t label it.
Since it’s an issue about the website, not the browser, I hope it will be labelled “reports/site-issues”.