I wanted to reply here as I’ve been experiencing the issue with Brave and I had a chance to look at it this morning. I also took a look at Chromium and Falkon to see if issues were similar as these are both related browsers offered here. I didn’t have time for a deep dive, so the reply will reflect where I am now. First, from what I see all three browsers crashed for completely different reasons, at least in my case. I will share what I found on Brave and Chromium here and be quick …
Brave: I’ve been observing similar behavior to that of others on this thread, so I started from the command line as such: brave-browser --enable-crash-reporter --enable-logging --v=137. My plan was to see if there was anything in the logs to lead me further. The logs yielded only KWallet-related errors. I don’t use KWallet, or any wallet, so I lazily clicked cancel when starting Brave for the very first time. I attempted to disable to the KWallet subsystem with that setting, but the errors were still present. I then re-enabled KWallet and unchecked the Use KWallet for the Secret Service interface setting. This took away the KWallet errors with Brave on startup and I haven’t had a crash since.
Chromium: I had also started the browser in a similar way with a similar thought process in mind as such… ‘chromium --enable-crash-reporter --enable-logging --v=137’… Generally, I haven’t observed any instability or crashing with this browser at all. However, when I attempt to click Manage Extensions as others have mentioned issues with, the browser does in fact crash. At first glance, the crashes seem to be related to the way that this feature has been “degoogled” and then the subsequent Chromium handling thereafter. Please see a snip of the log here…
[6494:6510:0821/102424.375501:ERROR:url_request.cc(649)] Block URL in URLRequest: https://chrome.9oo91e.qjz9zk/webstore?hl=en
[6494:6510:0821/102424.376259:ERROR:trk_protocol_handler.cc(17)] Blocked URL in TrkProtocolHandler: trk:https://chrome.9oo91e.qjz9zk/webstore?hl=en
Fontconfig error: Cannot load default config file: No such file: (null)
Also, see the dig results for the domain here:
dig 9oo91e.qjz9zk
; <<>> DiG 9.21.0 <<>> 9oo91e.qjz9zk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37088
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;9oo91e.qjz9zk. IN A
;; AUTHORITY SECTION:
. 7168 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025082100 1800 900 604800 86400
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Aug 21 11:32:15 EDT 2025
;; MSG SIZE rcvd: 117
Since the domain doesn’t exist, the Manage Extensions functionality could never work in Chromium. The poster who found and shared an alternative way of installing the extensions would seem to have the right solution for those that require the use of extensions with Chromium. Finally, I actually don’t even like so many things about Brave, so I might just install some extensions to this Chromium and see where it goes.