Mate, I doubt any amount of wine would fix the after-effects of a heart attack, and the onset of problems with gallstones....
(*Ouch! Them buggers HURT...)
Everything's decided to gang up on me at once.....Mike.
Slimjet web browser
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
A bit of wine is supposedly good for such things (so I've heard 
).-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
I've been updating 32bit slimjet over time on LxPupSc, LxPupTahr, and LxPupXenial. No issues encountered up to and including slimjet 14.0.10.0 on any of my pups and it's become my goto browser across the board. I've been using both OscarTalks SFS and my own SFS made from a direct slimjet download. With version 14.0.14.0 for the first time I have a bit of a snag. Both 14.0.10.0 and 14.0.14.0 are based on Chromium 57.0.2987.98.
14.0.14.0 runs without problems in LxPupXenial 17.06, based on XenialPup 7.0.8.1, 4.9.13 nopae kernel.
14.0.14.0 will not start in LxPupSc either 17.06.1 or 17.06.21, either with the stock 4.11.x kernel or with the 4.9.13 kernel from LxPupXenial. Calling it in terminal gives the following error message:
Illegal instruction
# [10726
0614/185116.665312:ERROR:broker_posix.cc(41)] Invalid node channel message
OscarTalks slackware 14.0 version of 14.0.14.0 exhibits the same behavior.
Any thoughts on what I could try here?
14.0.14.0 runs without problems in LxPupXenial 17.06, based on XenialPup 7.0.8.1, 4.9.13 nopae kernel.
14.0.14.0 will not start in LxPupSc either 17.06.1 or 17.06.21, either with the stock 4.11.x kernel or with the 4.9.13 kernel from LxPupXenial. Calling it in terminal gives the following error message:
Illegal instruction
# [10726
0614/185116.665312:ERROR:broker_posix.cc(41)] Invalid node channel messageOscarTalks slackware 14.0 version of 14.0.14.0 exhibits the same behavior.
Any thoughts on what I could try here?
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
The later chromiums 59+ apparently require gtk+3
Some discussion below.
http://www.murga-linux.com/puppy/viewto ... 018#957018
Just a shot in the dark, maybe has nothing to do with it.
Some discussion below.
http://www.murga-linux.com/puppy/viewto ... 018#957018
Just a shot in the dark, maybe has nothing to do with it.
-
Sailor Enceladus
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
I get the same error using 14.0.14.0.sfs (slacko14 and i686) in Slacko 6.9.9.9. Works ok in woof-CE Slacko 5.7.1 though.Marv wrote:I've been updating 32bit slimjet over time on LxPupSc, LxPupTahr, and LxPupXenial. No issues encountered up to and including slimjet 14.0.10.0 on any of my pups and it's become my goto browser across the board. I've been using both OscarTalks SFS and my own SFS made from a direct slimjet download. With version 14.0.14.0 for the first time I have a bit of a snag. Both 14.0.10.0 and 14.0.14.0 are based on Chromium 57.0.2987.98.
14.0.14.0 runs without problems in LxPupXenial 17.06, based on XenialPup 7.0.8.1, 4.9.13 nopae kernel.
14.0.14.0 will not start in LxPupSc either 17.06.1 or 17.06.21, either with the stock 4.11.x kernel or with the 4.9.13 kernel from LxPupXenial. Calling it in terminal gives the following error message:
Illegal instruction
# [10726
OscarTalks slackware 14.0 version of 14.0.14.0 exhibits the same behavior.
Any thoughts on what I could try here?
- Attachments
-
- Screenshot.png
- (22.27 KiB) Downloaded 1079 times
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi, Marv.
Hm. That's odd. I have Slimmie 14.0.14.0 working fine in X-Slacko 2.3.2 (this was rg66's original attempt, as you know.) I find it works better with many contemporary packages than the the newer X-series Pups, for some stupid reason.....
I've only tried one of peebee's LXPups, a while ago, and had no end of problems with it. Gave it up as a bad job in the end.
Mike.
Hm. That's odd. I have Slimmie 14.0.14.0 working fine in X-Slacko 2.3.2 (this was rg66's original attempt, as you know.) I find it works better with many contemporary packages than the the newer X-series Pups, for some stupid reason.....
I've only tried one of peebee's LXPups, a while ago, and had no end of problems with it. Gave it up as a bad job in the end.
Mike.
Morning Mike,
Yes, tis odd. I hadn't run X-slacko 4.2 in a bit other than on my NAS box so I fired it up. It had been running slimjet 14.0.1.0. 14.0.10.0 ran fine on it as did the i686 version (OscarTalks) of 14.0.14.0. I see above that Sailor E sees the same problem in Slacko 6.9.9.9 also. Seems to point to a change (in woof ce?) rather than the usual 'browser outrunning libraries' thing.
Yes, tis odd. I hadn't run X-slacko 4.2 in a bit other than on my NAS box so I fired it up. It had been running slimjet 14.0.1.0. 14.0.10.0 ran fine on it as did the i686 version (OscarTalks) of 14.0.14.0. I see above that Sailor E sees the same problem in Slacko 6.9.9.9 also. Seems to point to a change (in woof ce?) rather than the usual 'browser outrunning libraries' thing.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
-
OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Slimjet version now 14.0.15.0
Might be OK in Slacko 6.9.9.9 now. It does start for me which (as reported) the previous version did not.
Slimjet is offered by the website as .deb or tarball. I had mostly been using the .deb for my repacks as .sfs and .pet but someone reported a certificate problem in Precise and when I switched to using the tarball I was told that the problem was resolved.
The tarball version has a /lib sub-directory which is not present in the .deb but which contains some libraries including nss so I wonder if this is the reason or if there is some other explanation. Precise has some old nss libs which are contained within seamonkey.
Anyway, this /lib sub-directory also contains a libudev.so.1 which seems to be causing a conflict (and is not needed) in Slacko 6.9.9.9 because if I remove it then Slimjet starts and runs. I would suggest trying the i686 version first, the other version is intended for Slacko 5.7 or before libgconf2 was added. Treat all packages as being for testing and take the usual precautions if installing.
https://yadi.sk/d/fd8rBM0WoF9sB?force_show=1
Might be OK in Slacko 6.9.9.9 now. It does start for me which (as reported) the previous version did not.
Slimjet is offered by the website as .deb or tarball. I had mostly been using the .deb for my repacks as .sfs and .pet but someone reported a certificate problem in Precise and when I switched to using the tarball I was told that the problem was resolved.
The tarball version has a /lib sub-directory which is not present in the .deb but which contains some libraries including nss so I wonder if this is the reason or if there is some other explanation. Precise has some old nss libs which are contained within seamonkey.
Anyway, this /lib sub-directory also contains a libudev.so.1 which seems to be causing a conflict (and is not needed) in Slacko 6.9.9.9 because if I remove it then Slimjet starts and runs. I would suggest trying the i686 version first, the other version is intended for Slacko 5.7 or before libgconf2 was added. Treat all packages as being for testing and take the usual precautions if installing.
https://yadi.sk/d/fd8rBM0WoF9sB?force_show=1
Oscar in England
Tested in LxPupSc 17.06.22T. The i686 14.0.15.0 SFS starts correctly whereas 14.0.14.0 did not. The i686 14.0.15.0 SFS also tested and runs correctly in LxPupXenial 17.06. I'll check it in X-slacko 4.2 a bit later, posting from 14.0.15.0 in LxPupSc.OscarTalks wrote:Slimjet version now 14.0.15.0
Might be OK in Slacko 6.9.9.9 now. It does start for me which (as reported) the previous version did not.
Thank you!
Update: i686 14.0.15.0 SFS also fine in X-slacko 4.2
Update: i686 14.0.16.0 SFS running well in LxPupSc 16.06.25T, LxPupXenial 17.06 (XenialPup 7.0.8.1 based) and X-slacko 4.2
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi, Oscar.
Just a heads-up for you.
I don't know whether you've yet tried the 32-bit 15.x.x.x series yet. I was finding that even in Tahr 6.0.5, it was refusing to run.....and all older Pups just turned their nose up at it. I forget exactly, but something to do with a 'g (something or other)_symbol_lookup_error'.
I know, when I see that, that invariably it means a problem with the version of the glibc in use. Like, too old.....?
Two days ago, I thought I'd try one of the newer Pups, so I installed XenialPup 7.0.8.1. Runs beautifully, even on ye ancient P4 Dell (with the exception of a touchpad issue I'm working on).....and SlimJet 15.0.1.0 runs fine here. It uses glibc-2.23, as against Tahr's 2.19. peebee's current Chromium even runs fine on here, too, which it hasn't done in Tahr for several releases now. Go figure.
Just wanted to warn you about possible problems ahead, that's all. Or perchance your use of Phil's BBE-sandbox script has negated problems at your end; I don't know. I know Iguleder's libpuppygc.so module is working wonders for all the 64-bit Chromium 'clones' (after peebee re-compiled it).....and I'm using Iggy's original 32-bit version in a modified version of the 15.0.1.0 tarball here in Xenialpup. It's running nicely.
The only curiosity I've noticed in the 15-series is that the Forum is now labelled as 'Not Secure' in the address bar! In fact, all 'http' sites are being treated the same; seems SlimJet appears to expect 'https' sites all the time now.
Posting this from 32-bit SlimJet 15.0.1.0 in Xenialpup right now.
Mike.
Just a heads-up for you.
I don't know whether you've yet tried the 32-bit 15.x.x.x series yet. I was finding that even in Tahr 6.0.5, it was refusing to run.....and all older Pups just turned their nose up at it. I forget exactly, but something to do with a 'g (something or other)_symbol_lookup_error'.
I know, when I see that, that invariably it means a problem with the version of the glibc in use. Like, too old.....?
Two days ago, I thought I'd try one of the newer Pups, so I installed XenialPup 7.0.8.1. Runs beautifully, even on ye ancient P4 Dell (with the exception of a touchpad issue I'm working on).....and SlimJet 15.0.1.0 runs fine here. It uses glibc-2.23, as against Tahr's 2.19. peebee's current Chromium even runs fine on here, too, which it hasn't done in Tahr for several releases now. Go figure.
Just wanted to warn you about possible problems ahead, that's all. Or perchance your use of Phil's BBE-sandbox script has negated problems at your end; I don't know. I know Iguleder's libpuppygc.so module is working wonders for all the 64-bit Chromium 'clones' (after peebee re-compiled it).....and I'm using Iggy's original 32-bit version in a modified version of the 15.0.1.0 tarball here in Xenialpup. It's running nicely.
The only curiosity I've noticed in the 15-series is that the Forum is now labelled as 'Not Secure' in the address bar! In fact, all 'http' sites are being treated the same; seems SlimJet appears to expect 'https' sites all the time now.
Posting this from 32-bit SlimJet 15.0.1.0 in Xenialpup right now.
Mike.
-
OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Hello Mike,
I did take a brief look at Slimjet 15 some days ago and have now done so again.
I have Slimjet 15.0.1.0 running in Tahr 6.0.5 and Slacko 6.3.2 which remain the 2 current official 32bit Puppies.
If you are using the tarball rather than the .deb, try deleting the libudev.so.1 from inside the "lib" sub-directory as this might be what is causing the symbol error. The required glibc version now appears to be 2.15 but you also have to keep an eye on the libstdc++ version.
The bbe method replaces the libpuppygc.so method and I find it to be better with less of the chatter in terminal. It creates a fresh version of the main slimjet binary which has the internal modification for run-as-root. You just substitute it, remembering to give it execute permissions.
This Slimjet won't run in Wheezy or Precise or Slacko 5.7 so I am less enthusiastic about it. For now I have uploaded a .sfs package, but we will see how things go. The 14.0.16.0 packages will remain there for a while for use in those slightly older Puppies.
https://yadi.sk/d/fd8rBM0WoF9sB?force_show=1
I did take a brief look at Slimjet 15 some days ago and have now done so again.
I have Slimjet 15.0.1.0 running in Tahr 6.0.5 and Slacko 6.3.2 which remain the 2 current official 32bit Puppies.
If you are using the tarball rather than the .deb, try deleting the libudev.so.1 from inside the "lib" sub-directory as this might be what is causing the symbol error. The required glibc version now appears to be 2.15 but you also have to keep an eye on the libstdc++ version.
The bbe method replaces the libpuppygc.so method and I find it to be better with less of the chatter in terminal. It creates a fresh version of the main slimjet binary which has the internal modification for run-as-root. You just substitute it, remembering to give it execute permissions.
This Slimjet won't run in Wheezy or Precise or Slacko 5.7 so I am less enthusiastic about it. For now I have uploaded a .sfs package, but we will see how things go. The 14.0.16.0 packages will remain there for a while for use in those slightly older Puppies.
https://yadi.sk/d/fd8rBM0WoF9sB?force_show=1
Oscar in England
-
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,
The bbe file itself is an executable binary and the script just contains the commands to make the substitution. I do the steps manually rather than using the script. I only run bbe on the main executable binary. The name of this may be slimjet or chrome or vivaldi-bin or opera or whatever, depending on the chromium derivative.
So for example, with a terminal open inside the slimjet main directory creates the modified main binary named as slimjet1
Delete the original slimjet main binary
Rename slimjet1 to just slimjet
Make it executable
The only thing I do with the sandbox file is look at properties and make sure the SUID bit is set. Not sure if this is essential or not, but I always do it anyway.
The bbe file itself is an executable binary and the script just contains the commands to make the substitution. I do the steps manually rather than using the script. I only run bbe on the main executable binary. The name of this may be slimjet or chrome or vivaldi-bin or opera or whatever, depending on the chromium derivative.
So for example, with a terminal open inside the slimjet main directory
Code: Select all
bbe -e 's/geteuid/getppid/' slimjet > slimjet1Delete the original slimjet main binary
Rename slimjet1 to just slimjet
Make it executable
The only thing I do with the sandbox file is look at properties and make sure the SUID bit is set. Not sure if this is essential or not, but I always do it anyway.
Oscar in England
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi, Oscar.
Yes, that works nicely. I now have my remote copy of SlimJet (currently 15.0.2.0) running in all Pups in the kennel.
I just did what Phil suggested. I have the script open in one window, and my extracted tarball of 'Slimmie' open in another.. Drag the binary across, 'drop' it on the script. All done.
And the same 'trick' works for Iron, too! (Which is hardly surprising...)
I think you're right about libudev. Initially, I'd tried with this still in place a few days ago, before your last post, and.....it didn't want to know. So I've removed it, after performing the BBE-script trick; runs a treat now. Thanks for the tip.
(And there is a LOT less crud in the terminal.)
Under normal circumstances, I'd use your 32-bit packages anyway.....but with having such a convoluted set-up, running multiple sym-linked apps from a remote partition, it really is simpler (for me) to just extract the downloaded tarball, swap 'em over, then perform the mods 'in situ'. But,again:-
.....thanks for the tip!
(davids45 has got a lot to answer for; but his method for running sym-linked apps remotely is a life saver for me. Running the same set of apps in at least 10 different Pups, it'd just be crazy to install every one of 'em 10 times..!)
Cheers.
Mike.
Yes, that works nicely. I now have my remote copy of SlimJet (currently 15.0.2.0) running in all Pups in the kennel.
I just did what Phil suggested. I have the script open in one window, and my extracted tarball of 'Slimmie' open in another.. Drag the binary across, 'drop' it on the script. All done.
And the same 'trick' works for Iron, too! (Which is hardly surprising...)
I think you're right about libudev. Initially, I'd tried with this still in place a few days ago, before your last post, and.....it didn't want to know. So I've removed it, after performing the BBE-script trick; runs a treat now. Thanks for the tip.
(And there is a LOT less crud in the terminal.)
Under normal circumstances, I'd use your 32-bit packages anyway.....but with having such a convoluted set-up, running multiple sym-linked apps from a remote partition, it really is simpler (for me) to just extract the downloaded tarball, swap 'em over, then perform the mods 'in situ'. But,again:-
.....thanks for the tip!
(davids45 has got a lot to answer for; but his method for running sym-linked apps remotely is a life saver for me. Running the same set of apps in at least 10 different Pups, it'd just be crazy to install every one of 'em 10 times..!)
Cheers.
Mike.
Version 15.0.3.0 (from OscarTalks SFS) running well in LxPupSx 17.07.24, LxPupXenial (XenialPup 7.0.8.1 based), and X-Slacko 4.2. SFS in the Grub4Dos boot directory, shared by all, and the profile in my EXT2 data partition with symlinks in the various pups. No cruft at all in terminal!
Edit: Updated to 15.0.4.0 using OscarTalks i686 SFS on my all intel i5 laptop (Fujitsu S761) running LxPupSc 17.08.21. No issues noted. Also checked in X-Slacko 4.2, X-Tahr-2.0 and LxPupXenial 17.06.1 on that laptop. Starts and runs fine in all.
Edit: Now updated (08/20/2017) to Version 15.1.0.0 on the S761 laptop per above but now running LxPupSc 17.08.23. Also 15.0.4.0 i686 SFS is now running full time on an intel Bay Trail (J1900 CPU) desktop box running X-Slacko 4.3. No issues noted on either.
Thanks,
Edit: Updated to 15.0.4.0 using OscarTalks i686 SFS on my all intel i5 laptop (Fujitsu S761) running LxPupSc 17.08.21. No issues noted. Also checked in X-Slacko 4.2, X-Tahr-2.0 and LxPupXenial 17.06.1 on that laptop. Starts and runs fine in all.
Edit: Now updated (08/20/2017) to Version 15.1.0.0 on the S761 laptop per above but now running LxPupSc 17.08.23. Also 15.0.4.0 i686 SFS is now running full time on an intel Bay Trail (J1900 CPU) desktop box running X-Slacko 4.3. No issues noted on either.
Thanks,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
Bump: 10/16/2017. Now running Version 15.1.5.0 on the SS761 laptop, both in ZestyPup 17.10.13 and in LxPupSc 17.10.22. Runs well in both, using it as the default browser across the board. Twas an edit but I wanted you to know someone appreciates your SFS over time. Download link here
Thanks again.. and again,
Thanks again.. and again,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
-
roadkill13
- Posts: 154
- Joined: Wed 10 Aug 2011, 21:41
- Location: United States
- Contact:
@marv
@OscarTalks
Thank you, Thank you, Thank you...
Running quite well in Musher0's xenial 7.06 derivative.
Thanks for the heads up.Bump: 10/16/2017. Now running Version 15.1.5.0 on the SS761 laptop, both in ZestyPup 17.10.13 and in LxPupSc 17.10.22. Runs well in both, using it as the default browser across the board. Twas an edit but I wanted you to know someone appreciates your SFS over time. Download link here
Thanks again.. and again,
@OscarTalks
Thank you, Thank you, Thank you...
Running quite well in Musher0's xenial 7.06 derivative.
Does anyone have a version of Slimjet that runs on Slacko 5.6 (slack 14.0 compatible) that is capable of accessing Youtube? I have just tried several of OscarTalks versions (that I thought were working on youtube previously) but they all tell me I have no compatible video formats and offer to tell me more about html5.
Are some versions of Slimjet HTML5 compatible or am I somehow setting up wrong?
Are some versions of Slimjet HTML5 compatible or am I somehow setting up wrong?