desktop-packages team mailing list archive

[markba <846320@xxxxxxxxxxxxxxxxxx>]

> This should be been mostly fixed in Oneiric now, with the latest revision of NetworkManager and nm-applet.
I've updated, but having the exact same issue.

> To clarify, I guess what you mean was that wired would be connected but then no traffic at all would pass unless the connection ?> was re-established?
Correct.

> apport-collect 846320
This gives me the following error (I'm using chromium):
/usr/lib/chromium-browser/chromium-browser: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

> ip route list
default via 192.168.0.1 dev eth0  proto static 
192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.101 
192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.100

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/846320

Title:
  Wired connection does not take preference over wireless (regression
  11.10)

Status in “network-manager” package in Ubuntu:
  Incomplete

Bug description:
  When there is an active wireless connection, and the wired connector
  is connected, network manager is responding by notifying that the
  wired connection is made and the icon changes from wireless to wired.
  In ifconfig, a IP-address is bound to ethX.

  But when trying to do any file operations (or other things), it comes
  clear that the wired connection is not used, despite the icon and
  notification. The wired connection can only be activated when the
  wireless connecttion is forced into disconnect.

  But then, the wired connection is not becoming active, only after re-
  connecting the wired connection. Maybe the last problem is related to
  this bug mentioned. If not, a separate bug should be filed.

  When pulling the plug from, the wired connection, the wireless
  connection does not becomes active automatically, like it did prior to
  11.10. You have to force the wireless connection to get connected
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/846320/+subscriptions