I am a newbie at using a live usb persistent version of Puppy Linux (tahr64-6.0.5) with an encrypted save file. I have installed your latest Chrome sfs which generally works well. Thank you. However, whenever I try a right click and save action (e.g. right click "save image as") Chrome crashes to a black screen and I have to reboot.

Hallo, plrsmith. And 'Welcome' to the kennels. Nice to have you on board...

Y'know, I suspect your problem stems from that encrypted save-file. I don't know of anybody who actually uses one of those things. With Puppy, it's just unnecessary, extra 'complication'.....and it makes Puppy work twice as hard.

However.....

Can you give us some idea of your hardware; make & model, CPU, RAM, HDD, graphics, etc?

How did you install Puppy? Full or 'frugal'? HDD.....or flash drive? Where did you get the download from.....and did you check the md5 hash, just to be on the safe side? You might have a corrupted download; I've not heard of Tahr misbehaving quite like that before.

Mind you, Google are steadily making it harder & harder to produce the Chrome packages for Puppy. Many of us are turning to FlashPeak's SlimJet browser, and SRWare's Iron browser; both based on Chromium (which is where Chrome draws its source code anyway), and both allow you to use a normal Google a/c, along with all your bookmarks and extensions. And the Puppy packages are both 'NetFlix-ready', with the WideVine DRM modules already installed.

You can find them both at the MediaFire a/c in my sig; 'My Puppy Packages'. Just navigate through and help yourself.

It's also possible your Tahr64 needs the GTK-3.0 stuff installed; Chrome has required this since 56 or 57.....but I don't think it'll even fire up without it. You would need to manually install that from the PPM (Puppy Package Manager); you may have realised by now that Pup doesn't 'do' automatic updates.....it's all very 'hands-on', I'm afraid!

Thank you for your response. In answer to your questions. I have been using Linux for about 15 years now but am by no means an expert, although I know my way around more than some. However, I am new to USB live installations though and very new to Puppy Linux.

I am trying to revive an old (10+ years) Panasonic Letsnote CF-Y7 Laptop which is a Centrino Duo L7300 1.4GHz with built in 965GM graphics and 2Gb RAM. It is currently running Fedora 20 (which is no longer supported) and I have been experimenting with using a live persistent version of PuppyLinux on a 64GB USB stick to make certain aspects of my PC usage completely and very easily portable. It is because I intend to carry this USB stick around that I have encrypted the save file. The PuppyLinux even though it is on a USB stick is much faster than the installed Fedora OS.

I installed the official distribution of puppy tahr64 from one of the official mirrors and checked the MD5 hash. I have libgtk-3-bin_3.10.8 installed and cannot see any further gtk3 packages in PPM. Chrome loads and starts without hitch.

I also thought my problems may be due to the encryption but I could not see how to remove the encryption from the save file. Can I do this? Or do I have to start from scratch again?

Since my original post, I have discovered an additional problem. Viewing YouTube videos crashes the x server. That is the video keeps playing ( I can hear the sound) but the display goes black.

I am happy with everything else with this installation (although I had to change the permissions on the my-documents folder) and can connect to my wifi, print to my wireless printer, use Libreoffice, mount all the drives/partitions on the laptop etc.

The built in Palemoon browser seems to work without any problems but I would like to use Chrome if possible.

Hm. Well, I'm pretty certain this isn't what you want to hear....but the easiest way to get rid of the encryption is to create a new save-file (without encryption.)

What I would do is to make a back-up of the existing save-file. In Puppy, this is literally a simple copy/paste operation; just copy the save-file to somewhere safe. Then, delete the one on the USB stick's /mnt/home. Reboot, shut-down straight away, and create a normal save-folder. The save-folder has the advantage of being able to expand/contract (like a normal folder/directory) up to the available space on the partition.....unlike the save-file, which periodically needs enlarging if you add a lot of stuff to Pup.

If everything else is working fine, great; that's good to hear. Try it with recreating a new save-folder (you'll have to re-load the Chrome SFS, of course), and let us know what transpires, please. If you've still got problems after that, we'll have a think about the next step. Hopefully, there won't be one!

Thanks. I was afraid that would be the case. I will have a go at that tomorrow hopefully. Actually I might just try a new install without encryption on a different usb stick before giving up with this one. I'll let you know how I get on.

On a different note I tried the SlimJet browser as suggested but this would not start. It gave an error message saying that this could not be run as root but I could not find a way of starting it as spot. Have I missed something?

On a different note I tried the SlimJet browser as suggested but this would not start. It gave an error message saying that this could not be run as root but I could not find a way of starting it as spot. Have I missed something?

Nope, you haven't missed anything. This is one of those afore-mentioned little 'problems' that I'm working on right now, in fact, with the newest release, 15.1.4.0. I'm in the middle of doing a revised build as I write this.

Do this for me, would you? (Just to confirm that it's what I think it is...)

Enter

Code:

/usr/bin/flashpeak-slimjet

...in the terminal, and post the output back here for me, please. That'll tell me what I want to know; all of the Chromium-based browsers are pretty 'noisy' in the terminal, but the output provides good trouble-shooting material. Thanks.

Give the new version of SlimJet a try (I've just uploaded 15.1.4.0 this morning), and let me know if it works for you. I've 'treated' both the slimjet 'binary' and the 'slimjet-sandbox' with PhilB's 'bbe' script. This should have corrected the problem, all things being equal.

Let me know what happens, please. Oh, one little tip for future postings, which just makes it easier for everyone to read; when you post terminal output stuff, highlight that section, then just click on the 'Code' button above the editor window. That'll wrap

Code:

highlighted text

.....code 'tags' around that section, and make it stand out better, as above.....okay? Every forum I've ever belonged to does the same things in a different way.....Murga-Linux.com is no different in that respect..!

I have tried both Slimjet and Iron and they both install and function properly synchronising with my chrome account.

Chrome still does not install/work but I no longer need this as Iron and/or Slimjet meet my requirements.

Thank you for your assistance

Peter

Excellent! That's what we strive for here at Murga-Linux; happy users! SlimJet is an awesome browser, TBH. I think I only keep up with Chrome out of habit, these days..... With SlimJet, Iron and the like around now, there's no longer any real need to do so.

Was just wondering, I know Google has been giving us the middle-finger lately, but is there anyway to get your "Google-Chrome-62.0.3202.62-amd64-slacko.sfs" working in micko's latest Slacko64-6.9.9.9? I've loaded it in two different 'frugal' installs I have of Slacko64-6.9.9.9, and the sfs loads & installs ok, but it will not start or run.

If the new chrome versions won't run, what's the latest we could fall back to for Slacko64-6.9.9.9 w/o going to far back in terms of releases??

If the new chrome versions won't run, what's the latest we could fall back to for Slacko64-6.9.9.9 w/o going to far back in terms of releases??

Thanks.

Mm. 60 should be OK; I'm still using it myself, because it also uploads/downloads without crashing, too. I've still got it hanging around somewhere; I'll re-upload 'em if you like, in case anybody else is interested.

I started to downloaded it, then happened to look in a 'frugal' install-backup I had of another pup, and there it was! Boy, I really need to do some housecleaning on the 'frugal' install backups I have, and also backups overall.

Thanks again.

Also, I had one last question:

What is the idea behind the 22mb "lib' folder you have in the chrome.sfs files? When you go straight to Google, of course this isn't included in their download files, and I've found these downloaded chromes (debs) runs fine in my 64-bit pups. So I'm curious about these included "libs" and also a few other things:

1) this "lib" folder is placed inside the /opt/google/chrome folder. Shouldn't it be placed in the respective pup OSes /usr/lib folder?

2) also, most 64-bit pups already have these libs in that /usr/lib/ folder, so I am confused why they're again in the sfs?

3) Also, the "libpuppygc.so". I'm still too stupid to understand that, exactly what it does and also when it is placed in the actual startup of "google-chrome"? Is the idea to make the chrome.sfs self-reliant with all libs included in the sfs, and thus not having to worry about if they are all there in the 64-bit pup it is being installed to? And for your sfs creations, running Chrome means it uses the libs and only the libs that are in the sfs, and not the ones in the puppy OS? If so, is the libpuppygc.so thus the so-called "Governor" to make all this happen, since it is the first thing 'pre-loaded' in the line 35 of /opt/google/chrome/google-chrome?:

P.S. Sorry if I'm asking too many questions...just trying to learn more, and clarify confusion when attempting to understand all things puppy--which I'm fairly sure will never happen given this neanderthal-thick skull of mine.

Yes, you're right about why the 'lib' folder is within the 'Chrome' folder; it is to make the browser self-reliant.....to stop the libs 'breaking' compatibility for other, existing apps (I have no idea what other people may have installed!) As for the contents, battleshooter pretty much figured them out.....it's to do with the upgraded NSS requirements, and all the dependencies thereof.

'Libpuppygc.so', well; rather than me try to explain it, read Iguleder's post on the subject, where he introduced it:-

LD_PRELOAD is all to do with pre-loading libs'n'stuff, & 'environment variables' (which I still don't fully understand; I'm no 'coder', I'm afraid). All I know is 'libpuppygc.so' works......or did do, up until Chrome 62. I'm still working on that, but it may be a wee while before I finally figure out the 'magic formula' that'll get it running the way I want it to. Chrome 63 will probably be out before I do; I have a lot of 'irons in the fire' at the moment. Chrome's kind of on the 'back-burner' for now; 60 is working fine for me on the odd occasions when I do boot into Tahr64, so I'm sticking with it for now.....

The libs probably are in the newer 64-bit Pups.....but the only one I'm currently running is the oldest, 'modern' 64-bit Pup; Tahr64. And that one needs that stuff.....and there's still plenty of people who use it.

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

To be fair, you cannot point the finger at Google. Chrome is written for the 'multi-user' model. 99% of Linux distros employ that 'multi-user' model. Almost all of those distros also have regular, on-going updates.....so by the time Chrome release a variant like these last two, everybody's systems are already capable of running it. This is one of those Puppy-specific problems (due to the 'root' model, and lack of automatic updates) that simply has to be tackled as & when it crops up.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum