Session not restoring on ESR 128 upgrade

[Andrew J. Buehler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I am encountering what looks like (a variant of) bug #1901899 [1] on
upgrade to ESR 128. That is, I have a profile generated in a previous
Firefox (ESR) version, which has "remember tabs from last time" turned
on, and which does restore the saved session properly in that previous
version, but for which the session does not restore when ESR 128 is
launched with that profile.

That bug appears, from what I can tell in reading it, to only manifest
in cases where people have a primary password set and cancel entering it
on the first launch after upgrade. In the case I am seeing, there is not
any primary password set, and never has been, and no prompt about one is
presented - but the other symptoms of the bug still manifest, including
A: the stored session not restoring, and B: the exact same errors
(modulo slightly different line numbers, which probably correspond to
code changes in between the releases), about the user having canceled
primary-password entry, being reported in the Ctrl+Shift+J browser
console.

I was surprised to see B, because although it does suggest that I'm on
the right path with thinking that [1] may be related, as far as I can
see from reading that bug it looks like the fix for it should be
present in Firefox 126.0.1, 127.0.1, and 128.0b3 - and therefore I would
have expected the fix to already be in place by the time ESR 128
branched off.

I have filed bug #1927953 [2] about this, but it's been more than a
week, and as far as I can see it does not seem to have been
acknowledged.

I do not want to leave this sit and just hope that it will be addressed
in time, because from what I understand, there is a certificate
expiration coming up in March, and certain functionality (browser
extensions, if nothing else) in Firefox versions which do not have the
renewed certificate is expected to stop working at that point. I want to
make sure to have a sufficiently updated version deployed in my
organization before that time.


What is the appropriate path forward here?

Is there any straightforward way to find out whether the fix for [1] is
present in ESR 128? If it is not, what would it take to get it added for
the next update (or the one after)?

Is there an appropriate way to try to draw attention to [2], rather than
just sitting and hoping?


[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1901899

[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1927953

- --
Andrew J. Buehler
-----BEGIN PGP SIGNATURE-----

iQJJBAEBCgAzFiEEJCOqsZEc2qVC44pUBKk1jTQoMmsFAmcspwwVHHdhbmRlcmVy
QGZhc3RtYWlsLmZtAAoJEASpNY00KDJrdH4P/itepGpGrpy+VjW44K57l9WuhLgy
X+z3Ba23i6yqbw+3jT6EqL6iFOSZpM8eV2djF1I2B7W0kW+vBRkQjMCiCq2kC67j
GOkUUCCqailytKQcn2zOewwZGo+K83GZmnmZfoNahGFrdmkCIlAdFX56DN9axhjf
3rUgLBbONjpDJhaUOLEMQ9m7GnR8tdpesWhDqypevfY3PNWwu8Mq6yU9WkslQz6V
JidDYsy9iStDPIMpkiXDfCt2gAq9qOHsHTLcQ5NSVamFuKm8eQbx8KCcTCo+8QQB
zsVL+IGpo1tn+f7F3+p5RyYehygM7ky+OXeFzVDzEp4vLsaQNDbqDk6Aeam68DEC
P48qlBoN5FMSUmqoZAxcr2We9fz0FxSNuMr0ng/0FvmQ3sraSZ/g5HpwaHyy/1s8
KGVqWSVuNCqMkqq0Xyjd+7XeNuyFLn26G5ttPE8G1nEu14G0Y6g/OeEF9g0+g3qc
rwQDyQdgmcenB1LpKAhFv1zayjABwu4OzJL9tGZqzRUwQGUr4r/7JaRvKmL0XbJ5
iZLofJE4sHEXxkeyW584qcSBRabIxLdR7R3gUDgLhhQ2mYoLR6tr8K1oBXEY4Nmn
VI34Q2AwvaKy3+AvRp8VR6MY3NMUuVZEVZN6cYruvzjskqrz/F/DRzCK60dxZFZP
Vspl840fIkNjzrZ4
=8vJQ
-----END PGP SIGNATURE-----

[Mike Kaply]

The fix for 1901899 is definitely in the ESR.

The new bug should get triaged soon as part of our normal triage process, so someone will look at it.

Mike

--
You received this message because you are subscribed to the Google Groups "enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise+...@mozilla.org.
To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/672CA718.4090605%40fastmail.fm.