2/18/2023 0 Comments Ungoogled chromium web storeRestarted UG-C and a proper PROFILE folder was created.Īlso running in LxPupSc64 (slackware deriv) with, as expected, the following libs added to the chromium directory: There's a big red=broken symbolic link to /opt/Ungoogled_Chromium-portable/chromium/PROFILE which makes sense as the portable isn't in /opt. I closed UG-C via Menu>Exit as I wanted to see what the terminal had to say about closing. Just noticed the curious 'boxes' in the quoted terminal output which, AFAICT, were added by the Forum's software. And pass my appreciation on to Marmaduke if you can. What all the above complaints means in practical terms and how much older the glibc can be are yet to be determined.īut, thanks, Mike. Failed to register OID: 0"īut the UG-C opened and I'm posting from it now. InitializeSandbox() called with multiple threads in process gpu-process. initrd/mnt/dev_save/Pup-Apps/Ungoogled_Chromium-portable/chromium/PROFILE " Unable to show a dialog outside the UI thread message loop: Failed To Create Data Directory - Chromium cannot read and write to its data directory: Right-Clicking 'LAUNCH' and selecting 'Run in Terminal' will only take a moment". But I'm running Bionicpup64 which, according to pupsys-info, is using " Glibc: 2.27". So I downloaded and unpacked your portable. A good find, I think.!Īnyways the new 'portable' is now available from the usual location in post #1. A guy by the handle of "Marmaduke" is providing ready-to-go, self-contained portable Linux builds of UnGoogled Chromium (even has WideVine built-in by default, so no need to "borrow" it from Chrome) this, of course, means there's even less work involved in 'converting' them to the Puppy-portable format. Don't know why I never thought of this before. I tracked this down at semi-official "home" of ready-to-go Chromium builds. So how come somebody else can go to all that trouble.and you lazy buggers CAN'T? "Too much hard work too many different versions to cover." Yeah, RIGHT. You wanna know why? Because, mes amis, this one has been compiled with all the VAAPI hardware acceleration stuff built-in.the very stuff that I reported on a few years ago.that Google couldn't be arsed to provide in Chrome itself. Now I could apologise for the humungous size of this version, but.I'm not going to. Here, for your delectation, is the current 'portable' release of UnGoogled-Chromium.v.90. It should work, right? (I tried and yes it does work of course!) Now I'm a little curious about just running chromium from the same directory on both fossa installs. I guess what I'm saying is in Jackal I seemed to have download permissions granted, while in Fossa chromium does not have that permission even in /spot/downloads. Since I had the extensions crx files downloaded on Jackal, I just copied them in to the google extensions on Fossa, and so I have them installed. It's not critical at the moment, since I have many browsers, but you know, I'm always trying to learn something new. The getcrx is installed, the versions are the same (and not running off the same portable directory, I'm using seperate copies) so I'm confused. I don't remember if it was always in Jackal Remaster, or if I installed it When I use the getcrx on regular Fossapup and try to download an extension from the webstore, I'm getting permission denied on the download, even in spot. But I noticed that I now have a permission changer (root to spot, spot to root) option in my sys tray. This getcrx extension worked great in Fossapup Jackal remaster. crx file (remove fake '.gz' first) (9.56 KiB) Downloaded 48 times I know it's a bit long-winded.but it only needs doing once. Result? Your favourite extensions, without involving Google in the process (aside from having to visit the WebStore to find the things).and still no connections to Google's 'nosy' stuff. When you've finished, toggle the 'Developer Mode' button back to the 'Off' position it only needs to be 'On' for installation. (You can also use the same procedure if you have a favourite theme you like to use.) To install your extensions, it's basically rinse & repeat as above, drag the CRX files onto the Extensions page, followed by allowing the installation to proceed. When you find them, go to the extension's Store page right-click, and from the context menu select "Get CRX of this extension". and browse the Web Store to find the extensions you want.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |