Mailinglist Archive: opensuse-factory (269 mails)

< Previous Next >
Re: [opensuse-factory] Moving Firefox to a faster 4-week release cycle - can we get a different name for the ESR release, please?
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
  • Date: Sun, 22 Sep 2019 15:33:50 +0200
  • Message-id: <10608178.2VgTBIeAH6@xrated>
Am Mittwoch, 18. September 2019, 17:15:43 CEST schrieb Wolfgang Rosenauer:

So what could (and probably should) be discussed is if we need a Factory/TW
version of ESR. In that case with a different package name. In the mozilla
repo I used to provide a few years ago an alternative package called
firefox-esr where it was easy to switch between the different streams. This
is an option to do for Factory/Tumbleweed as well. This will give users the
choice which variant to run but on the other hand it's again a bit more
work. While not that much because I'm preparing both versions anyway in the
mozilla repo. It would just be another package name.

So overall I still think it's feasible to achieve but it will cause (at
least) a bit more work and I'm curious about opinions if we want to have an
official ESR option in Tumbleweed.

Given, that 69.0 regresses in several ways for me here, a firefox-esr version
for Factory is definitely a good idea and worth the hassle.

Firefox 68.1 fixed a 13 years old bug for me. In letters: thirteen!

https://bugzilla.mozilla.org/show_bug.cgi?id=372650

And 69.0 messed it all up again :-(. Neither desktop not window position are
remembered correctly across sessions. Given, that my usual setup consists from
about 60 windows, it's no fun at all.

And a new one: it cannot access my Fritz!Box 6490 Cable router anymore.

Beim Verbinden mit 172.16.x.y:zzzzz trat ein Fehler auf. Eine Verwendung des
Zertifikatschl├╝ssels ist f├╝r den versuchten Arbeitsschritt unpassend.
Fehlercode: SEC_ERROR_INADEQUATE_KEY_USAGE

There exist 2 ways to access this thing, either per ip address, as above, or
with a dyndns address (from selfhost.de). The FB created a certificate for the
latter, but since it is a self signed cert, one have to add an exception
anyway.

I tried to:
* restart the FB
* lower the security settings
* disable validation on OCSP server (whatever that is)
* check about:config security settings
* remove any related certs
* access a dozen other FB and Lancom routers

It's just this single FB, that is misbehaving out of the blue. 68.1 was fine.
Hrmpf.

Needless to say, apart from the usual Google obstacles (it won't remember any
passwords for unsave sites), Chromium does work with this FB of course!

I don't see any changelog entry in 69.0.1 of mozilla:Factory, that might
address this issue.

Pete


--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups