Can't reopen Brave after I close it

[Alexy]

After I log in, I can open and use Brave, no problem.
After I close it, when I try to open it again, it won’t open.
When I log out and back in, same behavior, It opens but won’t re-open.

System: EndeavourOS, X11, Qtile; Brave installed with yay (brave-bin).
The system is up to date, including Brave (135.1.77.100).

I installed Brave a little while ago (probably 1.77.95 or 1.77.97) and after encountering this behavior I thought maybe it’ll be fixed in an update, but it persisted.

Detailed breakdown (launched from terminal):

1. KDE wallet pop-up, I click “Cancel”.
2. Brave starts, works normally, I close it.
3. I try to open it again, KDE wallet pop-up, I Click “Cancel”; I get these errors:

brave:21623): libsecret-WARNING **: 20:39:49.231: received unexpected result type ao from Completed signal instead of expected o

(brave:21623): GLib-GIO-CRITICAL **: 20:39:49.231: g_task_return_error: assertion ‘error != NULL’ failed

(brave:21623): GLib-GIO-CRITICAL **: 20:39:49.231: GTask secret_service_real_prompt_async (source object: 0x4b400011d10, source tag: 0x77433ca96fd0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.

PS: Not as important, but what’s the deal with KDE Wallet popping up each time, should I do anything about it?

Solution/Update:

The KDE wallet was the problem. I ended up just setting one up (using blowfish). I installed kwalletmanager for this, though it may have worked without it too. Now Brave prompts me for a password on the first launch but not for subsequent launches.
I can live with this, though only Brave does this. Firefox and Vivaldi (chromium based, just like Brave) don’t do this, they start normally each time.

Thank you all for the replies and suggestions.

Additional notes:

Before setting up the KDE wallet I installed the Gnome desktop environment to see if maybe there was something wrong with my Qtile setup.
In Gnome I was also prompted for a password, though this time by a Gnome app, which I could also cancel, however this time I could open and close Brave as many times as I wanted.

[keescase]

Welcome to the forum

Does the popup screen looks like in the below mentioned topic ?

Kdewallet popup?

I recently did a fresh installation of EOS with Plasma. I already used it before though i can’t remember that i would get a Popup that demands the creation of a Kdewallet when trying to change Networksettings (similar to the image i uploaded). I remember usually it would just ask me for my root pass when changing certain settings. So what should do there? Just creating a wallet? [Method]

[Alexy]

Yes. I attached a screenshot in OP, the text is a bit different, but says basically the same thing.

[keescase]

Try the top option and leave the following boxes blank and click on ok or something like that.

[cscs]

@Alexy

After I log in, I can open and use Brave, no problem.
After I close it, when I try to open it again, it won’t open.

Great.
Now you can focus on using a real browser that actually respects you and your privacy.

@Alexy

PS: Not as important, but what’s the deal with KDE Wallet popping up each time, should I do anything about it?

As to kwallet popping up later after sign in ..
This either means there is something wrong with your kwallet configuration
OR
Probably the most likely - you are using autologin.

The wallet will not be automatically opened during automatic sign in because no password/unlocking action has taken place. Instead the first thing to require the wallet will then .. prompt for wallet unlocking. And normally I would expect this to occur even earlier due to something like wireless credentials .. but thats a digression.

Actually in your case its not even wallet unlocking thats popping up but rather the initial step of creating a wallet .. which returns us back to the first statement - wallet is certainly not properly configured as it appears it is not configured at all.

The KDE wallet stores various things (like wireless passwords, browser profile keys, etc) .. and, optionally if securely saved then using encryption though it can save things in plain text as well.

KDE Wallet - ArchWiki

[limotux]

@Alexy

Detailed breakdown (launched from terminal):

1. KDE wallet pop-up, I click “Cancel”.
2. Brave starts, works normally, I close it.
3. I try to open it again, KDE wallet pop-up, I Click “Cancel”; I get these errors:

First of all welcome @Alexy to the wonderful world of EndeavourOs and to this wonderful community.
My 2 cents.
1- I wonder if this wallet is the issue. I don’t know.
2- I wonder how would it be if you installed from their website, tha’t what I did and working fine with me. https://brave.com/download/ Try and see if this helps.

[cscs]

@limotux

2- I wonder how would it be if you installed from their website, tha’t what I did and working fine with me. https://brave.com/download/ Try and see if this helps.

This is rarely the greatest of ideas for a number of reasons.

• 1. Lacking any distro-specific patches and the like.
• 2. Filesystem naturalization - or how #1 may mean the thing and associated items are not properly placed.
• 3. No dependency resolution.
• 4. Updates - or lack thereof. You gotta visit that website again virtually every day.
• 5. Being outside the package manager can mean many things, but a future ‘X exists on filesystem’ is one such possibility.

And some more things that go along with this approach to adding software to your linux system.

Its still yours to do with as you like .. but normal operation does not include searching for some website to download your application from.

[limotux]

@cscs

• 3. No dependency resolution.
• 4. Updates - or lack thereof. You gotta visit that website again virtually every day.
• 5. Being outside the package manager can mean many things, but a future ‘X exists on filesystem’ is one such possibility.

Well, this was what worked with me.
I am not sure about the updates! Maybe the repo is added somehow perhaps and it would be updated? I am not that expert.

Btu I won’t need to visit everyday, maybe only when I read something about a new version or maybe once a month or even every 2 or 3 months. I am not really after the latest software.

The reason I am on EndeavourOS (other then being a wonderful community and a wonderful distro) I like the idea of a rolling release, I see no point in installing over and over. Plus the minimal install, plus how responsive and light on resources compare to any other non Arch distro.

[cscs]

@limotux

I am not sure about the updates! Maybe the repo is added somehow perhaps and it would be updated? I am not that expert.

No.
Nothing of the sort at all.
You downloaded and manually unpacked some third party files onto your system ~somehow~.
And thats how it is going to stay unless you do something about it.
It is not the same as getting the package from the repos, not even as good as using an AUR PKGBUILD .. its the same as unzipping something into root. Thats it. Whatever it did is whatever it did.

@limotux

Btu I won’t need to visit everyday, maybe only when I read something about a new version or maybe once a month or even every 2 or 3 months.

That is an insane way to deal with things .. not just on a rolling distro where something like other libraries will quickly become incompatible .. but on a browser no less?
The thing you use to interface with the internet and arguably one of the most common attack surfaces?
You want to leave that out of date for months at a time?

Do you happen to be in the market for a bridge?

[limotux]

@cscs

That is an insane way to deal with things .. not just on a rolling distro where something like other libraries will quickly become incompatible

I know for sure. But I just think if it works it works. If something becomes incompatible it is Brave that will break … mmm… I just exaggerated when I said 2 or 3 months. Honestly I was just exaggerating.

[Bink]

Welcome to the community @Alexy

@Alexy

After I log in, I can open and use Brave, no problem.
After I close it, when I try to open it again, it won’t open.
When I log out and back in, same behavior, It opens but won’t re-open.

You could try loging into your system without starting Brave, and completely clearing Brave’s configs and cache and starting fresh.

Warning: This will delete all of Brave’s browsing data, bookmarks, saved passwords, settings, etc.

rm -R ~/.config/brave ~/.config/BraveSoftware ~/.cache/Brave ~/.cache/BraveSoftware

Now try launching Brave.

[Alexy]

I ended up just making a KDE wallet w password and all.

[Alexy]

I don’t have autologin, and yes, I didn’t have a KDE wallet set up. I updated the OP with the solution.

[Alexy]

The wallet was the issue, I updated the OP with the solution.

[Alexy]

I tried that already, didn’t change anything. I updated the OP with the solution.

[limotux]

@Bink

You could try loging into your system without starting Brave, and completely clearing Brave’s configs and cache and starting fresh.

Warning: This will delete all of Brave’s browsing data, bookmarks, saved passwords, settings, etc.

rm -R ~/.config/brave ~/.config/BraveSoftware ~/.cache/Brave ~/.cache/BraveSoftware

@Bink
This sounds perfect. Much smarter and practical than what I suggested.
If OP reports it worked, just to make @cscs ok, I will uninstall what I installed from brave website and install it with yay so I get updates seamlessly!

I hope OP will report back if this works.
Or, @Bink should I just do it and install with yay?

[Bink]

With Arch/EndeavourOS, I would advocate using the package management system (pacman, yay, makepkg, etc) over any other option.

An exception that I might give a pass to though, is an AppImage, or Flatpack. These remain self contained, so won’t litter your system with untracked junk, provided you’re keeping track of the AppImages or Flatpacks. I would also consider them at least as safe, if you obtained it from the official developer’s website.

All that said, I’ve had a quick glance at the Brave installer script on their website, and it is leveraging the native tools for each platform. In the case of EndeavourOS, that’s yay, so I suspect it has installed it correctly for you, after all.

What’s the output of:

yay -Q | grep brave

[cscs]

@Bink

All that said, I’ve had a quick glance at the Brave installer script on their website, and it is leveraging the native tools for each platform. In the case of EndeavourOS, that’s yay, so I suspect it has installed it correctly for you, after all

I would have never expected that but it does seem so.

Huh. Next time I will double check before assuming.

Though they do use -Sy brave-bin .. the partial-upgrade version of installing packages.

[limotux]

@Bink

What’s the output of:

yay -Q | grep brave

[limo@eos SysBoost]$ yay -Q | grep brave
brave-bin 1:1.77.100-1
[limo@eos SysBoost]$ 

So, I have it actually installed from our AUR repos. Right?

@Bink

I’ve had a quick glance at the Brave installer script on their website, and it is leveraging the native tools for each platform. In the case of EndeavourOS, that’s yay, so I suspect it has installed it correctly for you, after all.

[cactux]

elif available pacman; then
        if pacman -Ss brave-browser >/dev/null 2>&1; then
            show $sudo pacman -Sy --needed --noconfirm brave-browser
        else
            aur_helper="$(first_of paru pikaur yay)" ||
                error "Could not find an AUR helper. Please install paru/pikaur/yay to proceed." "" \
                      "You can find more information about AUR helpers at https://wiki.archlinux.org/title/AUR_helpers"
            show "$aur_helper" -Sy --needed --noconfirm brave-bin

This is the relevant part of Brave’s installer script for Arch.
So if you have yay already installed, it will use it to install brave-bin from AUR.