Slimjet web browser

[duckguy]

Curious. Where are you getting your SlimJet from, may I ask?

---------------------------------------------------------------------
Hi Mike, I was using slimjet-12.0.11.0-tahr.pet, but it will not load. Good news though, I found a later vesion (that loaded) here: http://www.mediafire.com/file/7n0opd8xp ... tahr.pet#!

I also don't understand why your copy of Tahr64 is 'buggy', and 'crashes frequently'. My own is as stable as they come; it's where I package the 64-bit versions of SlimJet.....and they run just fine.

-------------------------------------------------------------------
First of all, in Tahr64, the touch pad never configures properly. The settings must be reconfigured every time the system reboots. Also the memory frequently clogs with data overflow and then the system freezes, which requires the user to do a hard reset of the system. I almost never shut down Tahr64 normally - because it locks up so frequently. I really like its speed and smoothness but it's unstable (at least the configuration that I have).

By the way, thank you for replying so astutely and with such alacrity! B"H.

Hi, duckguy.

Curious. Where are you getting your SlimJet from, may I ask? The 32-bit versions that both Oscar and I do for Puppy run without any problems...

I also don't understand why your copy of Tahr64 is 'buggy', and 'crashes frequently'. My own is as stable as they come; it's where I package the 64-bit versions of SlimJet.....and they run just fine.


Mike.

[duckguy]

Curious. Where are you getting your SlimJet from, may I ask?

---------------------------------------------------------------------
Hi Mike, I was using slimjet-12.0.11.0-tahr.pet, but it will not load. Good news though, I found a later vesion (that loaded) here: http://www.mediafire.com/file/7n0opd8xp ... 6-tahr.pet#! ... this updated version is loaded and running.

I also don't understand why your copy of Tahr64 is 'buggy', and 'crashes frequently'. My own is as stable as they come; it's where I package the 64-bit versions of SlimJet.....and they run just fine.

-------------------------------------------------------------------
First of all, in Tahr64, the touch pad never configures properly. The settings must be reconfigured every time the system reboots. Also the memory frequently clogs with data overflow and then the system freezes, which requires the user to do a hard reset of the system. I almost never shut down Tahr64 normally - because it locks up so frequently. Also, the screensaver never comes on, no matter how many times it's configured. The computer's sleep mode locks up Tahr64, requiring a hard reboot (yet in Tahr32 both sleep mode and screensaver work smoothly on the exact same hardware). Also, I do have the 32-bit compatibility mode utility installed. Tahrpup64 is buggy though. I really like its speed and smoothness but it's unstable (at least the configuration that I have).

By the way, thank you for replying so astutely and with such alacrity! Sorry to take so long to reply. I replied before, but the message board just shows my reply as a blank entry. B"H.

Hi, duckguy.

Curious. Where are you getting your SlimJet from, may I ask? The 32-bit versions that both Oscar and I do for Puppy run without any problems...

I also don't understand why your copy of Tahr64 is 'buggy', and 'crashes frequently'. My own is as stable as they come; it's where I package the 64-bit versions of SlimJet.....and they run just fine.


Mike.

[Mike Walsh]

Ah, well; as long as it's now up-and-running, that's all good.

Looks like one of mine; Oscar uses Yandex, AFAIK (after copy.com went under last year).

We do what we can to ensure maximum compatibility, but sometimes it's simply down to how much customising the individual has done with their system, or the particular combination of hardware.

The Chromium-based browsers all seem to rely, to a greater or lesser degree, on a number of the libs to be found in the FireFox directory, in /usr/lib. If you'd been using the version to be found in QuickPet, then I believe PhilB, when he was developing and building the Tahrs, mainly took many applications from their respective websites and did a direct .pet conversion on them. He wouldn't have had time to go through all the launcher scripts for every single one of them.....and the Chromium-based browsers have an enormous list of available command-line 'switches' which can be applied to the exec-line in the launcher scripts. Have a look here, if you don't believe me:-

http://peter.sh/experiments/chromium-co ... -switches/

There's well over a thousand individual commands there.....and the potential number of combinations is mind-boggling, to say the least!

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

I must confess, several of those problems you mention there are peculiar to laptops; like the touchpad, and the 'sleep' function.....stuff like that. My 64-bit machine is a BIG old Compaq business-class desktop PC, from around 12-13 years ago. My laptop is an even older Dell, from 2002.....with a P4, no less.

Still runs a lot of the modern Pups, though..!


Mike.

[duckguy]

Ah, well; as long as it's now up-and-running, that's all good.
Looks like one of mine; ...
I must confess, several of those problems you mention there are peculiar to laptops; like the touchpad, and the 'sleep' function.....stuff like that. ... Mike.

OK! I am running two laptops, that's true. One old Toshiba with a dual core AMD chip, and a slightly newer HP with a dual core Intel chip. Both are around ten years old. Both have the same issues with Tahr64, touchpad, screensaver, memory clogging. The Toshiba is maxed on RAM, but the HP still could take another 2GB. I found Tahr64 to be smoother on both. Tahr32 is rock solid on them though. There is almost nothing that can crash it and all the functions of the laptops work with no struggles.

Maybe I need a desktop like yours. Thanks for your help! B"H.

[Mike Walsh]

Interesting you should say that.

I, too, find the 64-bit Pups to be somewhat 'smoother' in their operation.....yet still prefer the 32-bit Pups, simply due to their blistering speed..!

And you're right about 32-bit Tahr 6.05 as well. It was the very first Pup I'd found, over two years ago, that simply 'worked' on ye ancient Dell, OOTB, without the need for any funny 'workarounds'. The Dell uses the Intel 'Extreme' graphics adapter, which for long enough has been acknowledged by many to be nothing more (& nothing less) than a king-sized PITA to use under Linux.

Works perfectly under XP, of course.....and yet, to give Intel their due, when you do discover how to get it working under Linux, it still gives (even after almost 15 years) a razor-sharp, crystal-clear picture. There's nothing wrong with its operation, yet it's the sort of 'tiffling-about' that puts many newcomers to Linux right off their stroke..!

Tahr 6.05 is by far the most 'stable' of the recent generation of Pups.....which is why I've never had the slightest hesitation in recommending it. To anybody.

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

Maybe I need a desktop like yours.

Hah! The old girl was rescued from an ignominious trip to the dump nearly 3 years ago; my sister had just bought a new one pre-loaded with Win 7, 'cos XP was at EOL. I took it off her hands; my bro donated a 15" Dell monitor; he'd just quit using Windows, and treated himself to a top-of-the-range iMac, with the 34" Retina display.....and the keyboard, mouse, peripherals, etc., I'd got already. It's had a lot of upgrading; it was a top-end machine for its time, although outfitted with a 'basic' spec.

Lots of room for maneouvre!


Mike.

[OscarTalks]

Some time ago I was thinking of stopping uploading any repacks of Slimjet. This was largely because the multimedia support did not seem as good as it is in some of the other Chromium derivatives.

This has been improving though in some of the more recent Slimjet versions and in 13.0.8.0 support has been introduced for additional media codecs via libffmpeg.so which has been the case in some other browsers for a while.

Instructions on the website talk about downloading the (pre-compiled) libffmpeg.so lib from git and installing it in the "/lib" subdirectory. The downloaded slimjet package contains a version of it in the main slimjet directory. A little confusing, but anyway what I did was download the git version, strip it and put in in place of the packaged one. I also created a relative symlink in the /lib subdirectory so it is effectively found in both locations.

Please note that for Slacko 6.3.x you should be able to use the "tahrpup" version which does have some working sandboxing.
https://yadi.sk/d/fd8rBM0WoF9sB

[Marv]

"tahrpup" version 13.0.8.0 up and running well in X-slacko 4.2, X-slacko slim 4.2r42, and LxPupSc 17.03.32T. All on frugal Grub4Dos installs to a core 2 duo all intel laptop. The profile is on a second EXT2 partition on the SSD and symlinked from /~/.config. For X-Slim I added these libraries as it comes with no moz or firefox browser libs on board

Code: Select all

/opt/slimjet/lib: 
libnspr4.so.0d libplc4.so libplds4.so.0d 
libnss3.so libplc4.so.0d libsmime3.so 
libnspr4.so libnssutil3.so libplds4.so libssl3.so 
/opt/slimjet/lib/nss: 
libfreebl3.chk libnssckbi.so libnssdbm3.so libsoftokn3.so 
libfreebl3.so libnssdbm3.chk libsoftokn3.chk 

but for the other two pups only the symlink to my slimjet profile (same as I used for 13.0.7.0 and 13.0.3.0) was needed. Seems like the first run after boot (not in RAM) is a bit quicker with your wrapper than with the stock slimjet wrapper I used with 13.0.7.0. Nothing fancy tried with it but all-in-all right now it is my favorite chromium deriv. and I haven't had it fail on any site or lock up in a fair bit of use on the three pups above.

Thanks,

[OscarTalks]

Pepper Flash update to 25.0.0.148
Slimjet update to 13.0.9.0
Still based on Chromium 55 but
Although it wasn't mentioned in the change log when I looked
Slimjet directory now contains the widevine libraries
These show up in slimjet://plugins and are used for Netflix and some other things.
People who use such features may wish to test
https://yadi.sk/d/fd8rBM0WoF9sB?force_show=1

[greengeek]

Slimjet update to 13.0.9.0
Still based on Chromium 55 but
Although it wasn't mentioned in the change log when I looked
Slimjet directory now contains the widevine libraries
These show up in slimjet://plugins and are used for Netflix and some other things.

Thanks Oscar - just tested the Slacko 14.0 pet and it works perfectly for me in a Slacko 5.6 derivative.

Netflix working perfectly.

cheers!

[Marv]

"tahrpup" version 13.0.8.0 updated to "tahrpup" version 13.0.9.0 in LxPupSc 17.04.1 smoothly. I'm running the SFS versions so it's just a matter of unloading the older SFS and loading the newer. The symlink in /~/.config/ to my profile on a data partition is unchanged. No issues noted, not a lot of errors run from terminal, only

Code: Select all

getrlimit(RLIMIT_NOFILE) failed
getrlimit(RLIMIT_NOFILE) failed
getrlimit(RLIMIT_NOFILE) failed
getrlimit(RLIMIT_NOFILE) failed

Thanks,

[OscarTalks]

Version now 14.0.1.0 (beta) 32bit
Based on Chromium 57
Run-as-root and some sandboxing ("adequate" in current Puppies) using bbe.
Suggested libffmpeg.so and pepperflash on board.
The one i686 version should also now be good for Precise and Wheezy.
I did still do a Slack14.0 one with the extra libs
https://yadi.sk/d/fd8rBM0WoF9sB?force_show=1

[Marv]

Thanks, OscarTalks. Various installs (13.0.7.0, 13.0.8.0, 13.0.9.0 all updated to 14.0.1.0 using the i686 SFS. Running in X-tahr 2.0, X-Slacko 4.2, LxPupXenial 7.0.8.1 and LxPupSc 17.04.1. It's very polite about pointing out that the profile (external and common to all for me) has been updated to 14.0.1.0 and that some changes would be lost/overwritten by running older versions with that profile. No exotica tried at this point but it seems rock solid. Slimjet is quite firmly my goto browser in all my pups at this point.

Cheers,

[artsown]

@OscarTalks

I used slimjet-14.0.1.0-i686.pet on latest versions of pups slacko, tahr,
xenial and vivid .... all working ok.

Do you plan to create a 64 bit version?

Art

[Mike Walsh]

Hi, Art.

No, that'll be my doing, at some point in the next few days (current health problems permitting!)

http://www.murga-linux.com/puppy/viewtopic.php?t=106957

You won't have to wait too long for the 64-bit version.....


Mike.

[greengeek]

...current health problems permitting!
Mike.

Clearly not drinking enough wine to kill the bacteria Mike!

[Mike Walsh]

Hi, GG.

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.

[greengeek]

Condolences. Sounds most unpleasant.

[Moat]

Yeah, Mike - hang in there! A bit of wine is supposedly good for such things (so I've heard ). Hope it was mild, and you're gettin' on top of it, and on with things.

Working on a gallbladder issue myself (wish they could just yank the damn thing out, already!! ).

Best to ya',

Bob

[Mike Walsh]

Thanks, guys. Seriously. It's appreciated.

Don't worry; I ain't got any plans to disappear off the scene for quite a while yet..!

(They'll have to drag me off in a casket before I do. Eeh, what it is to get old, eh? *Jeez*)

Never mind. Onwards & upwards..!!


Mike.

[Marv]

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
# [107260614/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?