Puppy Linux Discussion Forum

Odd, Brave is running perfectly for me. I'm running absolutely OOTB (without --no sandbox) in a non-savefile install of FP64_CE_radky6. My uncompressed Brave directory is located in my EXT2 data partition. My only terminal output is:

# ./LAUNCH
[7131:7266:0109/101352.894220:ERROR:object_proxy.cc(623)] 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
[7131:7266:0109/101352.894444:ERROR:object_proxy.cc(623)] 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
[7131:7266:0109/101352.894656:ERROR:object_proxy.cc(623)] 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
# 

The radky 6 install is minimal, without the stock ydrv Nee adrv or bdrv, and with my personal 7.9 MB ydrv with 5 small programs and my configure, panel, and theme setup in it. Nothing else. Maybe maybe..... I am running the 6.1.1 kernel with that install though why that would make a difference eludes me.

# uname -a
Linux puppypc21416 6.1.1-lxpup64 #1 SMP PREEMPT_DYNAMIC Thu Dec 22 07:44:49 GMT 2022 x86_64 x86_64 x86_64 GNU/Linux
#

I didn't check the terminal output in the current S15Pup64 or VoidPup64, also with 6.1.1 kernels, but it opened and ran cleanly there as well. I actually have a bit of use-time on it in all three and it's all good here.

Edit: to clarify that it's running OK OOTB for me in all 3 of my current pups, all with 6.1.1 kernel.

@Marv :-

You may not be alone. I've been running Fossapup's original k5.4.53 kernel in my daily driver, jrb's 'lite' spin on BK's old Quirky 64 April 7.0.1. It's been absolutely rock-solid & stable for a long while.

Along with an upgrade from glibc-2.20 to glibc-2.27, for a couple of weeks I was trying out peebee's k6.1.0 kernel.....but it was giving me all sorts of issues, including a lot of auto-start stuff simply not behaving itself or even starting-up at all, so I've reverted back to k5.4.53. Rock-steady again. I suspect Torvalds' team haven't got all the bugs out of the 6-series yet.

It's either that, or it's summat to do with having both aufs AND overlaysfs compiled in. Whatever the reason, it was giving me too much hassle, so it's gone. I've kept the glibc upgrade in place, but that kernel is history.....at least, for ME.

Mike.

@mikewalsh,
Agreed on kernels, I always have one pup as fallback when I'm flogging meself with the latest and greatest The things that seem to fluctuate most for me is how the newer kernels handle suspend and wakeup and timing things involving sync and unmounting. I cut my teeth entering code with toggle switches so I kind of like watching code and silicon interact, even when I pull some of my few remaining hairs.

In this case, the puzzle is why I'm getting away running Brave Portable without --no sandbox and some others seemingly aren't. I'll throw Brave at my fallback pup later...

Cheers,

Update: Took a bit of extra library fiddling beyond the usual slackware libs, mostly a libpng12 addition and a libz fiddle; but the latest Brave opened and ran in LxPupSc64 22.02 +2 with a 6.08 kernel. Much dirtier terminal than in the newer pups, but works. Posting from it now. The only change in the LAUNCH script was to make line 15 test for LxPupSc64 instead of Quirky April64.

@MochiMoppel :-

Hm. This is curious.

I've tried both 'current' builds of Fossapup64 9.6; the 'standard', "Woofed" one, AND Radky's modified version. You're absolutely right about the 'standard' one; Brave WON'T fire-up, and I cannot figure out why. This portable is set-up to run-as-spot, which is why I was all the more confused when you said you needed to add the "--no-sandbox" option; that's usually needed when running as root. Certainly not when running as user spot.

In the modified Radky build, however, it fires-up and behaves itself, as good as gold.

Very odd.

Mike.

@mikewalsh
Very odd indeed. But it's getting even odder.

I'm currently in FP64_9.6 and I'm happily posting now from a newly discovered 64bit Opera 12.16 . One reason why I still hang on to Slacko5.6 is the phantastic Opera Presto browser- not for everyone and definitely not for every site. I didn't know that they made a 64bit shortly before they dumped their business, their company and all my posts in the Opera forum But surprisingly they kept their archive online (https://ftp.opera.com/pub/opera/linux/1216/). A mere 14MB download and I can use my 32bit profile again. Good stuff...but I disgress.

I had saved your Brave 'portable' to my NTFS HDD, not convinced that I would ever use it again. Yes, it works perfectly on a Radky version, but this version uses a 6.0.12 kernel, probably the cause for its frequent failure to wake up from suspend.

So to check for the Brave problems with FP64_9.6 I expanded the package directly on the HDD and ran LAUNCH from there ....and it works
Lots of initial error messages...

[9122:9122:0111/220612.818854:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
[9122:9122:0111/220612.945310:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: GLX is not present.
[9122:9122:0111/220612.945528:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[9122:9122:0111/220612.976807:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
[9122:9122:0111/220612.977336:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: GLX is not present.
[9122:9122:0111/220612.977929:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[9122:9122:0111/220612.978125:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[9122:9122:0111/220613.210500:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[9169:9169:0111/220617.955420:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
[9169:9169:0111/220617.955931:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: GLX is not present.
[9169:9169:0111/220617.956077:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[9169:9169:0111/220617.956480:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
[9169:9169:0111/220617.956682:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: GLX is not present.
[9169:9169:0111/220617.956814:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[9169:9169:0111/220617.956995:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[9169:9169:0111/220617.964794:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[9079:9192:0111/220618.255692:ERROR:object_proxy.cc(623)] 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
[9079:9192:0111/220618.256748:ERROR:object_proxy.cc(623)] 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
[9079:9192:0111/220618.257287:ERROR:object_proxy.cc(623)] 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
[9193:9193:0111/220619.065139:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
[9193:9193:0111/220619.065630:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: GLX is not present.
[9193:9193:0111/220619.065801:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[9193:9193:0111/220619.066252:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
[9193:9193:0111/220619.066450:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: GLX is not present.
[9193:9193:0111/220619.066620:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[9193:9193:0111/220619.066778:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[9193:9193:0111/220619.073999:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[9216:9216:0111/220622.139243:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[9079:9079:0111/220811.333188:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220811.524847:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220815.861088:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220815.980930:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220816.356953:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220816.404882:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220816.476943:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220816.556804:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220816.701031:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220816.812815:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220817.388946:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9079:0111/220817.475340:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[9079:9108:0111/220904.456029:ERROR:print_backend_cups.cc(217)] CUPS: Error getting default printer: Bad file descriptor
[9079:9079:0111/220904.459167:ERROR:device_event_log_impl.cc(215)] [22:09:04.456] Printer: local_printer_handler_default.cc:224 Failure getting default printer name, result: kFailed
Warning: disabling flag --expose_wasm due to conflicting flags

, but the browser runs, and it runs as spot (access to /root denied), no need for the "--no-sandbox" option. You can figure that out

@MochiMoppel :-

Error messages, unfortunately, are endemic to the main product of the Chromium Project. You can have a Chromium-based browser, running in an ideal environment for the version used as 'base' PLUS whatever 'alterations' have been made by whatever project/organisation is releasing the 'clone' in question, and the terminal will STILL be full of complaints..!

This can be traced all the way back to the initial decision, in Autumn 2007, by the team that were handling all the reports from us 'beta testers' (I was part of the original beta-testing program for Chrome), that an on-going, live, second by second debug report, running concurrently with the browser itself, would be an excellent trouble-shooting idea for the devs....

They've retained it to this day. And it constantly bothers those who don't know any of the history behind the browser's development, given that the assumption made by many is that if something is running correctly, why SHOULD there be messages in the terminal..?

My response is always the same whenever this comes up. Blame Google, if you feel you must blame someone..! I've been so used to all this for the last 15 years or so, it doesn't even "register" any longer, but just goes straight over the top of my head these days.....

(*shrug*)

(Thanks for the info about that 64-bit Opera 12.16. I might have a play around with it again; I always had a job getting my head around the way that it functioned, 'cos it wasn't quite LIKE any other browser I'd come across.)

Mike.

@mikewalsh
1) I wasn't complaining about the error messages. I don't care as long as they don't affect the functionality of the program, which in this case they don't.

2) What happened in my (and probably your) failed attempt to run Brave is now clear to me. In a nutshell: the script run-as-spot, in line 75, tried to run the command "/root/Downloads/Brave-portable64/brave/brave" as spot, and this naturally fails as it should. This means that your 'portable' stuff can be copied to anywhere inside or outside of the main filesystem, but not to /root or any of its subdirectories. This you should make clear in your installation instructions.

3) Small proposal: In LAUNCH the commands
mkdir "$HERE/PROFILE" 2> /dev/null
mkdir "$HERE/PROFILE/spot" 2> /dev/null
mkdir "$HERE/PROFILE/spot/Brave-Browser" 2> /dev/null
can be replaced by a single command when you use the -p option ("make parent directories as needed"):
mkdir -p "$HERE/PROFILE/spot/Brave-Browser"
I also would not use the "2> /dev/null" redirection here. If the command fails the rest of the script will fail too, so it's essential that any error message is displayed and not swept under the /dev/null rug.

4) As for Opera at least one thing should be familiar to you: It is 'portable' OOTB. Can be launched from anywhere and the profile by default is created in the launch directory.

MochiMoppel wrote:

In a nutshell: the script run-as-spot, in line 75, tried to run the command "/root/Downloads/Brave-portable64/brave/brave" as spot, and this naturally fails as it should. This means that your 'portable' stuff can be copied to anywhere inside or outside of the main filesystem, but not to /root or any of its subdirectories. This you should make clear in your installation instructions.

It does work for me (on FossaPup) when I click 'Launch' from inside /root/Downloads (extracted with Uextract).

Btw, what would be the difference running it from inside /root/ or outside ?

For me this brave works perfectly, but...

... it only works if I unzip this file into the OPT folder.

I installed SLIMJET, FIREFOX, LIBREOFFICE, THE GIMP... outside OPT and there is no problem when I use the LAUNCH file to start the program, but with BRAVE I can't do this, it only works when I put it into the OPT folder (and I want to put it in the installation folder of my vanilladpup, in order to have a small save file and not to use as many space into it).

How can I solve it???

Is install it at the OPT folder the only solution.

Thanks in advance.

@mikewalsh

mikewalsh wrote: ↑Mon Jan 09, 2023 2:00 am

Morning, gang.

Okay. Here's the most recent 'stable' release of Brave-portable for Puppy; v1.46.153 - based around Chromium 108.0.5359.128.

Just as fast and snappy as ever; if anything, it seems a touch faster still. I'm not investigating, and I'm certainly not complaining! And just as reliable...

------------------------------------------------------

You can find the new release at the link in post #1, as always. Usual caveats apply:-

• Download

• Unzip

• Place anywhere you like, though outside the 'save' is best

• Click to enter

• Click 'LAUNCH' to fire it up

Scripts permit the addition/removal of a Menu entry, should one be required.

Enjoy.

Mike.

@pp4mnklinux ,
How is the partition that holds the vanillapup installation directory formatted. I have a perfectly running Brave portable in an EXT2 formatted partition. Copied it to my FAT32 boot partition and set the permissions of the spot directory in PROFILE to spot:spot. Dialog box correctly asked if I wanted the change to be recursive, answered yes. Permissions were not changed within spot. Brave couldn't create a singleton lock and hence wouldn't start. It had never occurred to me to run a portable from a FAT32 so I had never tried this before and won't persue it but might it be a possibility??

Okay, guys. Update time again...

Here's the Puppy-portable version of Brave browser. We're now at v1.48.171, based around Chromium 110.0.5481.177.

Just as stable & easy-to-use as always. Download link can be found in post #1.

Enjoy.

Mike.

mikewalsh wrote: ↑Fri Mar 10, 2023 4:15 pm

Okay, guys. Update time again...

Here's the Puppy-portable version of Brave browser. We're now at v1.48.171, based around Chromium 110.0.5481.177.

Just as stable & easy-to-use as always. Download link can be found in post #1.

Enjoy.

Mike.

Hi @mikewalsh

how do i make a portable version Yandex-browser ,??
https://aur.archlinux.org/packages/yandex-browser

Sofiya wrote: ↑Fri Mar 10, 2023 4:23 pm

mikewalsh wrote: ↑Fri Mar 10, 2023 4:15 pm

Okay, guys. Update time again...

Here's the Puppy-portable version of Brave browser. We're now at v1.48.171, based around Chromium 110.0.5481.177.

Just as stable & easy-to-use as always. Download link can be found in post #1.

Enjoy.

Mike.

Hi @mikewalsh

how do i make a portable version Yandex-browser ,??
https://aur.archlinux.org/packages/yandex-browser

@Sofiya :-

You're one of the very few here who would actually understand Yandex, aren't you? A lot of the built-in menus'n'stuff, and the 'home page', all come up in Cyrillic.

I did maintain a package for a wee while, but I gave up on it because it never got many downloads; I had enough other browsers to keep me occupied, so I let it slide. The one thing you must do with it as soon as you start to use it is to go through the settings with a fine toothcomb.....and disable anything that reports back to the Yandex Cloud. You can't even save bookmarks locally, 'cos it wants to save absolutely everything you do to 'the cloud'. Which in this case means having all your personal data 'picked-over' by the local KGB, no doubt!

It's a 'run-as-root' one, so all that's needed is the "--no-sandbox" switch. IIRC, the closest one to what you need is the Iron-portable. Should be easy enough to modify names, $PATHs & various other items to create a portable-Yandex. But with what's going on in the Ukraine ATM, I don't think you'll find a very up-to-date version anywhere....

If you do decide to attempt it, let us know how you get on, willya?

Mike.

mikewalsh wrote: ↑Fri Mar 10, 2023 4:44 pm

@Sofiya :-

You're one of the very few here who would actually understand Yandex, aren't ?

If you do decide to attempt it, let us know how you get on, willya?

Mike.

Yes this is true .
Okay, I'll let you know.

Thanks Mike, posting from the new one in jammypup64 B3. Came right up OOTB, then I copied my PROFILE in from the previous Brave portable and it graciously accepted that. As usual I keep a separate directory in my data partition for the new one and when it's working, replace the previous one in my portables directory. I'll check it in the slackware derivatives a little later but expect no problems based on how well the previous one ran in them.

Thanks,

Update: It's fine in the newest versions of S15Pup64 and LxPupSc64 as well.

mikewalsh wrote: ↑Fri Mar 10, 2023 4:15 pm

Okay, guys. Update time again...

Here's the Puppy-portable version of Brave browser. We're now at v1.48.171, based around Chromium 110.0.5481.177.

Just as stable & easy-to-use as always. Download link can be found in post #1.

Enjoy.

Mike.

unfortunately, in xenialpup64 7.5 CE, it needs a newer glibc

/root/Brave-portable64/brave/brave: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /root/Brave-portable64/brave/brave)

Hi @mikewalsh:

I just installed this version in my F96CE_XFCE_FUSILLI (F96CE derivative) and it doesn't start.

I think I did it correctly (With Opera, Firefox, Slimjet and Chrome there is no problem).

Anybody is having difficulties too ??

Let me know to continue trying or not.

Thanks a lot in advance, CHEERS.

-------------edited-------------------

If you go to previous version https://mega.nz/folder/yaRhwICQ#qODo0dx4DTpXMn24gocIiw, there is no problem with it, so I imagine the problem is the the last one.

mikewalsh wrote: ↑Fri Mar 10, 2023 4:15 pm

Okay, guys. Update time again...

Here's the Puppy-portable version of Brave browser. We're now at v1.48.171, based around Chromium 110.0.5481.177.

Just as stable & easy-to-use as always. Download link can be found in post #1.

Enjoy.

Mike.

@pp4mnklinux, Have you tried launching it in a terminal window to see what error messages show up? ie. go to the directory it is expanded into, the one containing 'LAUNCH', open a terminal and execute ./LAUNCH. That might help in diagnosing this. I am in jammypup64 using that Brave at the moment but I also run it in F96-CE_4 and I'll bounce to that and see if I can reproduce your non-start. My LAUNCH script is slightly modified, has 2> /dev/null at the end of the run-as-spot lines but that is the only change that might be relevant here.

OK, I'm in F96-CE_4, stock kernel, no savefile, and I get a clean start for Brave 1.48.171 with either the stock LAUNCH or my modified LAUNCH scripts so the change mentioned above isn't it. The only messages from chromium I get in terminal are the usual:

# ./LAUNCH
[10621:10621:0417/085326.482973:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.
[10559:10710:0417/085326.608183:ERROR:object_proxy.cc(622)] 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
[10559:10710:0417/085326.608411:ERROR:object_proxy.cc(622)] 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
[10559:10710:0417/085326.608606:ERROR:object_proxy.cc(622)] 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

My hardware is an all intel 2nd gen i5 based laptop circa 2012.

Thanks a lot for your answer.

When I execute this command, terminal dissapear and nothing happens.

I don't know what happened.... but Brave didn't start.

No problem for me... continue with old version.

Have a nice day, my friend.- CHEERS

Marv wrote: ↑Mon Apr 17, 2023 1:47 pm

@pp4mnklinux, Have you tried launching it in a terminal window to see what error messages show up? ie. go to the directory it is expanded into, the one containing 'LAUNCH', open a terminal and execute ./LAUNCH. That might help in diagnosing this. I am in jammypup64 using that Brave at the moment but I also run it in F96-CE_4 and I'll bounce to that and see if I can reproduce your non-start. My LAUNCH script is slightly modified, has 2> /dev/null at the end of the run-as-spot lines but that is the only change that might be relevant here.

OK, I'm in F96-CE_4, stock kernel, no savefile, and I get a clean start for Brave 1.48.171 with either the stock LAUNCH or my modified LAUNCH scripts so the change mentioned above isn't it. The only messages from chromium I get in terminal are the usual:

Code: Select all

# ./LAUNCH
[10621:10621:0417/085326.482973:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.
[10559:10710:0417/085326.608183:ERROR:object_proxy.cc(622)] 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
[10559:10710:0417/085326.608411:ERROR:object_proxy.cc(622)] 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
[10559:10710:0417/085326.608606:ERROR:object_proxy.cc(622)] 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

My hardware is an all intel 2nd gen i5 based laptop circa 2012.

Thanks

Six further releases are out after 1.48.171. Current is 1.50.119, according with Softpedia.

newpet wrote: ↑Tue Apr 18, 2023 9:58 pm

Six further releases are out after 1.48.171. Current is 1.50.119, according with Softpedia.

Uh-huh.

In case you're not aware, I do NOT religiously & single-mindedly build & publish portable packages for every single release of Brave. For one thing, it's pointless; they frequently publish several builds within a matter of hours. For another, this is only a hobby for me.....in real life - which frequently gets in the way - I have far better things to do with my time.

So the community gets perhaps one update every 2-3 weeks, and has to make do with THAT. Sorry if that doesn't meet with your approval. You're quite welcome to take over building these packages if that would suit you better!

Mike.

newpet wrote: ↑Tue Apr 18, 2023 9:58 pm

Six further releases are out after 1.48.171. Current is 1.50.119, according with Softpedia.

I pulled my original reply as it was a bit snide but the gist of it was that an update from 1.48.171 to 1.50.120 was trivial. Once Brave started nagging me, I downloaded the desired release as a deb from github, extracted it, and replaced the brave directory in the portable with the /opt/brave.com/brave directory from the extracted release. Done. A better post on the new releases would have been: They are available, I did an update to the portable like so, and it works -or I have specific issues, help-

The first question about updates is "is the old version still functional?". Brave may 'bitch & moan', but were you able to use the 'old version'? Some web-sites may be VERY picky. Most aren't. Browsers several years old and many versions behind may still work. But are they secure enough for your purposes? The main reason for updating is security. But how much more security does this week's version provide over last week's?

mikeslr wrote: ↑Wed Apr 19, 2023 4:53 pm

The first question about updates is "is the old version still functional?". Brave may 'bitch & moan', but were you able to use the 'old version'? Some web-sites may be VERY picky. Most aren't. Browsers several years old and many versions behind may still work. But are they secure enough for your purposes? The main reason for updating is security. But how much more security does this week's version provide over last week's?

Our bank is one of those websites that is. Who knows why, quite small local bank but chromium v112 is now required. My brokerages and larger banks are still satisfied with v110 or even v108. Go figure...

@mikewalsh
My post wasn't for you, as you can easily read. Therefore your comment is pointless.
Good for you that you have better things to do. Feel free to cultivate your hobby whenever you like.
I see no reason to be rude, honestly.

My post is rather directed towards whom likes tinkering with Brave (or any other browser) and/or update it, if necessary, and each in his own way.
Nothing serious I hope.

@Marv Yes, me too adopt the same method, .deb are available on github or ubuntu repos, no issues so far.

Cheers

Here's a little script to check latest Brave version and download the amd64 .deb automatically (using curl):
(currently it is "brave-browser_1.50.121_amd64.deb")

#!/bin/bash
LATEST=$(curl -Ls -o /dev/null -w %{url_effective} https://github.com/brave/brave-browser/releases/latest)
VER=$(basename "$LATEST" | sed 's/^v//')
echo "Latest brave-browser version is ${VER}"
curl -k -L "https://github.com/brave/brave-browser/releases/download/v${VER}/brave-browser_${VER}_amd64.deb" -o "brave-browser_${VER}_amd64.deb" 

Here's a more extended script for to upgrade Brave-Portable.
Usage: place the attached UpdateBrave script (remove fake .gz and make executable) in the portable directory next to LAUNCH from @mikewalsh's setup (in Brave-portable64 dir) and run from there in terminal ./UpdateBrave
It should automatically update to newest version if available.
It will download the .zip from Github (currently "brave-browser-1.50.121-linux-amd64.zip") to extract instead of the .deb (which is better IMO, extraction of .deb isn't always supported).

EDIT: The check for latest version installed (or not) depends on the file "Last Version" in PROFILE/spot/Brave-Browser/, running LAUNCH will update it (after latest version installed with the script).

@fredx181 :-

Thanks, Fred! Much appreciated....

I've added the UpdateBrave script to the portable, along wth a 'ReadMe' for how to use it, run the updater to get the newest version, and re-packed & uploaded to MEGA.nz. Works a treat.

Cheers, mi amigo!

Mike.

Dear @mikewalsh , if you still currenly use Xenialpup64 7.5, are you able to remember what build was the latest to work in Xenialpup? Current build don't start asking for a newer glibc