while I know version numbers are basically just mile markers on the evolutionary highway of software, doesn’t anybody else find that this issue being resolved in beta 1.54.xxx is a little far down the road for this to be patched officially, seeing as we’re at v1.52.xxx?
Who said it’s only coming in 1.54? All that was ever done was to never your test using Nightly. Once the issue is found and fixed, it often gets patched in unless is a major chromium update necessary.
Whenever a Github link is shared, you really should keep an eye on that. For example:
They already had it being pushed for 1.53 the day before you posted here to ask about it coming in 1.54.
I’m not sure which 1.53.xx it will release with, but release schedule is below (give or take a few days):
Link to full release schedule is https://github.com/brave/brave-browser/wiki/Brave-Release-Schedule
Hello,
Brave is complaining about being out of date, as I’m keeping it on 1.51.118 in order to avoid the bug.
So, I need to know : was a fix released in stable yet ? The last version I’m offered to install is 1.52.130.
Thanks
No, not to my knowledge. As shared above, it’s 1.53 that has it coming. At least they put it in for an uplift to 1.53. Otherwise wouldn’t be arriving until 1.54.82 or so.
Not only is it not out yet, but an interim update actually bricked my local instance in a next-level way never seen before. But rather than get into all that, I had to totally remove the system package and move to a flatpak implementation. Damn.
Interesting. I’m just going to tag @mattches so he can have that as a FYI. Also to see if he can confirm if it’s going to be this next update that should have it.
The issue had a cascade effect which then also took out Element messenger, and Web Apps on Mint … barely recovered so far.
@digitalextremist,
If you’re having some issues, it’d be great if you could open your own thread with all of the relevant information so we can take a look.
I appreciate that and have been happy to see how alive the Brave team and community are, but I cannot reproduce the issue without maiming my station again and losing hours.
Also, I changed to a mainline kernel and back to deal with a graphics driver issue near to the time of Brave bricking unrecoverably, so I cannot be sure that had no effect. But if it comes up again, I will definitely report it separately. It felt like it might have been corrupted somehow, and honestly I am just glad to be still in operation and only losing a few hours.
Actually, someone else caught this too:
Dark mode fix is coming in 1.53.
Any other issues should have a new topic created.
Thanks
@digitalextremist @heysoundude @wildernesscoder @t3chn0k and everyone else. I just wanted to tag y’all in to say newest update just hit for Release today. As per the topic shared at NOTICE: Change in Brave Version numbers it jumped to 1.56 instead of going to 1.53.
In any case, once you update to it, this issue should be resolved.
3 Likes