run google-chrome as root, how?

[gychang]

I am running F96-CE_3.iso frugal install to SSD, running google_chrome-portable from Mikes mega site, extracted running in /opt. I can run as spot by /opt/Google_Chrome-portable/LAUNCH or chrome --user-data-dir --test-type --no-sandbox from terminal, but both seems to be running as spot (only download to ./spot). I read the older "How to run chrome as root" here: viewtopic.php?t=1216&sid=1826c35f779c4d ... beda8f9eb9 but no go...
How do I run this as root so I can download to my /root/Downloads directory?

[thinkpadfreak]

Hello.

I publish Chrome sfs made from the official deb file.

Chrome sfs
https://sakurapup.com/forum1/viewtopic.php?f=25&t=3305

To run it as root:
# google-chrome-stable --no-sandbox

You can add --test-type in order to eliminate the warning message, but you won't be able to log in to various google services.

Edit:
Before you load the sfs, be sure to unload (or uninstall) any other version of Chrome package.

[gychang]

Hello.

I publish Chrome sfs made from the official deb file.

Chrome sfs
https://sakurapup.com/forum1/viewtopic.php?f=25&t=3305

To run it as root:
# google-chrome-stable --no-sandbox

You can add --test-type in order to eliminate the warning message, but you won't be able to log in to various google services.

Edit:
Before you load the sfs, be sure to unload (or uninstall) any other version of Chrome package.

is this the correct sfs (google-chrome-111.0.5563.64-x64.sfs) ?

[thinkpadfreak]

is this the correct sfs (google-chrome-111.0.5563.64-x64.sfs) ?

Yes, it is.
Please be sure to unload or uninstall any other Chrome package before you load the sfs. Otherwise they will conflict and damage Puppy.

[gychang]

@thinkpadfreak thanks, I keep getting no-sandbox warning sign even after clicking them off. Is this expected behavior?

[thinkpadfreak]

I keep getting these 2 warnings after clicking them off. Is this expected behavior?

Strange.
They may appear every time Chrome starts. But once I close them, they don't appear until I restart Chrome.

The behavior may be due to a previous install of Chrome. If you delete /root/.config/google-chrome, the settings will go back to the default. But all data (bookmark, history, etc) will be lost.

[gychang]

I keep getting these 2 warnings after clicking them off. Is this expected behavior?

Strange.
They may appear every time Chrome starts. But once I close them, they don't appear until I restart Chrome.

The behavior may be due to a previous install of Chrome. If you delete /root/.config/google-chrome, the settings will go back to the default. But all data (bookmark, history, etc) will be lost.

Just one "no --sandbox ..." keeps showing up everytime chrome starts?, is there a work around?

[thinkpadfreak]

You can add --test-type option to suppress the warning, but you will not be able to log in to google services.
If you need to log in to google with Chrome run as root, you will have to see the warning every time you start Chrome.

[mikewalsh]

@gychang :-

@thinkpadfreak thanks, I keep getting no-sandbox warning sign even after clicking them off. Is this expected behavior?

Aye. It IS "expected behaviour", Greg. It all comes down to our trying to defeat all the built-in sandbox protection, etc. Big Brother has decided, in his wisdom, that since he knows better than poor old Joe Bloggs in the street, dire warnings are in order if you attempt to run the browser in a way that was NOT intended..!

As thinkpadfreak says, we found out a while back that use of the "--test-type" switch stops Google account services from functioning properly. It's the sole side-effect, though.

Me, I've got so used to clicking the banner off every time I fire up, it doesn't even 'register' any more. I do so without thinking; it's become automatic for me....

You get used to it!

Mike.

[gychang]

@gychang :-

@thinkpadfreak thanks, I keep getting no-sandbox warning sign even after clicking them off. Is this expected behavior?

Aye. It IS "expected behaviour", Greg. It all comes down to our trying to defeat all the built-in sandbox protection, etc. Big Brother has decided, in his wisdom, that since he knows better than poor old Joe Bloggs in the street, dire warnings are in order if you attempt to run the browser in a way that was NOT intended..!

As thinkpadfreak says, we found out a while back that use of the "--test-type" switch stops Google account services from functioning properly. It's the sole side-effect, though.

Me, I've got so used to clicking the banner off every time I fire up, it doesn't even 'register' any more. I do so without thinking; it's become automatic for me....

You get used to it!

Mike.

thanks Mike, I can live with it, by the way your Mega portable pkg download is VERY useful.

Greg