Now we're back in the swing of things..!
Currently testing the 'beta' of Chrome 63.0.3239.30. NetFlix fine; Pepper working A-OK. At present, everything looking very smooth. No issues to report.
Mike.
![Wink :wink:](./images/smilies/icon_wink.gif)
Fatdog is true multi-user without sudo. The release system has one full user, root, and a "limited" user, spot, which is used to run Seamonkey by default. But you can run pretty much any process as spot by prefixing its command line with "run-as-spot". So I run Chromium-based browser Opera that way. It works well. For pepperflash support I have to specify the pepperflash.so path with --ppapi... and place the library file in spot's home folder with spot's ownership. Please note: don't hardwire /root/spot as spot's home. Instead read its location with ` ls -d ~spot` (bash) or `grep spot /etc/passwd|cut -d: -f6` (other shells).jake29 wrote:Maybe someone else can correct me if I'm wrong, but /root/spot/ exists and appears to be used in FatDog. My understanding of this is limited.Mike Walsh wrote:Ah, I'm pleased to hear that. Does FatDog make use of 'spot'? Never having used it, it's not something I was aware of.....
I'll let you into a few secrets, mate. I may have only been a Puppian for about 3 1/2 years, but I've been a Chrome user from day one. I downloaded that very first beta, pre-release evaluation spin of Chrome, in Autumn 2008.....and I've never looked back since.ally wrote:I do not like spot, very restrictive for me if I'm batching without being able to use wget.
Nah, you're all right, mate. I thought it was as good a time as any to clarify the situation as of this moment in time.....seems like Google have been making major changes with every other release these last few months.ally wrote:I fully understand it is a chrome's making apologies if it came across otherwise
Hello Mike,Mike Walsh wrote: No real problems to report, aside from the afore-mentioned possible reluctance to download/upload without freezing-up/crashing.
A slight bit of an aside, still chromium related, but this hint fixed the problems I had with Slimjet version 18.0.1.0 running from SFS in LxPupSc64 18.03 crashing/exiting on any attempt to save-to etc. I ranOscarTalks wrote: This may be happening because GTK3 needs its file chooser.
When you download or upload you get that window asking to browse for location.
The libs alone don't provide this.
Look in /usr/share/glib-2.0/schemas
There should be an .xml file for FileChooser and at least one other for ColorChooser.
If those are present you then have to run the command glib-compile-schemas
This updates the gschemas.compiled cog-wheel file to include all the .xml files present.
But the snag is that users may have other .xml gschemas files already installed and you don't want to "uncompile" those. Also, if you include an updated gschemas.compiled file in an .sfs package it won't appear above an existing one in the layered file system. I believe we don't have the option of a pinstall.sh script either.
I like the idea of standalone all-inclusive packages for convenience and I know that others are offering them. In this case though I am not sure what the best way forward is. Options include instructing the user to install the GTK3 package via PPM and removing it from the Chrome package or at least instructing the user to run glib-compile-schemas after loading the Chrome .sfs package (with the .xml files included).
Code: Select all
glib-compile-schemas /usr/share/glib-2.0/schemas