Unable to clear wired disconnected status without restarting NM.

Bug #456362 reported by Noel J. Bergman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Undecided
Noel J. Bergman

Bug Description

Binary package hint: network-manager

The full scenario is that after suspending when using a wired connection, resuming when it was not available, suspending again, and resuming with a wired connection available I found that the wired connection was disabled by NM 0.8. Plugging and unplugging the connection was not able to reset the status based on the carrier change, nor was there any way I could find to do it from the nm-applet.

I tried enabling and disabling networking in nm-applet to see if that would reset the status from disconnected, but it did not. Finally, I restarted the network manager service, and the connection established.

ii network-manager 0.8~a~git.20091016t185227.8d65515-0ubuntu2~nmt1 network management framework daemon
ii network-manager-gnome 0.8~a~git.20091019t002522.b905cc2-0ubuntu2~nmt1 network management framework (GNOME frontend

daemon log is attached.

Revision history for this message
Noel J. Bergman (noeljb) wrote :
Noel J. Bergman (noeljb)
Changed in network-manager (Ubuntu):
assignee: nobody → Noel J. Bergman (noeljb)
Revision history for this message
Tony Espy (awe) wrote :

I just tried this on my macbook, and it worked OK for me.

1. Connected to Wired --> suspend
2. Unplug Ethernet -> resume

system auto-connects to our office AP

3. Suspend again
4. Plug in Ethernet -> resume

NM connects to both Wired & Wireless

I'm running Karmic + latest updates:

network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Tony, thanks for looking. I haven't been able to reproduce this but the one time, either. Dan and I were looking over the logs ... might have been a troublesome DHCP server in the mix.

Regardless, there is new code upstream to clear the invalid status on connections when we sleep: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=4b2c810b1ba1f4ac6384bde3c749c94467b2886b

Just to make note of it: the code intentionally does not clear the status based on carrier state change. That is on purpose and by intent, even if there is some debate.

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

Thanks Joel. I marked the bug as FixCommitted as it's landed upstream.

Changed in network-manager (Ubuntu):
status: New → Incomplete
status: Incomplete → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.5 KiB)

This bug was fixed in the package network-manager - 0.8~rc2-0ubuntu1

---------------
network-manager (0.8~rc2-0ubuntu1) lucid; urgency=low

  * upstream snapshot 2009-11-12 01:22:59 (GMT)
    + 420ea0220c29a45337e239e4c53250a6989160a3
    - ppp: allow update of ppp secrets in all ACTIVATING stages (LP: #432205)
    - core: validate pidfile and quit early if NM is already running (rh #517362)
    - core: preserve wifi and networking enabled/disabled states (bgo #582447)
    - libnm-util: don't allow blank or NULL VPN items or secrets (rh #532084)

  * upstream 0.8-rc1 release
    - libnm-util: client cert shouldn't be required to set priv key (bgo #585570)
    - wifi: poll rfkill status for ipw2x00 devices
    - ppp: increase PPPoE pppd timeout to 30 seconds (debug)
    - wifi: don't allow scan requests when associating
    - wifi: ensure wifi devices are enabled on wakeup if not rfkilled
    - libnm-util: handle PEM files without ending newline (rh #507315)
    - system-settings: cache secrets to protect against nm_connection_clear_secrets
    - dnsmasq: VPN DNS fixes (LP #389006)
    - system-settings: fix crash when deleting wired connections
    - modem: subsitute known-good nameservers if PPP doesn't return any (LP: #434477)
    - core: clear invalid tag on failed connections when sleeping (LP: #456362)
    - wwan: unable to bring up mobile-broadband system connection (LP: #483773)
    - 8021x: fixed problems with invalid connection / client-certs (LP: #245184)

  * upstream 0.8-rc2 release
    - po: update italian translation (bgo #595673)
    - core: fix error when parsing state file for WirelessEnabled fails
    - libnm-util: fix potential crash when encrypting fails
    - modem: ensure deactivation on disable only happens on disable
    - modem: ensure device is deactivated if the modem is disabled
      underneath NM
    - modem: enable modem before connecting if required
    - libnm-glib: add WWAN enable/disable support
    - manager: add WWAN enable/disable support
    - modem: proxy the ModemManager Enabled property
    - manager: generalize rfkill operations
    - core: add statefile support for WWAN devices
    - udev: add support for other types of rfkill switches
    - core: generalize interface for enabling/disabling devices
    - modem: fix enable/disable/disconnect flow
    - system-settings: Fix using hostname from DHCP
    - libnm-util: client certificate should not be required to set
      private key (bgo #585570)

  [ Alexander Sack <email address hidden> ]
  * allow daily builds to be filed against ubuntu bug system;
    to allow this we add report['CrashDB'] = 'ubuntu' to the apport
    hook
    - update debian/source_network-manager.py
  * attach list of system-connection configuration files in apport hook
    - update debian/source_network-manager.py

  [ Mathieu Trudel <email address hidden> ]
  * updated pkcs11 smartcard patch
    - updated debian/patches/lp120363_smartcard_pkcs11.patch
  * updated signals patch for apport
    - updated debian/patches/70_lp145653_no_sigaction_for_crashes.patch
  * add new nm_setting_olpc_mesh_new symbol to libnm-util1.symbols
    - update debian/libnm-util1.symbols
  * add new nm_cl...

Read more...

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