Same issue, but on Kubuntu 22.04 LTS.
System Specs:
+1
Brave Version 1.51.110 Chromium: 113.0.5672.77 (Official Build) (64-bit)
Was working with KWallet until the latest Brave update.
I use KWallet as the Secret Service provider, of which there can only be one. Running GNOME Keyring/Seahorse (“Password and Keys”) is therefore not an option.
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-71-generic (64-bit)
Thanks Wilson, I’ve just done it. I’ve downgraded Brave to version 1.50.125. Now Brave Sync works again, but as you say it asks for the Sync Code (again). But as I have it from my mobile phone, the sync chain I had already made works again on my computer.
For those of you who also use Flatpak (via Flathub), the command to downgrade Brave to version 1.50.125 is:
sudo flatpak update --commit=2cbeea4c7ddb117f3680e6603bcf9cc799cf515f1e01ea7f1a3ff7e075115f94 com.brave.Browser
@4slam Luckily, it does not break the wallet in any way.
@DanielHuelsmann Thanks for that help. I am sure others will benefit from it.
no workaround yet? this is serious and annoying issue
My concern is that Brave will require GNOME Keyring for sync, i.e., KWallet will no longer be supported. Hopefully there’ll be a fix soon that continues to support both.
Not sure what you mean on workaround. Teams are currently investigating this and other problems. It’s not like it’s a quick “spell check a document” to fix. There’s millions of lines of code within the browser and many ways that things can go wrong.
It is indeed a serious issue, which is why they are trying to replicate it and gather data from people. It’s only affecting a small subset of the people using the browser as well. So it’s like finding a needle in a haystack. Not sure what you’re expecting.
That said, I’m hoping @Alexey can advise later whether they were able to replicate the issue. Then perhaps see if they are @Mattches will be able to say if they think any answers might be a quick turnaround of if this investigation may take a while. Honestly, I’m learning that unless they get lucky or have some really good reports from users to determine causes, that it can take a minimum of a month to investigate and fix an issue. So if you’re expecting it to happen in a day or two, you’ve got the wrong expectations.
Thanks for your suggestion; just rolled back to v1.50.125 from 1.51.110 myself until problem is patched or work-around is sorted.
And yes, @brauliobo, this is a serious problem, but Saoiray is absolutely correct: solving this problem can take weeks. A browser with advanced features for multiple platforms is incredibly complex, and speaking as a developer myself, it takes patience and diligence to troubleshoot properly and test accurately for all the variety of platforms supported. Time is needed.
For anyone who winds up here and is running an installation via adding the repo to their respective *buntu flavor, all I did to roll back was use the following command in terminal, and then re-enter my sync pass-phrase (to be clear: YOU WILL NEED YOUR CURRENT SYNC PASS-PHRASE IN ORDER TO RE-SYNC):
sudo apt install brave-browser=1.50.125
You should get something similar to the following, if all things went well:
neil@FractalNorth:~$ sudo apt install brave-browser=1.50.125
[sudo] password for neil:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be DOWNGRADED:
brave-browser
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 1 not upgraded.
Need to get 107 MB of archives.
After this operation, 2,163 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 https://brave-browser-apt-release.s3.brave.com stable/main amd64 brave-browser amd64 1.50.125 [107 MB]
Fetched 107 MB in 17s (6,442 kB/s)
dpkg: warning: downgrading brave-browser from 1.51.110 to 1.50.125
(Reading database ... 248248 files and directories currently installed.)
Preparing to unpack .../brave-browser_1.50.125_amd64.deb ...
Unpacking brave-browser (1.50.125) over (1.51.110) ...
Setting up brave-browser (1.50.125) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Love the browser. Love the devs. Humbly awaiting a patch.
Here’s the issue report for this: https://github.com/brave/brave-browser/issues/30147. Add a 
if it affects you, and subscribe to track it.
The method described at https://github.com/brave/brave-browser/issues/30147#issuecomment-1536736982 provides a workaround. Now I can use Brave Sync again (version 1.51.114).
I already had that option selected in Kwallet. This work-around changes nothing for me.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.