IP Address not displayed for wifi access points

Bug #1579825 reported by Bill Filler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
High
Unassigned
indicator-network (Ubuntu)
Invalid
High
Pete Woods
network-manager (Ubuntu)
Invalid
High
Unassigned
ubuntu-system-settings (Ubuntu)
Fix Released
High
Ken VanDine

Bug Description

latest rc-proposed build 319

Open system settings
expand the connected access point by pressing right arrow

expected results:
ip address is displayed

actual results:
ip address is not displayed, just a label "IP Address" with no value

Related branches

Revision history for this message
Bill Filler (bfiller) wrote :

nothing relevant in ubuntu-system-settings log or syslog

tags: added: regression-proposed
Changed in ubuntu-system-settings (Ubuntu):
importance: Undecided → High
assignee: nobody → Ken VanDine (ken-vandine)
Changed in indicator-network (Ubuntu):
importance: Undecided → High
Changed in network-manager (Ubuntu):
importance: Undecided → High
Changed in indicator-network (Ubuntu):
assignee: nobody → Pete Woods (pete-woods)
Revision history for this message
Bill Filler (bfiller) wrote :

this is on Arale

Revision history for this message
Tony Espy (awe) wrote :

I see this on mako running stable / #30 plus the a test version of NetworkManager 1.1.93 that I'm using for the VPN bug #1579222. When I go to the access point details page in system settings, I also see the following message logged to the upstart log file application-legacy-ubuntu-system-settings.log:

2016-05-09 12:36:50,542 - WARNING - Got invalid serialized mime data. Ignoring it.

When I go back to the main WiFi settings page, I also alot of the following log messages:

2016-05-09 12:34:24,080 - WARNING - file:///usr/share/ubuntu/settings/system/qml-plugins/wifi/PageComponent.qml:80: TypeError: Cannot read property of null

Revision history for this message
Bill Filler (bfiller) wrote :

This is in the log for uss when trying to expand the AP on the UI.

2016-05-09 12:40:40,395 - WARNING - Got invalid serialized mime data. Ignoring it.

Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

That log entry [1] is not related to the WiFi panel. I think it's copy/paste something complaining.

[1] WARNING - Got invalid serialized mime data. Ignoring it.

Revision history for this message
Ken VanDine (ken-vandine) wrote :

On my turbo the Ip4Address = 0. On my desktop it's not 0, sounds like a bug in network-manager to me.

      interface org.freedesktop.NetworkManager.Device {
        methods:
          Reapply(in a{sa{sv}} connection,
                  in t version_id,
                  in u flags);
          GetAppliedConnection(in u flags,
                               out a{sa{sv}} connection,
                               out t version_id);
          Disconnect();
          Delete();
        signals:
          StateChanged(u new_state,
                       u old_state,
                       u reason);
        properties:
          readonly s Udi = '/sys/devices/platform/mtk-msdc.3/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/net/wlan0';
          readonly s Interface = 'wlan0';
          readonly s IpInterface = 'wlan0';
          readonly s Driver = 'mtk_sdio_client';
          readonly s DriverVersion = '3.10.35+';
          readonly s FirmwareVersion = 'N/A';
          readonly u Capabilities = 1;
          readonly u Ip4Address = 0;
          readonly u State = 100;
          readonly (uu) StateReason = (100, 0);
          readonly o ActiveConnection = '/org/freedesktop/NetworkManager/ActiveConnection/0';
          readonly o Ip4Config = '/org/freedesktop/NetworkManager/IP4Config/7';
          readonly o Dhcp4Config = '/org/freedesktop/NetworkManager/DHCP4Config/0';
          readonly o Ip6Config = '/org/freedesktop/NetworkManager/IP6Config/7';
          readonly o Dhcp6Config = '/';
          readwrite b Managed = true;
          readwrite b Autoconnect = true;
          readonly b FirmwareMissing = false;
          readonly b NmPluginMissing = false;
          readonly u DeviceType = 2;
          readonly ao AvailableConnections = ['/org/freedesktop/NetworkManager/Settings/9'];
          readonly s PhysicalPortId = '';
          readonly u Mtu = 0;
          readonly u Metered = 4;
          readonly aa{sv} LldpNeighbors = [];
          readonly b Real = true;
      };

Revision history for this message
Tony Espy (awe) wrote :

@Ken

I see the same thing on krillin running rc-proposed / #320.

That said, looks like we made a poor choice of properties to use as 'IP4Address' was marked as deprecated as far back as NM 0.9:

https://developer.gnome.org/NetworkManager/0.9/spec.html#org.freedesktop.NetworkManager.Device

Looks that choice has now bitten us, and the property is no longer being populated on purpose.

tags: added: lt-blocker
Revision history for this message
Pete Woods (pete-woods) wrote :

indicator-network is not involved in reading the IP address of connections.

Changed in indicator-network (Ubuntu):
status: New → Invalid
Changed in canonical-devices-system-image:
importance: Undecided → High
status: New → Confirmed
status: Confirmed → In Progress
milestone: none → 11
Changed in canonical-devices-system-image:
status: In Progress → Fix Committed
Changed in ubuntu-system-settings (Ubuntu):
status: New → Fix Released
Changed in network-manager (Ubuntu):
status: New → Invalid
Changed in canonical-devices-system-image:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.