Bug 1376928 - wicd needs to properly handle the /etc/resolv.conf symlink from systemd-tmpfiles-setup
Summary: wicd needs to properly handle the /etc/resolv.conf symlink from systemd-tmpfi...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wicd
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-16 20:38 UTC by Jerry Amundson
Modified: 2016-12-20 21:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 21:34:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1264364 0 unspecified CLOSED During installation there is no dns-server set: systemd-tmpfiles creates /etc/resolv.conf as a broken symlink, NetworkMa... 2023-09-14 03:05:31 UTC
Red Hat Bugzilla 1313085 0 unspecified CLOSED Name resolution fails (resolv.conf is a broken systemd symlink) on livemedia-creator live image 2021-02-22 00:41:40 UTC

Internal Links: 1264364 1313085

Description Jerry Amundson 2016-09-16 20:38:53 UTC
Description of problem:
wicd needs to properly handle the /etc/resolv.conf symlink from systemd-tmpfiles-setup

Version-Release number of selected component (if applicable):
wicd-1.7.3-2

How reproducible:
Always with these steps

Steps to Reproduce:
1. Boot with no network - no wired connection, and no auto-connecting wireless
2. Note /etc/resolv.conf, created by systemd-tmpfiles-setup.service, points to a non-existent file
3. Disable NetworkManager, enable wicd

Actual results:
No DNS resolution.

Expected results:
DNS resolution.

Additional info:

Comment 1 Fedora End Of Life 2016-11-25 09:35:25 UTC
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.

Comment 2 Fedora End Of Life 2016-12-20 21:34:56 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.


Note You need to log in before you can comment on or make changes to this bug.