2018-04-24 12:34:16 |
Jeremy Bícha |
bug |
|
|
added bug |
2018-04-24 12:42:27 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
2018-04-24 15:04:40 |
Jeremy Bícha |
description |
gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed.
Testing Done
============
In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too).
sudo apt uninstall libnss-myhostname
Restart
Open the GNOME Settings app (gnome-control-center)
In the left sidebar, click Devices
Enter a different Device name in the block
Open a terminal and verify that the hostname has been changed.
Other Info
==========
There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277.
See also LP: #1162475
Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.)
Regression Potential
====================
I believe most distros do install libnss-myhostname as recommended by https://www.freedesktop.org/wiki/Software/systemd/hostnamed/ As long as things appear to work, maybe we can ignore that recommendation. |
gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed.
Testing Done
============
In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too).
sudo apt uninstall libnss-myhostname
Restart
Open the GNOME Settings app (gnome-control-center)
In the left sidebar, click Devices
Enter a different Device name in the block
Open a terminal and verify that the hostname has been changed.
Other Info
==========
There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277.
See also LP: #1162475
Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.)
Regression Potential
====================
To quote from the manpage:
https://manpages.debian.org/unstable/nss-resolve
"Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd-resolved is not running."
Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. |
|
2018-04-24 15:06:43 |
Jeremy Bícha |
description |
gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed.
Testing Done
============
In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too).
sudo apt uninstall libnss-myhostname
Restart
Open the GNOME Settings app (gnome-control-center)
In the left sidebar, click Devices
Enter a different Device name in the block
Open a terminal and verify that the hostname has been changed.
Other Info
==========
There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277.
See also LP: #1162475
Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.)
Regression Potential
====================
To quote from the manpage:
https://manpages.debian.org/unstable/nss-resolve
"Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd-resolved is not running."
Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. |
gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved.
Testing Done
============
In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too).
sudo apt uninstall libnss-myhostname
Restart
Open the GNOME Settings app (gnome-control-center)
In the left sidebar, click Devices
Enter a different Device name in the block
Open a terminal and verify that the hostname has been changed.
In Debian, running `ping new-hostname` fails, but it works fine in UBuntu.
Other Info
==========
There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277.
See also LP: #1162475
Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.)
Regression Potential
====================
To quote from the manpage:
https://manpages.debian.org/unstable/nss-resolve
"Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd-resolved is not running."
Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. |
|
2018-04-24 15:06:53 |
Jeremy Bícha |
description |
gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved.
Testing Done
============
In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too).
sudo apt uninstall libnss-myhostname
Restart
Open the GNOME Settings app (gnome-control-center)
In the left sidebar, click Devices
Enter a different Device name in the block
Open a terminal and verify that the hostname has been changed.
In Debian, running `ping new-hostname` fails, but it works fine in UBuntu.
Other Info
==========
There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277.
See also LP: #1162475
Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.)
Regression Potential
====================
To quote from the manpage:
https://manpages.debian.org/unstable/nss-resolve
"Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd-resolved is not running."
Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. |
gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved.
Testing Done
============
In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too).
sudo apt uninstall libnss-myhostname
Restart
Open the GNOME Settings app (gnome-control-center)
In the left sidebar, click Devices
Enter a different Device name in the block
Open a terminal and verify that the hostname has been changed.
In Debian, running `ping new-hostname` fails, but it works fine in Ubuntu.
Other Info
==========
There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277.
See also LP: #1162475
Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.)
Regression Potential
====================
To quote from the manpage:
https://manpages.debian.org/unstable/nss-resolve
"Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd-resolved is not running."
Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. |
|
2018-04-24 15:13:00 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-desktop/gnome-control-center/ubuntu |
|
2018-04-24 15:16:38 |
Jeremy Bícha |
nominated for series |
|
Ubuntu Bionic |
|
2018-04-24 15:16:38 |
Jeremy Bícha |
bug task added |
|
gnome-control-center (Ubuntu Bionic) |
|
2018-04-24 15:16:45 |
Jeremy Bícha |
gnome-control-center (Ubuntu Bionic): status |
New |
Fix Committed |
|
2018-04-24 15:30:59 |
Andreas Hasenack |
bug |
|
|
added subscriber Andreas Hasenack |
2018-04-24 17:02:48 |
Steve Langasek |
bug |
|
|
added subscriber Steve Langasek |
2018-05-11 17:13:27 |
Jeremy Bícha |
description |
gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved.
Testing Done
============
In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too).
sudo apt uninstall libnss-myhostname
Restart
Open the GNOME Settings app (gnome-control-center)
In the left sidebar, click Devices
Enter a different Device name in the block
Open a terminal and verify that the hostname has been changed.
In Debian, running `ping new-hostname` fails, but it works fine in Ubuntu.
Other Info
==========
There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277.
See also LP: #1162475
Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.)
Regression Potential
====================
To quote from the manpage:
https://manpages.debian.org/unstable/nss-resolve
"Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd-resolved is not running."
Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. |
Impact
======
gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved.
Test Case
=========
sudo apt uninstall libnss-myhostname
Restart
Open the GNOME Settings app (gnome-control-center)
In the left sidebar, click Devices
Enter a different Device name in the block (let's say new-hostname)
Open a terminal and verify that the hostname has been changed.
Then run ping new-hostname and verify that that command works in the terminal.
Other Info
==========
There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277.
See also LP: #1162475
Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.)
Regression Potential
====================
To quote from the manpage:
https://manpages.debian.org/unstable/nss-resolve
"Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd-resolved is not running."
Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. |
|
2018-05-11 19:11:51 |
Launchpad Janitor |
gnome-control-center (Ubuntu): status |
Fix Committed |
Fix Released |
|
2018-05-23 13:16:31 |
Jeremy Bícha |
gnome-control-center (Ubuntu Bionic): status |
Fix Committed |
In Progress |
|
2018-05-23 13:27:04 |
Jeremy Bícha |
gnome-control-center (Ubuntu Bionic): status |
In Progress |
Triaged |
|
2018-05-24 08:34:35 |
Jeremy Bícha |
gnome-control-center (Ubuntu Bionic): assignee |
|
Jeremy Bicha (jbicha) |
|
2018-09-04 15:46:28 |
Jeremy Bícha |
gnome-control-center (Ubuntu Bionic): status |
Triaged |
Won't Fix |
|