Bug 1378330

Summary:	connectivity check doesn't use NetworkManager
Product:	[Fedora] Fedora	Reporter:	Fabrice Bellet <fabrice>
Component:	firefox	Assignee:	Gecko Maintainer <gecko-bugs-nobody>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	gecko-bugs-nobody, jhorak, pjasicek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-29 11:40:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Fabrice Bellet 2016-09-22 07:21:51 UTC

Hi!

I think it's unfortunate that firefox dropped support for the DBUS NetworkManager listener a few months ago, because now the offline support of firefox is not in sync with other linux desktop applications that use NetworkManager. 

It seems that current firefox behaviour is to check for netlink events and to report that the connectivity is available when _one_ network interface is up and running. firefox should benefit from the richer NetworkManager connectivity checks, allowing to make the difference between a CONNECTED_GLOBAL and a CONNECTED_SITE situation (captive portal for example). I noticed that firefox proposes an alternative captive portal detection via a dedicated URL (http://detectportal.firefox.com/success.txt). This detection didn't work for me, and even if it worked, it would duplicate the work of the NetworkManager.

I use the network.offline-mirrors-connectivity flag set. Other configs have default values.

Comment 1 Fedora End Of Life 2017-02-28 10:20:46 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 2 Fedora End Of Life 2018-05-03 08:27:59 UTC

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 11:40:45 UTC

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.