Description of problem: The Red Hat Bugzilla placeholder for tracking purposes. We can't rely on resolv.conf to have proper, working information before the portal login is complete. After discussing this with the dnssec-trigger team on the Fedora side, we should find a way to explictly make the portal helper use the dns servers that are specified in the connection configuration. Two possible approaches: 1) use an LD_PRELOAD hack like https://github.com/hadess/resolvconf-override 2) set up some minimal containerization around the portal helper and bind mount a suitable resolv.conf in place Additional info: See https://bugzilla.gnome.org/show_bug.cgi?id=752534
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
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.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'. 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 29 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.
(In reply to Tomáš Hozza from comment #0) > Two possible approaches: > > 1) use an LD_PRELOAD hack like https://github.com/hadess/resolvconf-override > 2) set up some minimal containerization around the portal helper and bind > mount a suitable resolv.conf in place I see there are old patches in the upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=752534 to implement the second approach, but that won't work nowadays because systemd-resolved exists. Instead, we could simply write a custom GResolver, which is easier. The upstream bug got closed several years ago, though, as part of a mass close. The motivation behind this change was to be able to run Unbound as a local resolver, whereas nowadays systemd-resolved won out. So I'm not sure whether it's still important or not. I'm inclined to close this downstream bug with a suggestion that the issue be reported to upstream if desired. Red Hat Bugzilla is not used for upstream development of GNOME Shell, and this component is basically a bug graveyard.