** Summary changed: - NM fails automatically to configure a wired interface that is connected at run time + NM fails automatically to configure a wired interface that is connected after logging in
-- 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/660023 Title: NM fails automatically to configure a wired interface that is connected after logging in Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager on Meerkat the wired connection works if connected on boot, but if connected after logging in, the wired interface is ignored. No network lights, Lenovo T61, both i386 and x86_64. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Wed Oct 13 08:58:23 2010 Gconf: IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928) IpRoute: 192.168.60.0/24 dev eth0 proto kernel scope link src 192.168.60.51 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.60.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: yes SourcePackage: network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/660023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
