That effort took me almost 10 days… ten frustrating days. Note that configuring Chromium to use a different Google Client-ID is not hard to do – but I leave it as an exercise for the reader to find out how exactly this is done.Īfter this debacle with Chromium 94 I decided to instead build a package for chromium-ungoogled since that variant is incapable of syncing data to/from Google anyway and I wanted a working browser. I have not found a way to fix this crash behavior, and decided to forestall a package upgrade in my repository until I am certain that it can be fixed at all – or not. Unlike with pre-94 releases where I performed the same tests, enabling Google Cloud-sync makes the browser crash every time I start it after it has completed its initial full sync (making all my bookmarks, passwords and browser history available locally). What did take me by surprise is what happened when I switched to a different Google client-id one that does have access to Google Cloud sync. Well OK, I was waiting for that to happen since March of this year so no real surprise there. It did not take long to discover that in Chromium 94, finally my Google client-id stopped working, meaning a loss of access to my Google Cloud-synced data. It took some work to get it to compile without errors – an annoyance which always occurs when switching to a new major source release. I started building one of the earlier 94.x source releases of Chromium (to create the actual chromium, not the chromium-ungoogled package). Read my earlier article “ How to un-google your Chromium browser experience” to learn more about my reasons for providing the package as well as pointers to make it a pleasant browser experience.īack to my first sentence of this blog post. It’s still the powerful Chromium browser engine but then without the privacy concerns that surround Google’s Chrome browser and to a lesser extent also its Chromium open source variant. This is basically what Eloston’s project does. The un-Googled version of Chromium is incapable of “phoning home” to Google, by altering the source code and stripping/mangling all occurrences where that might happen. Extended leave of absence of the maintainer seems to be the issue which by now has been resolved by giving more people commit access to that repository. In part because the un-googled repository maintained by Eloston did not offer release tarballs for a while. It’s a jump from the 92 to the 94 release (.81 to be precise) but I simply did not have the opportunity to build a 93 release. You can find packages for Slackware 14.2 and -current in my repository on. After nearly two weeks of pulling my hair out I finally was able to build the newest Chromium in its un-Googled variant.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |