Puppy Linux Discussion Forum

I downloaded and installed the browser from link below, but it won't start when I click launch. Could it have something to do with spot or permissions?

Thanks!

https://mega.nz/folder/6LYmRTzK#mXaNPN4 ... r/KHhSWKJT

Open a terminal in the same directory as the LAUNCH script.
In the terminal, type:

./LAUNCH

Post the errors

I found it.

What filesystem is your partition? Mine won't start on an ntfs partition but does on a linux filesystem. Maybe something to do with the linking process being a portable application, not sure?

Trapster wrote: ↑Tue Jan 09, 2024 2:50 pm

Open a terminal in the same directory as the LAUNCH script.
In the terminal, type:

Code: Select all

./LAUNCH

Post the errors

Why is Brave automatically accessing the internet without permission and attempting an update?
Is the browser refusing to run because it has not been updated?

amethyst wrote: ↑Tue Jan 09, 2024 2:55 pm

What filesystem is your partition? Mine won't start on an ntfs partition but does on a linux filesystem. Maybe something to do with the linking process being a portable application, not sure?

I believe it is ext4, but is there a way to easily check it?

@Governor :-

Coupla points here.

With the 'portable' versions of all these Chromium-based browsers, we've disabled the internal update mechanism. Quite simply, if you let that run, it then goes and writes the updated version into the main filesystem as normal, and that's NOT what we want. We want to keep the portable browser self-contained within its own directory, so fredx181 has written update scripts for most of them.

You run this from a terminal in the portable directory itself. In other words, you go into the portable directory, hit the key above 'Tab' - the 'back-tick' key - and this will open a terminal. Then, in this case, you type

./UpdateBrave

.....hit 'Enter', and just leave it to run through the update process. It'll tell you when it's done.

=======================

However; this should NOT prevent it from firing-up, even when out-of-date. If you start it from a terminal - again, open a terminal beside the 'LAUNCH' script, and run

./LAUNCH

.....what output are you getting.?

(None of the 'zilla-based browsers have this problem.......probably because Firefox et al were always written to be able to run as a self-contained application, dating all the way back to when NetScape Navigator 'morphed' into the very first Firefox. Thus, the internal updater was written to keep that update 'internal'.)

Mike.

Governor wrote: ↑Tue Jan 09, 2024 3:06 pm

Trapster wrote: ↑Tue Jan 09, 2024 2:50 pm

Open a terminal in the same directory as the LAUNCH script.
In the terminal, type:

Code: Select all

./LAUNCH

Brave won't start.pngPost the errors

Why is Brave automatically accessing the internet without permission and attempting an update?
Is the browser refusing to run because it has not been updated?

Very strange what you get in the address bar (looking at the pic you posted),

it's very different for me first time launching brave :

Anyway, as said, post the content of the terminal output when running ./LAUNCH .

fredx181 wrote: ↑Tue Jan 09, 2024 8:30 pm

Anyway, as said, post the content of the terminal output when running ./LAUNCH .

root# ./LAUNCH
[773:773:0110/084912.132420:ERROR:message_box_dialog.cc(146)] Unable to show a dialog outside the UI thread message loop: Failed To Create Data Directory - Brave cannot read and write to its data directory:

/mnt/nvme0n1p3/Downloads/Brave
[773:773:0110/084912.172022:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd6 was not provided by any .service files
[773:773:0110/084912.172074:ERROR:kwallet_dbus.cc(112)] Error contacting kwalletd6 (isEnabled)
[773:773:0110/084912.172374:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files
[773:773:0110/084912.172410:ERROR:kwallet_dbus.cc(81)] Error contacting klauncher to start kwalletd6
[773:773:0110/084912.172640:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd6 was not provided by any .service files
[773:773:0110/084912.172659:ERROR:kwallet_dbus.cc(503)] Error contacting kwalletd6 (close)
[773:773:0110/084912.180193:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd5 was not provided by any .service files
[773:773:0110/084912.180218:ERROR:kwallet_dbus.cc(112)] Error contacting kwalletd5 (isEnabled)
[773:773:0110/084912.180396:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files
[773:773:0110/084912.180406:ERROR:kwallet_dbus.cc(81)] Error contacting klauncher to start kwalletd5
[773:773:0110/084912.180573:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd5 was not provided by any .service files
[773:773:0110/084912.180588:ERROR:kwallet_dbus.cc(503)] Error contacting kwalletd5 (close)
[773:773:0110/084912.188475:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd was not provided by any .service files
[773:773:0110/084912.188508:ERROR:kwallet_dbus.cc(112)] Error contacting kwalletd (isEnabled)
[773:773:0110/084912.188713:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files
[773:773:0110/084912.188732:ERROR:kwallet_dbus.cc(81)] Error contacting klauncher to start kwalletd
[773:773:0110/084912.188967:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd was not provided by any .service files
[773:773:0110/084912.188981:ERROR:kwallet_dbus.cc(503)] Error contacting kwalletd (close)
[773:773:0110/084912.189759:ERROR:policy_logger.cc(157)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(163) Cloud management controller initialization aborted as CBCM is not enabled.
mesa: for the --simplifycfg-sink-common option: may only occur zero or one times!
mesa: for the --global-isel-abort option: may only occur zero or one times!
mesa: for the --amdgpu-atomic-optimizations option: may only occur zero or one times!
[773:954:0110/084912.463197:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[773:954:0110/084912.463717:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[773:954:0110/084912.463988:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
Fontconfig error: Cannot load default config file: No such file: (null)
^[[4~

After the manual update: See screenshot

mikewalsh wrote: ↑Tue Jan 09, 2024 3:22 pm

@Governor :-

Coupla points here.

With the 'portable' versions of all these Chromium-based browsers, we've disabled the internal update mechanism. Quite simply, if you let that run, it then goes and writes the updated version into the main filesystem as normal, and that's NOT what we want. We want to keep the portable browser self-contained within its own directory, so fredx181 has written update scripts for most of them.

You run this from a terminal in the portable directory itself. In other words, you go into the portable directory, hit the key above 'Tab' - the 'back-tick' key - and this will open a terminal. Then, in this case, you type

Code: Select all

./UpdateBrave

.....hit 'Enter', and just leave it to run through the update process. It'll tell you when it's done.

=======================

However; this should NOT prevent it from firing-up, even when out-of-date. If you start it from a terminal - again, open a terminal beside the 'LAUNCH' script, and run

Code: Select all

./LAUNCH

.....what output are you getting.?

(None of the 'zilla-based browsers have this problem.......probably because Firefox et al were always written to be able to run as a self-contained application, dating all the way back to when NetScape Navigator 'morphed' into the very first Firefox. Thus, the internal updater was written to keep that update 'internal'.)

Mike.

Change in settings: On startup select > open the new tab page and new tab page shows blank. Restart browser. Your home page is not a valid url currently although you should be able to browse with a valid url or are you saying that your browser is not working at all even when you type in a valid url to browse the internet (obviously make sure you are connected to the internet)?

@Governor :-

Mm. There's something not quite right with your set-up. I get the same as Fred; it launches with the older Brave home-page (from several releases back).....and the update warning showing. At this point, I shut it down; run the updater script; get it up-to-date, and launch Brave again. And NOW, the new-style homepage should be showing.....

I wanted to get away from the constant grind of re-building and re-uploading, just so that users always downloaded the very newest version all the time. By the simple addition of a script - very kindly provided by Fred - the user could take care of their own updating (and keep it up-to-date).

We need to figure out why it's working for everybody else, but not for you....and just ATM, I'm out of ideas. Have you tried what @amethyst suggested? 'Cos it looks like you're not connected to the internet in that screenshot; something's not kosher with your DNS settings.

Networking, however, is not my strong point.....

Mike.

@Governor As @amethyst said too, what you have in the address bar is not a valid internet address, any idea how it got there ?
Anyway, try to remove what's now in the address bar and type some valid url, e.g. https://duckduckgo.com/ or https://google.com/
edit: what you can do also to start "fresh" is deleting the "PROFILE" directory , then the 'Welcome' page should show at start.

Just another note on Brave browser. You need to use the very latest version. A week ago I started to get all sorts of errors (Oh, snap...crashes) when trying to search with google (only google, other search engines were fine) as search engine. This also happened when I deleted all my cookies and cache data so something definitely changed otherwise. I then downloaded the latest portable and everything seems fine again.

fredx181 wrote: ↑Wed Jan 10, 2024 12:08 pm

@Governor As @amethyst said too, what you have in the address bar is not a valid internet address, any idea how it got there ?
Anyway, try to remove what's now in the address bar and type some valid url, e.g. https://duckduckgo.com/ or https://google.com/
edit: what you can do also to start "fresh" is deleting the "PROFILE" directory , then the 'Welcome' page should show at start.

Brave worked for about two minutes, and froze up. The mouse pointer got weird and has no connection with the browser.
See: Brave browser frozen.png