FS#44075 - [networkmanager] 1.0.0-2 fails to find dhcp client

Attached to Project: Arch Linux
Opened by James Crompton (DonJaime) - Friday, 06 March 2015, 19:41 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 08 March 2015, 05:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After package upgrade to version 1.0.0-2 Network Manager fails to get an IP address via DHCP

Additional info:
# journalctl -b | grep dhcp
Mar 06 20:09:20 viajero NetworkManager[386]: <warn> No usable DHCP client found ('dhcpcd' support not found or not enabled.)! DHCP configurations will fail.
Mar 06 20:09:23 viajero NetworkManager[386]: <info> (wlp2s3): device state change: ip-config -> failed (reason 'dhcp-start-failed') [70 120 15]
Mar 06 20:09:26 viajero NetworkManager[386]: <info> (wlp2s3): device state change: ip-config -> failed (reason 'dhcp-start-failed') [70 120 15]
...etc...

Downgrade to version 1.0.0-1 and restarting NetworkManager fixes the problem.

Steps to reproduce:
pacman -Sy networkmanager
systemctl restart NetworkManager
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 08 March 2015, 05:03 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Saturday, 07 March 2015, 03:01 GMT
dhcpcd support has been disabled. If you have something in your conf file forcing it to use dhcpcd, remove it.
Comment by James Crompton (DonJaime) - Saturday, 07 March 2015, 17:50 GMT
Ah yes, there it is: https://wiki.archlinux.org/index.php/NetworkManager#Configure_NetworkManager_to_use_a_specific_DHCP_client

Might be worth an announcement on the front page (something important breaking under some circumstances?).
Comment by Doug Newgard (Scimmia) - Sunday, 08 March 2015, 05:02 GMT
It's something you had to configure yourself, so it's your responsibility.

Loading...