GNOME Bugzilla – Bug 735911
Destroy hotspot connection when switching off
Last modified: 2021-06-09 16:08:41 UTC
So that it's not re-enabled by error, and we can change the name of the hotspot without problems, if the computer's name changed.
Created attachment 285550 [details] [review] network: destroy hotspot when switching off This works, but I'm marking it as obsolete since we really do not want to do this unless we can find a way to use the same security key each time the hotspot is created.
(In reply to comment #1) > Created an attachment (id=285550) [details] [review] > network: destroy hotspot when switching off > > This works, but I'm marking it as obsolete since we really do not want to do > this unless we can find a way to use the same security key each time the > hotspot is created. Not being able to change the settings from the original is a problem. We should probably offer a default password but the ability to change it in the "Turn on Hotspot" dialogue. It would allow us to change it, and keep it around as well. Is it security sensitive? Should we save it in the keyring?
In the meanwhile, I'd be fine with not allow a hotspot password to be chosen but to keep it around for the next run.
(In reply to comment #3) > In the meanwhile, I'd be fine with not allow a hotspot password to be chosen > but to keep it around for the next run. And that would allow us to fix this bug while not changing UI, which means we could land it in 3.14.
(In reply to comment #2) > Is it security sensitive? Should we save it in the keyring? Of course!
Review of attachment 285550 [details] [review]: ::: panels/network/net-device-wifi.c @@ +1180,3 @@ + gpointer user_data) +{ + if (error != NULL) { Is it correct that we don't free GErrors passed to callbacks? Or is the code I copied this from (the function really_forgotten lower in this file) wrong?
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new bug report at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/ Thank you for your understanding and your help.