Network Connections window says I've "Never" used the wired connection I'm using right now

Bug #447067 reported by Matthew Paul Thomas
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: network-manager

1. Connect to a wired network.
2. Secondary-click on the network icon and choose "Edit Connections...".

What happens: The "Wired" tab reports that the wired connection you're using was "Last used" "Never".
What should happen: The window should show that you're using the connection right now.

ProblemType: Bug
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Fri Oct 9 10:19:54 2009
DistroRelease: Ubuntu 9.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 10.45.43.0/24 dev eth2 proto kernel scope link src 10.45.43.110 metric 1
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
 default via 10.45.43.1 dev eth2 proto static
NonfreeKernelModules: wl
Package: network-manager 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2
ProcEnviron:
 LANGUAGE=en_NZ.UTF-8
 PATH=(custom, user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
RfKill:

SourcePackage: network-manager
Uname: Linux 2.6.31-12-generic i686
WpaSupplicantLog:

CVE References

Revision history for this message
Matthew Paul Thomas (mpt) wrote :
Revision history for this message
Jeff Lane  (bladernr) wrote :

I have seen the same thing since the beginning of the Lucid cycle... network-manager correctly reports the "Last Used" time for my wireless device, but for the copper enet card, nothing at all.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Confirming, setting priority to Low.

I see it happening on my system as well, and it seems (from last time I looked at it briefly) like it was the timestamp for last use being in the past or something, causing the label do display "Never", for a wired connection currently in use.

Same applies to a currently-used wifi connection: mine currently displays "4 minutes ago", even though it is currently connected.

Changed in network-manager (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager - 0.8.2-0ubuntu1

---------------
network-manager (0.8.2-0ubuntu1) natty; urgency=low

  * new upstream release 0.8.2
    - update timestamp in active system connections every 5 mins
    - ignore authorization for sleep/wake requests (but restrict to root)
    - add timestamp to default auto wired connections (LP: #447067)
    - don't crash if for some reason HW addresses aren't available (bgo #630534)
    - ensure Enabled state is preserved regardless of rfkill (LP: #387345)
    - add dhcp4-change and dhcp6-change events (bgo #563654)
    - validate Enable/Disable WiFi and WWAN requests
    - handle VPN service installation/removal dynamically (LP: #458595)
    - let plugins forbid VPN connections from getting the default route
      (LP: #598357)
    - work around dbus-glib property access bug (CVE-2010-1172)
    - ensure dhcp_manager exists before trying to unref it (bgo #626610)
  * drop dhcp3 support patch, it was applied upstream.
    - remove debian/patches/99-support-dhcp3.patch
    - update debian/patches/series
  * drop cherry-picked patches to /etc/hosts handling, their changes are
    included in the source tarball:
    - remove debian/patches/lp659872_dont_overwite_hosts_aliases_ee9ce60.patch
    - remove debian/patches/lp632896_cleanup_etc_hosts.patch
    - update debian/patches/series
  * Properly document workflow for working on NM packaging.
    - add debian/README.source
  * Slight change to GET_SOURCE script. Looks like we were looking for the
    "orig" keyword in the wrong variable.
    - update debian/rules
  * Fix typo in README.source
    - update debian/README.source
  * network-manager Breaks: dhcp3-client (<< 4.1.1-P1-11) to provide seemless
    upgrades to isc-dhcp 4 and avoid unnecessary compatibility issues
  * switch Build-Depends from dhcp3-client to isc-dhcp-client >= 4.1.1 to make
    sure we don't build with an old version of DHCP.
  * libnm-glib2 also Breaks: dhcp3-client (<< 4.1.1-P1-11)
    - debian/control
  * libnm-util1 Breaks: dhcp3-client (<< 4.1.1-P1-11) as well
    - debian/control
  * Patch various files to support building with kernel headers 2.6.36 and
    newer (otherwise it conflicts with libc headers for interface structures)
    - debian/patches/do-not-include-netif.patch
    - debian/patches/series
 -- Mathieu Trudel-Lapierre <email address hidden> Tue, 09 Nov 2010 13:01:48 -0500

Changed in network-manager (Ubuntu):
status: Confirmed → 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.