Data restoring, possible somehow?

[goingnutsffs]

Description of the issue:

I have encountered a bug yesterday which is related to those:

[BUG] Brave won't show window after setting ozone flag to Wayland

Description of the issue: Ever since I updated to the latest version of brave browser on the dnf repo, it stopped launching. To get it to launch, I had to delete ~/.config/BraveSoftware. Steps to Reproduce (add as many as necessary): 1. 2. 3. Visit brave://flags and set Preferred Ozone Platform to Wayland or Auto on a Wayland session (Fedora KDE Wayland). Relaunch to apply, as the notification prompts you to do. Actual Result (gifs and screenshots are welcome!): Nothing shows up except an e…

Latest update broke Ozone Wayland; Brave window invisible

Description of the issue: Brave window invisible How can this issue be reproduced? Set Ozone Wayland in brave://flags Relaunch Brave does open, but the window is invisible/not drawn properly & moving other windows over Brave causes “visual smearing-artifacts” Expected result: It still functioning, like before the update Brave Version( check About Brave): 1.65 I think. Latest Brave Stable & Beta from Flatpak, and the AUR. Additional Information: Arch Linux (up2date) AMD CPU + GPU KDE Pla…

Latest upgrade (v1.65.114) in Fedora won't launch

Description of the issue: Latest update does not work in Fedora. How can this issue be reproduced? [image] Upgrade to 1.65.114 try to launch brave Does not open, but all the processes are running. May or may not require a force quit after right clicking icon and selecting quit. System reboot does not help. Expected result: It opens normally Brave Version( check About Brave): 1.65.114 Additional Information: “sudo dnf downgrade brave-browser” fixes the issue

Did not cross my mind to either downgrade or check the forums here.

I was using browser normally, closed it and could not re open again, a window appeared but it was invisible. I started banging my head to the table tryina fix this, and ultimately made the bad decision to remove brave and copy data from the three folders in ~/.var/app/com.brave.Browser .

Reinstalled and it worked somehow.

Tried putting those files back, and browser wont launch.

Removed those files and reinstalled, launched normally.

Now, i am on dual boot windows and fedora, the brave browser was (and is) on my sync chain, and properly shows that fedorawas last active yesterday.

Went back to fedora, launched the fresh brave install and added it to the sync chain. Nothing syncing except for bookmarks.

I’m seeing from other posts that there is currently some gibberish going on with sync features.

Is there any way i can restore stuff from my previous install?

How can this issue be reproduced?

By being a dumbass like me

Expected result:

Things just work

[cyangalaxy]

If you had set Brave to launch with Wayland using brave://flags, one way would be to delete this file:

~/.var/app/com.brave.Browser/config/BraveSoftware/Brave-Browser/Local State

This file contains saved flags from brave://flags, but I think it may also contain normal settings…

Maybe not the best tip, but that’s my first idea.

(Maybe forcing X11 using launch-arg or brave-flags.conf could override the flag in brave://flags ?)

Or, do you not have the backed up (& broken) com.browser.Brave anymore?

[real_username]

@cyangalaxy

~/.var/app/com.brave.Browser/config/BraveSoftware/Brave-Browser/Local State

Try putting the data back into the folder, then running flatpak run com.brave.Browser --disable-experiments. I’m not sure if that’s the correct way to pass command line arguments into a flatpak app, but try it anyway.