Umm. Mm-hm.
I always did have 'issues' with up-to-date Chrome in Tahrpup64. It's part of the reason why I switched to doing my development/packaging work in Xenialpup64.....it never gave me any problems.
Tahr64 was 666philb's very first 64-bit Puppy. Naturally, it was a learning curve, not only for him, but for the rest of us, too. By the time Xenial Xerus 16.04 LTS was released, Phil had learnt a lot of 'tricks' from his first 64-bit attempt, with the result that Xenialpup64 has just been that much smoother, and more stable, from the outset. We all learn from our mistakes.....it's how the human learning process works.
Not being funny, but I would definitely suggest upgrading to Xenialpup64. 'Trusty Tahr' went EOL on the 30th April (day before yesterday), so is now unsupported. (I mean, Puppies are in fact 'timeless', as we all know.....but even Puppies have to move on in order to be able to run newer software.)
I vaguely recall the problem in Tahr64 being something to do with the available version of GTK-3.0; newer versions wouldn't 'play nice' with the system libraries, etc (and too many things needed upgrading to make it worthwhile 'fixing').
------------------------
Try this. I assume you're trying to run the newest version I've just published, yes? If so, run
Code: Select all
/home/spot/chrome.sh
Mike.