(old)Puppy Linux Discussion Forum

Hello Sheldon,

In Settings, tick the option to "use system title bar and borders". This puts the JWM window frame around it and then you can move and resize.


For anyone interested,

I have now packaged and uploaded the 32bit Iron version 55.0.2900.0 as .sfs and .pet
Pepper Flash is version 24.0.0.186
Ignore the browser if it reports 23.0.0.207
Use http://adobe.com/software/flash/about to verify true version.
Note that default setting is now "ask to activate flash".

Small point of interest, the official Iron download link for the 32bit .deb contained 64bit binaries so there is a mistake there. The tarball was OK so I used that for the repackage.
https://yadi.sk/d/_S5b4g7tpcyZn

Hi, Oscar.

Yes; there seems to be more than a wee bit of that kinda thing about various parts of the SRWare operation. Even the forums seem rather amateurish compared to Puppy.

I, too, prefer the tarballs. With the .debs you seem to get all sorts of permission problems. I know it's simple enough to 'chown root:root', but it's just one more step I can do without!

I tend to always run without the system title bar and borders; maximizes 'real estate', as it were. But thanks for reminding me; I'd forgotten about that.


Mike.

OscarTalks wrote: Small point of interest, the official Iron download link for the 32bit .deb contained 64bit binaries so there is a mistake there. The tarball was OK

You are right.

In Puli, I always downloaded the actual .deb file because the spot user runs it well.
I first bumped into problems in version 54 but I could manage it by issuing different commands to start the old versions and v54.

I picked up your v55 package as soon as I found your post, and now I am writing this using v55 in Puli. Spot user, of course. Thank you, Oscar.

Just one question: Did you compile v55 from source? Some of your binaries, e.g., chrome are smaller than their counterpart in the tarball.

(edited one day later)

Anyway, as I prefer sandboxed browsers, I created a pet file from the v55 tarball. Runs fine by spot user. Actually, I am comparing the performances of the v55 flavors (with and without sandboxing, different file sizes)

(edited a couple of days later)

Speed test result using http://peacekeeper.futuremark.com/:
I skipped comparing other browsers, such as Firefox, Slimjet and Opera, due to their inability to play HTML5 videos encoded with the H.264/MPEG-4 AVC codec.

Mike Walsh wrote:... With the .debs you seem to get all sorts of permission problems. I know it's simple enough to 'chown root:root', but it's just one more step I can do without!

Tarball files are owned by ftp user. Moreover, the SUID bit is unset for chrome-sandbox and chrome-wrapper. The appropriate changes are recommended by SRWare (manually if one uses the tarball), and done by the postinst script of the .deb package.

Do you all run Iron as root?


Have fun!

Regards,

gjuhasz

Hi, gjuhasz.

Yep, we do, I'm afraid..! Although I have found with the newest 64-bit versions of Chrome, SlimJet & Iron, that they will quite happily run, as root, fully-sandboxed.

I've been mulling over the possibility of running all of these as 'Spot', instead.....but I'll confess, I'm not too sure how to go about it. Obviously, we normally have to employ the tricks we do (like disabling various of the sandboxes), simply because the Chromium-based browsers don't like running as root. Well, the 32-bit ones don't.....they won't have it.

It kinda makes me wonder why it is that the 64-bit versions will, nowadays.....

Any pointers as to how I'd run these as 'Spot'? What script modifications would I need to employ?


Mike.

Hello gjuhasz,

I didn't compile Iron from source. I noticed that most of the files including the big main executable are not stripped so I ran "strip --strip-unneeded" on them. This removes quite a large amount of stuff which is totally useless but adds a lot of size to an already big package. I really don't know why SRware have not included this step in their builds.

I usually find that files in a .deb are owned by root but in a tarball this is not always the case. Anyway it is always good to check and "chown -R root:root" if necessary is an easy step. There was a libavcodec.so in the .deb which was 32bit and not present in the tarball. Don't know if it does anything but I copied it across anyway.

Since Puppy generally runs as root by default and also because I wanted to support some slightly earlier Puppies I uploaded packages designed to run that way. Running as spot can be done and I know some sandboxing can be activated this way but it can be different depending on the kernel and Puppy version from what I have observed. You (or others) may wish to upload some packages with different configurations.

Now testing Iron 58.0.3050.0 (32bit) with modification suggested by 666philb using bbe to enable run-as-root with sandbox and infobars enabled. Results will vary in different Puppies. Pepper Flash version is the latest, use http://adobe.com/software/flash/about to test.
Download from:-
https://yadi.sk/d/_S5b4g7tpcyZn?force_show=1

For the life of me, I've always downloaded their "update" and managed to keep things plugging along. Now I can't seem to remember what I did before. I always kept the wrapper script but now it's suddenly spitting the (run as a normal user) window.

Did something change in the latest upgrade? No matter what I try fails. I went as far as loading as spot but that doesn't seem to load any personal settings. I reinstalled iron from the 58 pet here. That works just fine.

Is there something edited in the pet that can be edited manually

Distro: LxPupXenial 16.08

I use the script below and make it executable in /root/my-applications/bin Then a do a drag and drop to the desktop. Well, actually, I package a pet like that includes the desktop but it's 64bit. Anyway, the script below works for me just be mindful of the path. I keep it in /opt/iron directory.... Hope this helps...

if su -l -c "PATH=$PATH LANG=$LANG DISPLAY=$DISPLAY /opt/iron/chrome-wrapper" spot ; then
echo ""
else
cd /
cd /opt/iron
chown root chrome-sandbox
chmod 4755 chrome-sandbox
chmod 4755 chrome-wrapper
cd /
su -l -c "PATH=$PATH LANG=$LANG DISPLAY=$DISPLAY /opt/iron/chrome-wrapper" spot
yad --text="Note: Script needed to fix Iron. Should be fine going forward..."
fi

Thanks! that worked like a charm.

My pleasure! Credit where credit's due, the first "if" in the script was received from RCRSN51. The "else" part of the script is what the SRWare provided to allow for proper permissions so the darn thing works.

Just another light note, you can do the following for incognito in the script above:

/opt/iron/chrome-wrapper -incognito

I haven't used chrome much and forgot that it syncs the bookmarks to my account. from trying the different installs in usr/lib usr/share, I manage to fool myself by not being logged in.

Then it loaded with crazy menus. 1$ is trying to log in to 2$ kept showing in the addy bar. Then it was pulling random gtk into the menu. I thought, man I screwed this up real good.

Dear OscarTalks I guess it's you who have compiled this verson of Iron Browser and mantain to it. I just want to thank you very much for the work. I am running the latest puppy slacko (6.3). Firefox, which is the accompanying browser, It updated and it updates itself. It's a very sympathetic browser, but it does not really go up to modern web-based services like facebook and all google applications. It this iron browser does. It is updated and fast and can do it all. So, thank you so much for that.

/Mikkel

Hi all,

Anyone know how to get rid of this annoying "no-sandbox" popup in Iron? I am testing some of the blink engine browsers, which honestly all feel the same, on both 32 and 64 pups and ddogs. With Iron, no matter what I do, I am getting this annoying popup everytime it starts. I've tried slavvo's script above, and a few other tricks, but now I am stumped. Anyone know before I give up completely on Iron and go on testing the others?

belham2 wrote:Anyone know how to get rid of this annoying "no-sandbox" popup in Iron?

Yes. Don't use the --no-sandbox switch at all and then you will get some level of sandboxing working depending on the Puppy version. In order to do this you need to tweak things a bit. In my packages I do this by modifying the main binary with bbe and you will see no such messages. If you insist on running with --no-sandbox you could also try adding --disable-infobars and see if it removes the warning, but no need to do this if you follow the first suggestion.

OscarTalks wrote:

belham2 wrote:Anyone know how to get rid of this annoying "no-sandbox" popup in Iron?

Yes. Don't use the --no-sandbox switch at all and then you will get some level of sandboxing working depending on the Puppy version. In order to do this you need to tweak things a bit. In my packages I do this by modifying the main binary with bbe and you will see no such messages. If you insist on running with --no-sandbox you could also try adding --disable-infobars and see if it removes the warning, but no need to do this if you follow the first suggestion.

Thanks, Oscar, the "--disable-infobars" is what I couldn't remember and works great as a temporary basis until I can try phil's bbe solution. Weirdly, the trouble I having with Iron and this popup is not in Puppys, but instead in all the Debian Dogs Jessie and Stretch versions. In a couple of Puppies, I've gotten it to run in/as "spot" (as I've done Chrome before) by setting everything up inside the "Spot" directory and making a few mods to scripts and the wrapper while symlinking back to needed pup directories.

Thanks again.

The Iron 58 sfs provided here works great, it's the best of the chromium-based browsers for my HP laptop. Thank you!

I downloaded iron 60 in tar.gz from the srware website. It gives me the dreaded "don't run as root' warning. I tried every trick in this thread: changing permissions, using the extra script, etc. Nohing works except the no-sandbox tag.

Interestingly (for me, anyway!) running Iron 60 in this way prevents spotify from playing in webplayer form, whereas Iron 58 sfs can play spotify without trouble.

So Iron 58 sfs it is for now...

Not sure about anyone else, but the last Iron update required libnss3 be upgraded on my system. (Xenial 16.04) Otherwise it puked on the command line .

Version 61.0.3200.0 (Developer Build) custom (32-bit)

Hi, spiritwild.

No, it's not just you; this was a requirement by Google with the release of Chrome/Chromium 61, across the board. It's 'unearthed' a fresh batch of worms for us here in 'Puppy-land'.....


Mike.

Mike Walsh wrote:Hi, spiritwild.

No, it's not just you; this was a requirement by Google with the release of Chrome/Chromium 61, across the board. It's 'unearthed' a fresh batch of worms for us here in 'Puppy-land'.....


Mike.

I'm just glad iit was a simple fix from the PPM. I was not in the mood for another pulse audio type fix like firefox. Now I'm just waiting for my 32 bit to be unsupported.

SRWare Iron is a Browser, Google's Web browser Chrome thrilled with an extremely fast site rendering, a sleek design and innovative features. But it also gets critic from data protection specialists, for reasons such as creating a unique user ID or the submission of entries to Google to generate suggestions. SRWare Iron is a real alternative. The browser is based on the Chromium-source and offers the same features as Chrome - but without the critical points that the privacy concern.

Comparism of Iron and Chrome at privacy:

Chrome
A copy of Google Chrome includes a generated installation number which will be sent to Google after the installation and the first usage. It gets deleted when Chrome checks first time for updates.If Chrome is received as part of a promotional campaign, it may generate a unique promotion number which is sent to Google on the first run and first use of Google Chrome.

Iron
does not exist in Iron.

Chrome
Depending on the configuration, each time you put something in the address line,this information is sent to Google to provide suggestions.

Iron
does not exist in Iron.

Chrome
Depending on the configuration, if you have typed a false address in the adress bar, this is sent to Google and you get an error message from Google's servers.

Iron
does not exist in Iron.

Chrome
Depending on the configuration, details about crashes or failures are sent Google's servers.

Iron
does not exist in Iron.

This might clear things out!
Please visit my new blog https://ponbee.com constructive criticism is open or any comments will be appreciated. Thank you very much