I am currently very pissed off, because after updating manjaro, my Brave Browser is not here anymore. Instead I have Brave-Beta Browser now, and all my settings are gone.
Also my Metamask wallet with my crypto coins …
Now, I had a shortcut on my KDE toolbar to my browser. The icon was missing since a while ago (after some updates of course). But it was always working.
However, today I decided to delete that shortcut, because it was annoying me that the icon was missing, and I wanted to add it again, to fix the icon issue.
However, I can’t find it anymore, only Brave Beta. This is when I realized, that my browser is gone.
Is there any f** way to find it again? Or to restore a shortcut on the KDE toolbar?
Any help is greatly appreciated …
Thx!
I just see that it was removed on the 12.10.2021, I think since then the icon went missing for my shortcut in the KDE taskbar. However, it would still open it with all my settings (and the icon was orange). Today after deleting the shortcut, I can only open the “new” Brave with the blue icon. For some reason, i believe that there must be a way, to open the “old” browser again?
First I nnotice you have been using brave beta for almost a year now.
It wasnt … it was renamed. And back in October.
Notice brave-beta-browser → brave-browser-beta
(and the corresponding version numbers)
There should be no ‘new brave’ … and certainly not from an icon deletion.
Its possible you had a special launcher I suppose.
Maybe that in conjunction with a particular profile?
You maybe want to look in your home directory (or .config or .cache) for if the data still exists.
…though I just thought of another possibility … do you happen to use snaps or flatpaks and possibly installed another brave that way?
It is both times starting the same browser “the new version” …
~ ❯ brave-browser-beta ✘ INT 15:22:01
(brave:13778): Gtk-WARNING **: 15:22:16.397: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version
[13812:13812:1230/152216.531419:ERROR:vaapi_wrapper.cc(1123)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[13812:13812:1230/152216.531542:ERROR:vaapi_wrapper.cc(1070)] FillProfileInfo_Locked failed for va_profile VAProfileH264Main and entrypoint VAEntrypointVLD
[13812:13812:1230/152216.531715:ERROR:vaapi_wrapper.cc(1123)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[13812:13812:1230/152216.531788:ERROR:vaapi_wrapper.cc(1070)] FillProfileInfo_Locked failed for va_profile VAProfileH264High and entrypoint VAEntrypointVLD
[13778:13827:1230/152218.618230:ERROR:chrome_browser_main_extra_parts_metrics.cc(226)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends.
[13778:13827:1230/152218.618253:ERROR:chrome_browser_main_extra_parts_metrics.cc(229)] crbug.com/1216328: Checking Bluetooth availability ended.
[13778:13827:1230/152218.618259:ERROR:chrome_browser_main_extra_parts_metrics.cc(232)] crbug.com/1216328: Checking default browser status started. Please report if there is no report that this ends.
[13778:13827:1230/152218.697639:ERROR:chrome_browser_main_extra_parts_metrics.cc(236)] crbug.com/1216328: Checking default browser status ended.
~ ❯ brave-beta 16s 15:22:32
#
(brave:14156): Gtk-WARNING **: 15:22:34.460: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version
[14191:14191:1230/152234.624625:ERROR:vaapi_wrapper.cc(1123)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[14191:14191:1230/152234.624700:ERROR:vaapi_wrapper.cc(1070)] FillProfileInfo_Locked failed for va_profile VAProfileH264Main and entrypoint VAEntrypointVLD
[14191:14191:1230/152234.624772:ERROR:vaapi_wrapper.cc(1123)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[14191:14191:1230/152234.624827:ERROR:vaapi_wrapper.cc(1070)] FillProfileInfo_Locked failed for va_profile VAProfileH264High and entrypoint VAEntrypointVLD
Failed to parse JSON adblock resources: EOF while parsing a value at line 1 column 0
[14156:14186:1230/152236.735066:ERROR:chrome_browser_main_extra_parts_metrics.cc(226)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends.
[14156:14186:1230/152236.735100:ERROR:chrome_browser_main_extra_parts_metrics.cc(229)] crbug.com/1216328: Checking Bluetooth availability ended.
[14156:14186:1230/152236.735106:ERROR:chrome_browser_main_extra_parts_metrics.cc(232)] crbug.com/1216328: Checking default browser status started. Please report if there is no report that this ends.
[14156:14186:1230/152236.803401:ERROR:chrome_browser_main_extra_parts_metrics.cc(236)] crbug.com/1216328: Checking default browser status ended.
~ ❯ pacman -Qo '/usr/bin/brave-beta' '/usr/bin/brave-browser-beta' 16s 15:22:50
/usr/bin/brave-beta is owned by brave-browser-beta 1.34.57-1
/usr/bin/brave-browser-beta is owned by brave-browser-beta 1.34.57-1
~ ❯
OK … well you should be able to move your old profile to the new directory.
I dont know about the internals of brave … so how picky you are is up to you, but you should more or less be able to drag+drop the contents to the proper location.
Hint. You should use sync from brave browser settings. It gives you a 12 word phrase password, where you can restore all the settings and pages at any device or at new installations. Firefox has it too, and saves a lot of trouble by trying to restore the previous version with the profile datas, even it mostly works.
This was basically a quirk of the nomenclature change.
And as pacman should not touch anything in your home … the old path was left, while the new one was automatically generated with default/empty contents.
To put it another way … you could have converted your old profile to the new correct location.
The package upgrade would not do this for you, but you could have also edited the directory name to add the -Beta if that was the new syntax (removing the the automatically created one if it exists - which would only happen if brave was launched without one existing).
“the new version” …
