New Chromium versions - problem with ElCapitan

Re: New Chromium versions - problem with ElCapitan

Sat, 15 Feb 2020 14:58:43 +0000

Till today all new Chromium Versions works well now!

Re: New Chromium versions - problem with ElCapitan

Wed, 18 Dec 2019 13:07:08 +0000

With the new FreeSMUG build Chromium Version 79.0.3945.88 (Entwickler-Build) (64-Bit) it works now on my both Macs.
What was wrong in the other FreeSMUG Chromium builds?

Re: New Chromium versions - problem with ElCapitan

Wed, 18 Dec 2019 13:05:38 +0000

With the new FreeSMUG build Chromium Version 79.0.3945.88 (Entwickler-Build) (64-Bit) it works now on my both Macs.
What was wrong in the other FreeSMUG Chromium builds?

Re: New Chromium versions - problem with ElCapitan

Wed, 27 Nov 2019 09:57:03 +0000

Google Chromium gives them back to FreeSMUG … bugs.chromium.org ….. id=1027894#c14

It sounds like you are using the FreeSMUG build of Chromium. We don't control how they build Chromium or what additional configurations they have included, so you will need to follow-up with freesmug to resolve this issue.
If you have the same problem in an official Google Chrome build, please open a new bug and include a Net Log

Re: New Chromium versions - problem with ElCapitan

Sat, 23 Nov 2019 22:58:00 +0000

Please give me free permission to embed links.

Sorry, I can't manage this option by single user. It is set to Karma level 1.
More info about Karma here:
http://www.wikidot.com/doc:karma

Re: New Chromium versions - problem with ElCapitan

Sat, 23 Nov 2019 17:22:20 +0000

Now I open an bug report id=1027894
…..bugs.chromium.org p chromium issues detail?id=1027894
I had to change the link.
Please give me free permission to embed links.

Re: New Chromium versions - problem with ElCapitan

Sat, 23 Nov 2019 14:04:03 +0000

I am not so firm with Google bug reports. Please could me tell the link to Google Chrome developer support.

You can follow these steps (only with Chrome):
https://support.google.com/chrome/answer/95315?co=GENIE.Platform%3DDesktop&hl=en

or post a request on Chromium-dev forum (but only about official Chrome builds):
https://groups.google.com/a/chromium.org/forum/#!forum/chromium-dev

or fill a bug here:
https://bugs.chromium.org/p/chromium/issues/list

Re: New Chromium versions - problem with ElCapitan

Sat, 23 Nov 2019 09:46:05 +0000

I found a new hint about this problem:
How do I "update [my] sandbox profile to allow cfprefsd access!"? Console message often coincides with Chrome freezing
iphoneteile.com 212010 How-do-I-update-my-sandbox-profile-to-allow-cfprefsd-access-Console-message-often-coincides-with-Chrome-freezing

Re: New Chromium versions - problem with ElCapitan

Thu, 21 Nov 2019 06:23:37 +0000

I am not so firm with Google bug reports. Please could me tell the link to Google Chrome developer support.

Re: New Chromium versions - problem with ElCapitan

Wed, 20 Nov 2019 21:17:24 +0000

FreeSMUG builds are done with clean Chromium source code, without modifications.
If this bug happens also with official Chorme builds you can open a bug with Chrome developers.

Re: New Chromium versions - problem with ElCapitan

Wed, 20 Nov 2019 17:37:09 +0000

Now I have tested this on a 2nd Mac (also with ElCapitan).
On this Mac there are also several users.
The connection problem only occurs with https (port 443), http (port 80) works.
If a user has never had Chrome open before, https works if a Chromium profile did not exist.
I deleted everything with the name Chromium from a user's directory and searched for Chrome and Google and also deleted suspects. No success.
When I call up an https page I see in the DNS log that the name is resolved.
What prevents the new Chromium versions in particular from accessing https pages under ElCapitan 10.11.6?
Is it SSL/TLS on the part of Mac OS X - but why does this occur depending on the user?

(Translated with DeepL.com-Translator)

Re: New Chromium versions - problem with ElCapitan

Tue, 19 Nov 2019 16:36:51 +0000

Now Chromium_OSX_78.0.3904.108 installed.

I created several users on my Mac.
My main user, where Chromium doesn't work, doesn't have admin rights.
Also with the Chromium_OSX_78.0.3904.108 is the same picture.

Changed to other users on the same Mac, there didn't exist a Chromium profile.
User with admin rights - Chromium 78.0.3904.108 works.
User with no admin rights - Chromium 78.0.3904.108 works.

Back to my main user, searched for Chromium with Find_Any_File and renamed all directories and files under /Users/username/Library/, so Chromium had to create a new profile.
Also with this new profile Chromium 78.0.3904.108 did not work. What could be the reason?

But with the older Chromium 77.0.3865.120 and the same Chromium profile it works.

One of my test pages is dnssec.vs.uni-due.de
The error message:
The website is not available. The website under dnssec.vs.uni-due.de may be temporarily unavailable or has been permanently moved to a new web address.
ERR_FAILED

(Translated from German with ….DeepL.com Translator)

Re: New Chromium versions - problem with ElCapitan

Mon, 18 Nov 2019 11:50:06 +0000

I have installed all my Internet Apps in a subfolder
/Applications/_Browser & Internet Tools/Chromium.app

I'd try with /Applications/Chromium.app
Maybe it will not solve the problem, but just for a test.

Re: New Chromium versions - problem with ElCapitan

Sun, 17 Nov 2019 15:34:32 +0000

Now I had disabled/enabled/set as default Secure DNS lookups without any affect.
Secure DNS lookups
Enables DNS over HTTPS. When this feature is enabled, your browser may try to use a secure HTTPS connection to look up the addresses of websites and other web resources. – Mac, Windows, Chrome OS, Android
#dns-over-https

Re: New Chromium versions - problem with ElCapitan

Sun, 17 Nov 2019 09:19:23 +0000

I have installed all my Internet Apps in a subfolder
/Applications/_Browser & Internet Tools/Chromium.app
Now in Applications/Chromium.app - the same.

I use Opera an Vivaldi too, both use the Chrome engine and works well.

Opera: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36 OPR/65.0.3467.42

Vivaldi: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.99 Safari/537.36 Vivaldi/2.9.1705.41

Re: New Chromium versions - problem with ElCapitan

Sat, 16 Nov 2019 08:21:00 +0000

Now I read on Heise.de

Chrome-Experiment führte zu Browser-Abstürzen in Firmen
In vielen Firmen kam es zu Problemen mit Chrome – plötzlich verschwanden Webseiten und das Browser-Tab blieb leer. Grund war eine experimentelle Funktion.

Translated:
Chrome experiment led to browser crashes in companies
In many companies there were problems with Chrome - suddenly web pages disappeared and the browser tab remained empty. The reason was an experimental function.

Are thist both Flags this problem?

chrome://flags/#web-contents-occlusion chrome://flags/#calculate-native-win-occlusion

Re: New Chromium versions - problem with ElCapitan

Fri, 15 Nov 2019 15:30:54 +0000

All - 78.0.3904.97, 78.0.3904.87, 78.0.3904.70.dmg - have this same problems, my MacOS ElCapitan 10.11.6
Only 77.0.3865.120 works well.
I have installed all my Internet Apps in a subfolder
/Applications/_Browser & Internet Tools/Chromium.app

Re: New Chromium versions - problem with ElCapitan

Fri, 15 Nov 2019 15:20:59 +0000

Sorry, I could not insert links to pics.

Re: New Chromium versions - problem with ElCapitan

Fri, 15 Nov 2019 15:19:16 +0000

I open your page with 78.0.3904.97 with macOS 10.14.6. Probably is an ElCaptitan issue.
FreeSMUG builds are done with clean Chromium source code without modifications.
Does this problem happen with last Chrome version?
If yes, you can open a bug with Chrome/Chromium developers.

New Chromium versions - problem with ElCapitan

Fri, 15 Nov 2019 15:00:22 +0000

Hi,
the last chromium versions have a network problem in ElCapitan
The last version that works well 77.0.3865.120
With the newer I could't open some web-sites.
So as this dnssec.vs.uni-due.de
I use the same user profile. Now I had installed
Chromium 77.0.3865.120 (that works well)
Chromium 78.0.3904.97 (this version don't work as described)