Yea, sorry that I mentioned strace. It requires a person to have some low level programming knowledge to interpret. (software engineer here with 40+ years, now retired).
BTW, opi and Flatpak don’t interfere.
One other thing … in this forum, there is:
Which is available to paste large amounts of data, then you paste the link into the Reply - most folks in here won’t click on a 3rd party link.
Another user with the “159 error” problem:
Hello, thanks again for your help. Some data there are clear to me, mostly not.
Yeah, sure opi and flatpak are different to each other, but have installed and using opi codecs and chrome. I have to restore to default Tumbleweed, remove opi and use flatpak, but i find flatpaks slower than normaly official packages.
I have prob with paste.opensuse.org, Both Chrome and Falkon crash tabs pasting on this page.
I saw it with interest, and i’m watching out the internet wherever i can, Chrome is already unused now for me, even Falkon browser sometimes stops loading pages. It looks like I’m going to Firefox, but since I’m the user of KDE i find Chrome more favorable and performs better, of course FF has much better safety as chrome. I look more appropriate chrome with kde when it comes to performance of pages and web social network servies.
Thank you for the suggestions and advice.
A new post has been made (which I answered) about the browser (Chrome), so now we have multiple posts about this issue.
As I mentioned before, I think this problem is related to Tumbleweed.
newest thread about problem
.
BTW: Is this 159 error bug report somewhere? I would like to know how it will be fixed, when and where.
I must be completely stupid or these pages just work as they please. I tried to write just two lines of text, but the above printout came out unintentionally.
I wouldn’t worry about the excessive, quoted stuff.
HOWEVER, when I click on the link posted by
@promeneur … yes, I get the “This page is no longer available” response. I even copied the link and tried other browsers. Same error
So, I assume the link posted by @promeneur has a flaw.
I don’t know why but this report is visible only for me.
Chrome support is also weird.
I send a bug report
The answer to my bug report
I do not believe that we should use bugzilla as an escalation path for user
support questions. Chrome is a third party package. In the absence of
further information, contact the vendor and work with then.It seems the problem is Tumbleweed environment.
Why do you think that? Your report lacks technical details.
We do not ship Chrome, you can try the chromium package though.
This is not actionable as a bug. Closing.
this is disappointing.
Switch to Firefox and help yourself with error 159, and the Firefox cause that needs more users.
However, it shouldn’t be surprising, because Chrome is not a openSUSE-modified | enhanced version.
Chrome does offer a list of error codes - execute this URL in Chrome:
chrome://network-errors/
I did a search for “159” and found one possible match:
ERR_SSL_UNRECOGNIZED_NAME_ALERT (-159)
aand one possible match for 149:
ERR_SSL_BAD_PEER_PUBLIC_KEY (-149)
You stated that you had a ticket out at Chrome Support at Google … you might want to update your ticket with those possibilities.
Good news, openSUSE reopened the bug report.
I understand it’s because Chromium gets the same problem. See the comment #3
I wrote my own experiences in that bug and it was reopened. I think it needs to be investigated to see where the problem is - at least I don’t know that either.
https://bugzilla.opensuse.org/show_bug.cgi?id=1239780
Oh yeah. Ritva Opas is the same as RaijaR. I had to change my username a couple of years ago because I messed up my username. Ritva Opas is an anagram of the words “vara posti” (spare mail)
That’s great the openSUSE team opened the ticket back up.
It’ll be interesting to read what they find. An strace log would be helpful. If I had the problem on Leap 15.6, I’d add an strace.
And yea, @raijar … I was out searching the Chrome Support at Google last night, for the 159 issue, and I seem to recall reading a post or two from you 
Chrome support is terrible because they think just because you misspell something it needs flagged. 
Do you have insight into the support? Google explains clearly in the community content policy why something can be flagged as “irrelevant content”.
No I am just saying that I have experienced the same problem.