IRON 32 bit browser is BACK!
-
OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
-
Puppus Dogfellow
- Posts: 1667
- Joined: Tue 08 Jan 2013, 01:39
- Location: nyc
-
Pelo
Version 23.0.1300.0 (165188)
Surprise Puppy-es night 5.5 has Iron as default browser. What an idea ! Browser is a tool that will drive me to my prefered web sites, including Facebook and You Tube. If Iron does it, why not ?
Version 23.0.1300.0 (165188). Ouah colleagues have newer...
Facebook is OK. Iron has been bookmarked with Puppy-es developers forums. Bravo Nilson, Bravo josep2424, that is the way to enter in contact with the pupjibaros
Version 23.0.1300.0 (165188). Ouah colleagues have newer...
Facebook is OK. Iron has been bookmarked with Puppy-es developers forums. Bravo Nilson, Bravo josep2424, that is the way to enter in contact with the pupjibaros
- Attachments
-
- onglets.jpg
- Puppy-es 55, Iron Browser selected as default.. hum...
- (23.92 KiB) Downloaded 1341 times
Last edited by Pelo on Sat 27 Aug 2016, 15:43, edited 1 time in total.
-
OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Version updated to 52.0.2750.0
Released August 21st 2016
This version now autodetects Pepper Flash but the path is hard-coded so the plugin lib must be placed in /usr/lib/adobe-flashplugin for this to work. The wrapper script then does not need to specify the path.
EDIT:- November 2016, Pepper Flash updated to 23.0.0.207
Note that chrome://plugins reports an older version (incorrectly)
Use http://adobe.com/software/flash/about to see the true installed version.
Plays Twitter and Periscope videos and others (which some browsers do not).
Experimental 32bit packages tested briefly in Precise, Slacko 5.7 (needs libgconf2 as always) and also Wheezy.
https://yadi.sk/d/_S5b4g7tpcyZn
Released August 21st 2016
This version now autodetects Pepper Flash but the path is hard-coded so the plugin lib must be placed in /usr/lib/adobe-flashplugin for this to work. The wrapper script then does not need to specify the path.
EDIT:- November 2016, Pepper Flash updated to 23.0.0.207
Note that chrome://plugins reports an older version (incorrectly)
Use http://adobe.com/software/flash/about to see the true installed version.
Plays Twitter and Periscope videos and others (which some browsers do not).
Experimental 32bit packages tested briefly in Precise, Slacko 5.7 (needs libgconf2 as always) and also Wheezy.
https://yadi.sk/d/_S5b4g7tpcyZn
Oscar in England
-
OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Version 54.0.2850.0
Seems OK with sandboxing disabled in those slightly older Puppies.
Pepper Flash 23.0.0.207 added.
Not sure about Netflix. The widevine libs are in there but?
NOTE:- the location /usr/lib/adobe-flashplugin already exists in the Puppy system as a symlink to /usr/lib/mozilla/plugins so I have to put the Pepper Flash libpepflashplayer.so at /usr/lib/mozilla/plugins in the package. That way both .pet and .sfs install and work as expected.
https://yadi.sk/d/_S5b4g7tpcyZn
Seems OK with sandboxing disabled in those slightly older Puppies.
Pepper Flash 23.0.0.207 added.
Not sure about Netflix. The widevine libs are in there but?
NOTE:- the location /usr/lib/adobe-flashplugin already exists in the Puppy system as a symlink to /usr/lib/mozilla/plugins so I have to put the Pepper Flash libpepflashplayer.so at /usr/lib/mozilla/plugins in the package. That way both .pet and .sfs install and work as expected.
https://yadi.sk/d/_S5b4g7tpcyZn
Oscar in England
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi, Oscar.
Many thanks for this. 54.0.2850.0 is running beautifully in Tahr 6.05, Slacko 5.7.0, X-Slacko 2.3.2 and Precise 5.7.1.
I'm running a single instance of this, mounted on a remote partition, and making liberal use of Pup's powerful sym-link function into all four Pups using davids45's method. For anybody who's interested, the thread is here:-
http://www.murga-linux.com/puppy/viewtopic.php?t=99388
Despite the somewhat disparaging posts further into the thread, I find it works a treat.....and is allowing me to use a really modern Chromium clone on the 32-bit Pups. And it does seem a bit daft setting up multiple copies of the same app/browser/whatever across multiple Pups. I still like SlimJet (don't get me wrong).....but I've kinda got used to Chrome/Chromium's new, angular tabs.
Appreciated. Cheers!
BTW: I've given NetFlix a tryout, but....no soap, I'm afraid. It errors out with a network connection fault.....which is not one I've seen before.
Mike.
Many thanks for this. 54.0.2850.0 is running beautifully in Tahr 6.05, Slacko 5.7.0, X-Slacko 2.3.2 and Precise 5.7.1.
I'm running a single instance of this, mounted on a remote partition, and making liberal use of Pup's powerful sym-link function into all four Pups using davids45's method. For anybody who's interested, the thread is here:-
http://www.murga-linux.com/puppy/viewtopic.php?t=99388
Despite the somewhat disparaging posts further into the thread, I find it works a treat.....and is allowing me to use a really modern Chromium clone on the 32-bit Pups. And it does seem a bit daft setting up multiple copies of the same app/browser/whatever across multiple Pups. I still like SlimJet (don't get me wrong).....but I've kinda got used to Chrome/Chromium's new, angular tabs.
Appreciated. Cheers!
BTW: I've given NetFlix a tryout, but....no soap, I'm afraid. It errors out with a network connection fault.....which is not one I've seen before.
Mike.
-
OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Hi Mike,
The strange thing about Netflix support was that the announcement on the Iron forum said that you need to copy the libwidevinecdm.so from Chrome, but the file was included in the Iron package so I was not sure if they had stuck it in there themselves. You could try substituting the one from the latest Chrome and see if that makes any difference if you get chance.
Each of these Chromium derivatives seems to have certain merits even though of course they all have lots of similarities. Iron is a good option for people who want one that looks similar to Chromium or Chrome but want a very recent version for 32bit Puppies with glibc 2.13 or later.
The strange thing about Netflix support was that the announcement on the Iron forum said that you need to copy the libwidevinecdm.so from Chrome, but the file was included in the Iron package so I was not sure if they had stuck it in there themselves. You could try substituting the one from the latest Chrome and see if that makes any difference if you get chance.
Each of these Chromium derivatives seems to have certain merits even though of course they all have lots of similarities. Iron is a good option for people who want one that looks similar to Chromium or Chrome but want a very recent version for 32bit Puppies with glibc 2.13 or later.
Oscar in England
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Mm. Y'see, the major snag with that is that Chrome no longer comes in 32-bit, does it? And I can't see that the 64-bit ELFs from a current Chrome will work, y'know?OscarTalks wrote:Hi Mike,
You could try substituting the one from the latest Chrome and see if that makes any difference if you get chance.
Iron is a good option for people who want one that looks similar to Chromium or Chrome but want a very recent version for 32bit Puppies with glibc 2.13 or later.
The only thing I can think of to try is substituting the libwidevineadapter.so module from one of peebee's recent Chromium builds. He's been getting them from AlienBob, of course.....but Bob's got job and personal concerns that mean he's not got the time to keep stuff up to date at the moment. And peebee's current builds are now coming from the Open Mandriva Project.....and from what I understand, they're only compatible with the very newest Pups now.
Mike.
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi again, Oscar.
We have..... (wait for it, wait for it)..... SUCCESS.
I did some digging around in AlienBob's repo. The very last 32-bit WideVine module he produced was the one for the final 32-bit release of Chrome (48.0.2564.116).....which is the one I run myself.
However, rather than poach it from my Chrome build, I've used his.....and it does indeed work for Iron.
So, for anyone who would like to be able to watch NetFlix in a very modern Chromium clone on 32-bit Pups, here's how:-
1) Download the chromium-libwidevinecdm.so module from here:-
http://www.slackware.com/~alien/slackbu ... /pkg/14.1/
Third entry up from the bottom.
2) Extract the libwidevine.cdm.so module to a known location.
3) Open /usr/lib/iron, and move the existing libwidevinecdm.so module to a safe location (just in case), then copy the new version you've just extracted over in its place.
4) Go into your NetFlix a/c, and.....enjoy!
This should work for most of the more recent Pups. As stated earlier in this thread, I run a single instance of this from a remote data partition, sym-linked into multiple 32-bit Pups, and it works fine.
Incidentally, the libwidevinecdm.so as supplied with Iron is around 140 kb in size. The WideVine module from AlienBob is nearly 7 MB in size; quite a difference, no?
It turns this into a totally usable, everyday Chrome/Chromium replacement. I didn't think I'd hear myself saying this, but it may well take over (for me) as my go-to- Chrome replacement. Iron has improved by leaps & bounds recently; I remember the extremely old version of it I tried in SliTaz some while ago (11? 12? ...something like that), and that was impossible to sync with your Google account.....and it didn't support my few 'must-have' extensions. This is now very, very good.
My only grumble is the way it insists on having Pepper in the 'adobe-flash' directory; makes it impossible to sym-link it to my 'common' PepperFlash directory on the remote data partition. And you can't change the 'switches' or parameters for this since, as Oscar points out, it's 'hard-coded' into the binary itself... Grrr!!
(I have my entire system set-up so that one single update of Pepper updates it for every Chrome/Chromium-based browser that I run.....though that's not as many now as it used to be, with sym-linking 'common' browser installs throughout the Pups.)
Anyway, hope that's of some use..!
Mike.
We have..... (wait for it, wait for it)..... SUCCESS.
I did some digging around in AlienBob's repo. The very last 32-bit WideVine module he produced was the one for the final 32-bit release of Chrome (48.0.2564.116).....which is the one I run myself.
However, rather than poach it from my Chrome build, I've used his.....and it does indeed work for Iron.
So, for anyone who would like to be able to watch NetFlix in a very modern Chromium clone on 32-bit Pups, here's how:-
1) Download the chromium-libwidevinecdm.so module from here:-
http://www.slackware.com/~alien/slackbu ... /pkg/14.1/
Third entry up from the bottom.
2) Extract the libwidevine.cdm.so module to a known location.
3) Open /usr/lib/iron, and move the existing libwidevinecdm.so module to a safe location (just in case), then copy the new version you've just extracted over in its place.
4) Go into your NetFlix a/c, and.....enjoy!
This should work for most of the more recent Pups. As stated earlier in this thread, I run a single instance of this from a remote data partition, sym-linked into multiple 32-bit Pups, and it works fine.
Incidentally, the libwidevinecdm.so as supplied with Iron is around 140 kb in size. The WideVine module from AlienBob is nearly 7 MB in size; quite a difference, no?
It turns this into a totally usable, everyday Chrome/Chromium replacement. I didn't think I'd hear myself saying this, but it may well take over (for me) as my go-to- Chrome replacement. Iron has improved by leaps & bounds recently; I remember the extremely old version of it I tried in SliTaz some while ago (11? 12? ...something like that), and that was impossible to sync with your Google account.....and it didn't support my few 'must-have' extensions. This is now very, very good.
My only grumble is the way it insists on having Pepper in the 'adobe-flash' directory; makes it impossible to sym-link it to my 'common' PepperFlash directory on the remote data partition. And you can't change the 'switches' or parameters for this since, as Oscar points out, it's 'hard-coded' into the binary itself... Grrr!!
(I have my entire system set-up so that one single update of Pepper updates it for every Chrome/Chromium-based browser that I run.....though that's not as many now as it used to be, with sym-linking 'common' browser installs throughout the Pups.)
Anyway, hope that's of some use..!
Mike.
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi again, Slavvo.
Well I can answer that last question myself. Strangely, it still wants /usr/lib.....not /usr/lib64, as you might expect...
------------------------------------------------------------------------------------------------
RE:- Your 'sandboxing' issues. You'll probably find, like I have, that all recent Chrome (and indeed Chromium-based 'clones') on the 64-bit architecture now want to run with 'full' sandboxing.....even with the necessary Puppy 'tweaks'. I don't mind this in the slightest, 'cos it's got to be more secure like that..!
If you're using the .deb file, you'll need to change permissions on the 'chrome-wrapper' script itself. Instead of being
.....which is what I normally use, it is in fact showing
No execute permissions at all. I tumbled to that one when after initially failing to start from the Menu entry, I tried the wrapper-script direct from the terminal, and got 'Permission denied!'
I've moved the Iron directory to /opt (as per my usual practice), changed the .desktop entry to suit, and used a modified version of my 64-bit SlimJet wrapper-script. I've enclosed it below if you want to take a look.
On the Net flix front, I've replaced the libwidevinecdm.so module with that from the current Chrome; SRWare's supplied one was still giving network errors.....but it's so small, compared to Chrome's, there's got to be a ton of stuff missing, to my way of thinking. Put simply, it now works.
Mike.
Well I can answer that last question myself. Strangely, it still wants /usr/lib.....not /usr/lib64, as you might expect...
------------------------------------------------------------------------------------------------
RE:- Your 'sandboxing' issues. You'll probably find, like I have, that all recent Chrome (and indeed Chromium-based 'clones') on the 64-bit architecture now want to run with 'full' sandboxing.....even with the necessary Puppy 'tweaks'. I don't mind this in the slightest, 'cos it's got to be more secure like that..!
If you're using the .deb file, you'll need to change permissions on the 'chrome-wrapper' script itself. Instead of being
Code: Select all
r w x
r - x
r - xCode: Select all
r w -
r w -
r - -I've moved the Iron directory to /opt (as per my usual practice), changed the .desktop entry to suit, and used a modified version of my 64-bit SlimJet wrapper-script. I've enclosed it below if you want to take a look.
On the Net flix front, I've replaced the libwidevinecdm.so module with that from the current Chrome; SRWare's supplied one was still giving network errors.....but it's so small, compared to Chrome's, there's got to be a ton of stuff missing, to my way of thinking. Put simply, it now works.
Mike.
- Attachments
-
- Iron wrapper script.tar.gz
- Modified Iron 'chrome-wrapper' launcher script. This is working for me...
- (782 Bytes) Downloaded 363 times
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
-
OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Hi Mike,
That situation with the adobe-flashplugin directory had me puzzled for a while. I eventually figured out that because it exists as a symlink in the Puppy .iso this means that if you use a .pet package it will work but if you load Iron as a .sfs it won't. I think this is because .sfs packages are loaded underneath the main .iso in the layered filesystem. The libpepflashplayer.so in your package becomes hidden because the original symlink sits on top of it and obscures it.
Stick libpepflashplayer.so in /usr/lib/mozilla/plugins in your package and also include a relative symlink from /usr/lib/adobe-flashplugin to /usr/lib/mozilla/plugins in the package just to have everything structured correctly (even though it already exists in Puppy). I think these paths are all /usr/lib/* and NOT /usr/lib64 even in the 64bit Puppies.
That situation with the adobe-flashplugin directory had me puzzled for a while. I eventually figured out that because it exists as a symlink in the Puppy .iso this means that if you use a .pet package it will work but if you load Iron as a .sfs it won't. I think this is because .sfs packages are loaded underneath the main .iso in the layered filesystem. The libpepflashplayer.so in your package becomes hidden because the original symlink sits on top of it and obscures it.
Stick libpepflashplayer.so in /usr/lib/mozilla/plugins in your package and also include a relative symlink from /usr/lib/adobe-flashplugin to /usr/lib/mozilla/plugins in the package just to have everything structured correctly (even though it already exists in Puppy). I think these paths are all /usr/lib/* and NOT /usr/lib64 even in the 64bit Puppies.
Oscar in England
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi, Oscar!
You've just saved me the trouble of PM-ing you; I was about to say I'd figured this one out myself, and was going to let you know...
Yep; that's the crux of the problem. /usr/lib/mozilla/plugins is an inode.....a 'concrete' location. In Puppy, adobe-flashplugin is a sym-link; and you can't install to a sym-link, can you? Or, if you can (with a .pet package), I'm hanged if I can see how...
I've made my SFS up to have libpepflashplayer.so installed to /usr/lib/mozilla/plugins, and left it at that. Because of the sym-link, it appears in adobe-flashplugin, Iron finds it, and everybody's happy. And, er, yes; you're right. Even in x86-64, it still uses lib, not lib64. Which confuses the issue, to say the least.....
Mike.
You've just saved me the trouble of PM-ing you; I was about to say I'd figured this one out myself, and was going to let you know...
Yep; that's the crux of the problem. /usr/lib/mozilla/plugins is an inode.....a 'concrete' location. In Puppy, adobe-flashplugin is a sym-link; and you can't install to a sym-link, can you? Or, if you can (with a .pet package), I'm hanged if I can see how...
I've made my SFS up to have libpepflashplayer.so installed to /usr/lib/mozilla/plugins, and left it at that. Because of the sym-link, it appears in adobe-flashplugin, Iron finds it, and everybody's happy. And, er, yes; you're right. Even in x86-64, it still uses lib, not lib64. Which confuses the issue, to say the least.....
Mike.
Hey Mike:
First, thanks. I'll try. That tar you attached is a dud, however. Errors unpacking. Either way, I get the idea.
Update: I was able to download the tar above by changing the name before saving the download. Had some %20's in there that didn't take well. Still not working. Mike, what am I doing wrong?
I moved Iron into Opt directory, as well. I moved your script in and also changed the chrome-wrapper to rw rw r Still, nada.
Slavvo67
First, thanks. I'll try. That tar you attached is a dud, however. Errors unpacking. Either way, I get the idea.
Update: I was able to download the tar above by changing the name before saving the download. Had some %20's in there that didn't take well. Still not working. Mike, what am I doing wrong?
I moved Iron into Opt directory, as well. I moved your script in and also changed the chrome-wrapper to rw rw r Still, nada.
Slavvo67
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi, Slavvo.
Sorry about that; I forgot to append the .txt to it!
Give this one a try.....
BTW, that rw,rw,r is what the .deb file did with the 'chrome-wrapper'. You want it to be
If you echo my experience, trying to start that from the terminal (/opt/iron/chrome-wrapper) will get you 'Permission denied...' And the only reason I use /opt is 'cause it's a nice 'catch-all' directory.....and since Chrome installs there by default, and these are all Chrome/Chromium 'clones'.....
(*shrug*)
Mike.
Sorry about that; I forgot to append the .txt to it!
Give this one a try.....
BTW, that rw,rw,r is what the .deb file did with the 'chrome-wrapper'. You want it to be
Code: Select all
rwx
r-x
r-x(*shrug*)
Mike.
- Attachments
-
- iron-wrapper-script.zip
- Iron wrapper script...
- (846 Bytes) Downloaded 278 times
-
sheldonisaac
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Thank you, OscarTalks!OscarTalks (in part) wrote:Version 54.0.2850.0
https://yadi.sk/d/_S5b4g7tpcyZn
I downloaded the iron-54.0.2850.0-i386.sfs
and put it in /mnt/sda1/slim/
Booted Slim Slacko 6 with pfix=ram
Did sfs_load
/usr/lib/iron/iron-wrapper starts IRON
Can someone please help on this: I can't move/resize the window; minimize and maximize work OK.
I am an ordinary user, not an expert.
Many thanks,
Sheldon
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi, sheldon.
I've just run up the SFS packages for the 64-bit variant of version 55, which was released this morning.
The problem is the same there, too. As you say, you can minimize/maximize just fine.....but in the 'minimized' state, you can't resize the windows there, either. Interesting; I hadn't tried it with Iron before now.
I know you can do it with Chrome and SlimJet, 'cos I've done it with those a few times on odd occasions. It must be another of those things that have been 'hard-coded' in by SRWare.
Sorry I can't help with that one!
Mike.
I've just run up the SFS packages for the 64-bit variant of version 55, which was released this morning.
The problem is the same there, too. As you say, you can minimize/maximize just fine.....but in the 'minimized' state, you can't resize the windows there, either. Interesting; I hadn't tried it with Iron before now.
I know you can do it with Chrome and SlimJet, 'cos I've done it with those a few times on odd occasions. It must be another of those things that have been 'hard-coded' in by SRWare.
Sorry I can't help with that one!
Mike.