I experience the same issue than the OP on current testing (jessie) using systemd.

In my case, this occurs when selecting a "Wired connection" in the Network-Manager applet. I'm using network-manager 0.9.10.0-3 and network-manager-gnome (for the nm-applet binary)
0.9.10.0-2

Connecting to a wireless network works fine.

Here's the output of systemctl status.

root@mazer:~# systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled)
   Active: active (running) since Fri 2014-10-10 18:14:35 CEST; 2 days ago
 Main PID: 8721 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           ├─ 8721 /usr/sbin/NetworkManager --no-daemon
└─30108 /sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-ee9a7...

Oct 13 12:39:43 mazer NetworkManager[8721]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Oct 13 12:39:43 mazer NetworkManager[8721]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Oct 13 12:39:43 mazer NetworkManager[8721]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Oct 13 12:39:43 mazer NetworkManager[8721]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Oct 13 12:39:43 mazer NetworkManager[8721]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0] Oct 13 12:39:43 mazer NetworkManager[8721]: <info> (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Oct 13 12:39:43 mazer NetworkManager[8721]: <warn> Activation (eth0) failed for connection 'eth0' Oct 13 12:39:43 mazer NetworkManager[8721]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Oct 13 12:39:43 mazer NetworkManager[8721]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 13 12:39:43 mazer NetworkManager[8721]: <info> (eth0): deactivating device (reason 'none') [0]


The issue seems to be a configuration issue though. Editing the connections in the applet and setting the method in the "IPv4 Settings" for the wired connection to "Automatic (DHCP)" worked for me. It was initially set to "Ignore".

best regards,
David


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to