After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 692921 - All networks but the connected one are now called "novo"
All networks but the connected one are now called "novo"
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Network
3.7.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-01-31 08:57 UTC by Bastien Nocera
Modified: 2013-02-12 06:57 UTC
See Also:
GNOME target: 3.8
GNOME version: ---


Attachments
screenshot (33.77 KB, image/png)
2013-01-31 08:57 UTC, Bastien Nocera
  Details
network: Be more careful in ignoring shared connection (1.27 KB, patch)
2013-02-12 03:11 UTC, Matthias Clasen
committed Details | Review

Description Bastien Nocera 2013-01-31 08:57:58 UTC
Created attachment 234890 [details]
screenshot

I setup a hotspot (on a machine that doesn't support Ad-Hoc or AP mode), and after disabling it, all my networks are called "novo" (the name of my machine), except the connect one.
Comment 1 Dan Winship 2013-02-01 17:25:40 UTC
can't reproduce... but then, my card supports both ad-hoc and ap.

Presumably if you quit and restart, the names get fixed? (ie, the mixup is purely control-center-internal, not inside NM)
Comment 2 Bastien Nocera 2013-02-02 23:40:54 UTC
Quit and restart what? gnome-control-center? Then no, absolutely not, it shows the correct names for the networks for a short period of time (0.5 secs) and then all the networks except the connected one gets changed to "novo". 100% reproduceable on my home machine.
Comment 3 Matthias Clasen 2013-02-06 00:30:15 UTC
odd; not happening here either
Comment 4 Bastien Nocera 2013-02-11 13:55:18 UTC
This is the output for the hotspot connection. I can still reproduce the problem at will with 3.7.5.

As the output of "nm-tool" or gnome-shell's network menu doesn't have that problem, I'm guessing that a match in the loop going through all the APs is associating the "Hotspot" connection to all the connections.

$ nmcli c list uuid 058ef731-0a99-4f91-8dfe-05aab6daf44c
Warning: nmcli (0.9.7.995) and NetworkManager (0.9.7.0) versions don't match. Use --nocheck to suppress the warning.
connection.id:                          Hotspot
connection.uuid:                        058ef731-0a99-4f91-8dfe-05aab6daf44c
connection.type:                        802-11-wireless
connection.autoconnect:                 no
connection.timestamp:                   0
connection.read-only:                   no
connection.permissions:                 
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.secondaries:                 
802-11-wireless.ssid:                   'novo'
802-11-wireless.mode:                   adhoc
802-11-wireless.band:                   --
802-11-wireless.channel:                0
802-11-wireless.bssid:                  --
802-11-wireless.rate:                   0
802-11-wireless.tx-power:               0
802-11-wireless.mac-address:            00:26:82:8C:13:2C
802-11-wireless.cloned-mac-address:     --
802-11-wireless.mac-address-blacklist:  
802-11-wireless.mtu:                    auto
802-11-wireless.seen-bssids:            
802-11-wireless.security:               802-11-wireless-security
802-11-wireless.hidden:                 no
802-11-wireless-security.key-mgmt:      none
802-11-wireless-security.wep-tx-keyidx: 0
802-11-wireless-security.auth-alg:      --
802-11-wireless-security.proto:         
802-11-wireless-security.pairwise:      
802-11-wireless-security.group:         
802-11-wireless-security.leap-username: --
802-11-wireless-security.wep-key0:      --
802-11-wireless-security.wep-key1:      --
802-11-wireless-security.wep-key2:      --
802-11-wireless-security.wep-key3:      --
802-11-wireless-security.wep-key-flags: 0 (none)
802-11-wireless-security.wep-key-type:  0 (unknown)
802-11-wireless-security.psk:           --
802-11-wireless-security.psk-flags:     0 (none)
802-11-wireless-security.leap-password: --
802-11-wireless-security.leap-password-flags:0 (none)
ipv4.method:                            shared
ipv4.dns:                               
ipv4.dns-search:                        
ipv4.addresses:                         
ipv4.routes:                            
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv6.method:                            auto
ipv6.dns:                               
ipv6.dns-search:                        
ipv6.addresses:                         
ipv6.routes:                            
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.ip6-privacy:                       -1 (unknown)
ipv6.dhcp-hostname:                     --
Comment 5 Dan Winship 2013-02-11 14:55:00 UTC
ok, let me make sure I've got this:

  - You create a hotspot, which doesn't actually work, and then
    deactivate it

  - After deactivating it, all wifi networks in the list except for
    the active one show up as "novo"

      - In your screenshot, all of the networks show up with the
        gear icon as well, indicating that it thinks you have
        connected to them before. Is that correct? Or should some
        of the networks in that list be not-previously-connected-to?

  - If you quit gnome-control-center and restart it at this point,
    the network list comes up correctly at first, but then quickly
    switches back to being broken (without you touching anything).

      - Does the problem go away after rebooting / restarting NM, or
        does it stay broken forever?
Comment 6 Bastien Nocera 2013-02-11 15:07:45 UTC
(In reply to comment #5)
> ok, let me make sure I've got this:
> 
>   - You create a hotspot, which doesn't actually work, and then
>     deactivate it

Correct.

>   - After deactivating it, all wifi networks in the list except for
>     the active one show up as "novo"

Yes.

>       - In your screenshot, all of the networks show up with the
>         gear icon as well, indicating that it thinks you have
>         connected to them before. Is that correct? Or should some
>         of the networks in that list be not-previously-connected-to?

None of the ones named "novo" should have the gear icon, because I never connected to any of them.

>   - If you quit gnome-control-center and restart it at this point,
>     the network list comes up correctly at first, but then quickly
>     switches back to being broken (without you touching anything).

Correct.

>       - Does the problem go away after rebooting / restarting NM, or
>         does it stay broken forever?

It doesn't go away after rebooting. It's a purely UI issue, as gnome-control-center 3.6.x doesn't show the problem.
Comment 7 Matthias Clasen 2013-02-12 03:11:33 UTC
Created attachment 235762 [details] [review]
network: Be more careful in ignoring shared connection

It was possible for us to accidentally use the shared
connection for naming all access points.
Comment 8 Matthias Clasen 2013-02-12 03:12:51 UTC
Try this patch - the loop there is a bit hairy. We rely on connection being reset in all cases but the one where we break because we've found the right connection.
Comment 9 Bastien Nocera 2013-02-12 06:57:26 UTC
That seems to have fixed it.

Attachment 235762 [details] pushed as a0de63d - network: Be more careful in ignoring shared connection