(old)Puppy Linux Discussion Forum

Now:
chromium_80.0.3987.149+pepper_32.0.0.344

24-June-2020

Will work on LxPupSc32, LxPupSc64, ScPup32, ScPup64, BionicPup32 & UPupEE/EF, FossaPup64 (if adrv included) **

32-bit:
chromium_83.0.4103.116+pepper_32.0.0.387

64-bit:
chromium64_83.0.4103.116+pepper_32.0.0.387

** n.b. BionicPup64-8.0 requires the 64-bit .sfs to be converted - see: http://murga-linux.com/puppy/viewtopic. ... 205#867205 (use option 2)

Hello Peebee,

Is there a trick I missed in getting sound to work with your latest build aboard Bionic64?

There are currently no issues with PaleMoon's ability.

==

Omit that. My levels were off.

Hello again, Peebee.

Is Chrome's Native Client plugin built into your version, and if possible, how would I enable it for use with TeamViewer's extension? I'm currently running Bionic64.

TIA

Semme wrote:Is Chrome's Native Client plugin built into your version,

Not that I know of.....try Chrome?
https://sourceforge.net/projects/lxpup/ ... /browsers/
will also need converting for BP64

Chromium's what I was referring to posting in this thread.

If you can tell me, great. If not, I'll dig a bit further.

Thanks.

==

Actually, I'll simply accept the fact that TeamViewer for Linux is no longer a Pup-centric alternative and instead go with one of the remote-desktop options tested and confirmed to work by Mike Walsh.

Thanks again.

28-Apr-2020

chromium_81.0.4044.122+pepper_32.0.0.363

03-May-2020

chromium_81.0.4044.129+pepper_32.0.0.363

12-May-2020

chromium_81.0.4044.138+pepper_32.0.0.371

22-May-2020

Now: chromium_83.0.4103.61+pepper_32.0.0.371

Interesting read:
https://alien.slackbook.org/blog/chromi ... ne-plugin/

Thanks again peebee. Your packages continue to work perfectly on my bionic64 system. Keep 'em coming.

09-June-2020

Now:

chromium_83.0.4103.97+pepper_32.0.0.387

17-June-2020

now:

chromium_83.0.4103.106+pepper_32.0.0.387

G'day peebee,

Ran latest v83 sfs (made into links from its files on my data partition) which was very nice in a LxPupSc64 but I can't find where a profile was created that could be then copied/linked/shared to other 64-bit Pups on my desktop (all in my 64-bit Pups partition).

I looked in ~/.config but no new directory had appeared.

Manually copied Chromium's exported bookmarks to a 64BionicPup using the same new sfs as LxPupSc64 and again I couldn't find a new chromium directory in its ~/.config.

But both re-start with the added data ('profile'), called up from somewhere, but where?

Thanks for any help.

David S.

davids45 wrote:but where?

**Runs-As-Spot** so.........

/root/spot/.config/chromium

with ownership spot:spot

G'day peebee,

Thanks for your quick reply.

I'll see if I can adapt this to suit my preferential way of doing browsery things.

I might need to try Chromium in a Portable version if not?

More to learn.

David S.

Experimental.............beta of next version.....
constructed from snap
chromium-beta84.0.4147.68.sfs

Runs OK on LxPupSc, ScPup32, BionicPup32 (UPupBB32) and UPupEF32

24-June-2020

now:

chromium_83.0.4103.116+pepper_32.0.0.387

peebee wrote:24-June-2020

Will work on LxPupSc32, LxPupSc64, ScPup32, ScPup64, BionicPup32 & UPupEE/EF, FossaPup64 (if adrv included) **

32-bit:
chromium_83.0.4103.116+pepper_32.0.0.387

64-bit:
chromium64_83.0.4103.116+pepper_32.0.0.387

** n.b. BionicPup64-8.0 requires the 64-bit .sfs to be converted - see: http://murga-linux.com/puppy/viewtopic. ... 205#867205 (use option 2)

Does it also works on xenialpup 32 bit?

memo wrote:

peebee wrote:24-June-2020

Will work on LxPupSc32, LxPupSc64, ScPup32, ScPup64, BionicPup32 & UPupEE/EF, FossaPup64 (if adrv included) **

32-bit:
chromium_83.0.4103.116+pepper_32.0.0.387

64-bit:
chromium64_83.0.4103.116+pepper_32.0.0.387

** n.b. BionicPup64-8.0 requires the 64-bit .sfs to be converted - see: http://murga-linux.com/puppy/viewtopic. ... 205#867205 (use option 2)

Does it also works on xenialpup 32 bit?

Yes it does..works perfectly.