Red Hat Bugzilla – Bug 1480517
NetworkManager resets wifi hotspot SSID name to hostname
Last modified: 2018-05-29 08:54:18 EDT
Description of problem:
NetworkManager allows to create wifi hotspots which have a name.
The hotspot SSID name can be editted to some arbitary string; however if you change the SSID and save it (via /etc/sysconfig/network-scripts/ifcfg-Hotspot or nm-connection-editor), the next time you start your wifi hotspot, the hotspot name reverts back to the hostname.
Even edit, save, restarting networkmanager, start wifi hotspot has same bug behaviour.
Running under cinnamon desktop and enabling using NetworkManager applet
This used to work as expected in F24.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. From X desktop, goto NetworkManager -> Network Connections
location "Hotspot" under "Wifi" subsection and "Edit"
2. Change SSID name and save
3. vefify name change is persisted /etc/sysconfig/network-scripts/ifcfg-Hotspot
4. goto NetwokrManager -> NetworkSettings
5. click "Use as Hotspot.." and "Turn On"
5. the "Network Name" in dialog shows that the SSID has been reverted to the hostname
Hotspot SSID changed to hostname
hotspot SSID to be honoured when hotspot is enabled and no overwriting/updating of /etc/sysconfig/network-scripts/ifcfg-Hotspot
Worked under Fedora 24
The "Network Settings" dialog is part of cinnamon control center and it resets the SSID to the system hostname every time the hotspot functionality is activated. Updating the bug component.
Does gnome-control-center do the same?, fedora cinnamon-control-center was recently rebased to 3.24.3
Looking at the gnome commits it is the intended behaviour.
(In reply to leigh scott from comment #2)
> Does gnome-control-center do the same?, fedora cinnamon-control-center was
> recently rebased to 3.24.3
> Looking at the gnome commits it is the intended behaviour.
network-manager-applet (nm-connection-editor) is a gnome component so it shouldn't try to set hotspot name if gnome-control-center doesn't support it.
After a discussion with Leigh about the reported bug and the fact it is intended behaviour from "Network Settings" in GNOME Control Center to reset the name of the hotspot to the machine's hostname on activation, I think GNOME should not ship tools that are contradicting and conflicting in their intended functionality.
(In reply to Björn "besser82" Esser from comment #4)
> After a discussion with Leigh about the reported bug and the fact it is
> intended behaviour from "Network Settings" in GNOME Control Center to reset
> the name of the hotspot to the machine's hostname on activation, I think
> GNOME should not ship tools that are contradicting and conflicting in their
> intended functionality.
What is contradicting? nm-connection-editor (as the name says) is a
editor of NM profiles (connections) and the "hotspot" generated by
gnome-control-center is a normal wi-fi connection with mode=AP. I
don't think that nm-c-e should prevent users from editing connections
just because other tools created them. Also, how nm-c-e should detect
that the connection was created by control-center, by the name? (if
so, if users create a connection named "Hotspot", they won't be able
to edit the connection again).
In my opinion when users activate the hotspot fuctionality,
control-center should either (1) reuse the existing profile if it is
compatible (right SSID, device, ...) or (2) create a new one.
(In reply to Beniamino Galvani from comment #5)
> In my opinion when users activate the hotspot fuctionality,
> control-center should either (1) reuse the existing profile if it is
> compatible (right SSID, device, ...) or (2) create a new one.
The better option would be, if nm-c-e would warn a user about g-c-c might clobber any customization made to a profile named "Hotspot" or if a such named profile is created by the user…
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'
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.