1541354 - "Secure Connection Failed" displayed after update&history deleted

Status: RESOLVED DUPLICATE of bug 1546361

(Firefox for Android Graveyard :: Awesomescreen, defect, P1)

Description

[Sorina Florean [:sflorean]]

Attachment: SecErrorLibraryFailure.txt

Environment:
Device: Samsung Galaxy Tab S3(Android 8.0);
Build: Nightly 68.0a1 (2019-04-02);

Steps to reproduce:

1. Install an older Nightly build (03/29);
2. Visit 4-5 pages (recommended by Pocket);
3. Go to Google Play and update Nightly;
4. Open Nightly and "Clear browsing history" from History panel;
5. From Top Sites panel, open 2-3 articles.

Expected result:
The pages are loaded without issues.

Actual result:
"Secure Connection Failed" message is displayed. Error code: SEC_ERROR_LIBRARY_FAILURE.

Notes:

• Not reproducible if History is not deleted.
• Reproducible with other pages (Google, Wikipedia).
• Going to Nightly Settings->Clear data do not solve the problem, only Clear data from Android settings.

Comment 1

[Sorina Florean [:sflorean]]

Attachment: Screenshot_2019-03-29-14-33-35.png

Comment 2

[miralobontiu]

Hi,
I was able to reproduce the issue with these steps:

1. Update Nightly from Google Play.
2. Open a page from Top Sites.

It's reproducible on OnePlus 5T (Android 9.0) on the latest Nightly 68.0a1 (2019-04-03).
It isn't reproducible on Huawei P9 Lite (Android 6.0).

Thanks!

Comment 3

[Marcia Knous [:marcia]]

Marking P1 per triage discussion.

Comment 4

[Petru-Mugurel Lingurar [:petru]]

Seems to be happening in the same conditions as bug 1541811.
(on specific devices, after updating from an older Nightly)

Comment 5

[Liz Henry (:lizzard) (relman/hg->git project)]

Is this reproducible on release?

Comment 6

[Sorina Florean [:sflorean]]

Tested on release and also on Beta build and this issue is not reproducible.

Based on comment 4: For bug 1541811 a regression range have been found, Petru do you think I should check here too?

Comment 7

[Petru-Mugurel Lingurar [:petru]]

(In reply to Sorina Florean [:sflorean] from comment #6)

Tested on release and also on Beta build and this issue is not reproducible.

Based on comment 4: For bug 1541811 a regression range have been found, Petru do you think I should check here too?

Would be great if you could confirm the same regression range.

Comment 8

[Sorina Florean [:sflorean]]

Regression window found:

• Last good build: 03/20
• First bad build: 03/21

Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=25398e555020fef80c7b2a06a0d4c667e861cd6f&tochange=b2f1edb41241d3da6ded54edf38cca1d2d08325b

Petru, the regression range is not the same as in bug 1541811.

Comment 9

[Devin Reams]

Chris, discussed during triage today. Is this perhaps something you can help us find folks to look into on the Gecko side?

Comment 10

[Chris Peterson [:cpeterson]]

(In reply to Devin Reams (dreams) from comment #9)

Chris, discussed during triage today. Is this perhaps something you can help us find folks to look into on the Gecko side?

Adding [geckoview] whiteboard tag so the GeckoView triage meeting will review this bug.

Comment 11

[Chris Peterson [:cpeterson]]

snorp is investigating these connection errors in bug 1546361.

Comment 12

[Chris Peterson [:cpeterson]]

dupe of bug 1546361