Public bug reported:

Binary package hint: network-manager

In the office I have a docking station for my Dell Latitude E-5500 laptop with 
LAN cable connection on eth0.
In the office we also have a WLAN which I use when I take the laptop to a 
meeting room.
I was used to set both (LAN eth0 and WLAN "MayWifi") to autoconnect.

Then recently I had the problem that on login the WLAN connection was
considered as the somewhat "main" connection which leads to the problem
that I do not have access to particular resources without first
establishing a VPN connection. This is a different story (Bug 629284)
but the reason I unchecked the autoconnect option for the WLAN
connection.

So, but now when I do not set the WLAN to autoconnect, I also don't get
the LAN autoconnected although available.

In the attached screenshot(s) you can also see that the wired LAN
connection is showing "never" in the "Last Used" column which is
definitely wrong as I use it on a daily basis.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Thu Nov  4 08:52:56 2010
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
IpRoute:
 172.30.47.0/24 dev wlan0  proto kernel  scope link  src 172.30.47.103  metric 
2 
 172.30.48.0/22 dev eth0  proto kernel  scope link  src 172.30.50.190  metric 1 
 169.254.0.0/16 dev eth0  scope link  metric 1000 
 default via 172.30.50.1 dev eth0  proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
 LC_TIME=en_DK.utf8
 LANGUAGE=en
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: network-manager

** Affects: network-manager (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 lucid

-- 
Autoconnect to wired not working correctly when disabled for WLAN
https://bugs.launchpad.net/bugs/670809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to