FS#44878 - [networkmanager] 1.0.2 requires openresolv to establish DNS

Attached to Project: Arch Linux
Opened by Pedro Martinez-Julia (pedromj) - Wednesday, 06 May 2015, 17:08 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 06 May 2015, 19:25 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
New release 1.0.2 requires openresolv as, for some reason, NM tries to call "resolvconf" instead of writing "resolv.conf" by itself.

Steps to reproduce:
Uninstall resolvconf, clear /etc/resolv.conf, try to connect to a network, see /etc/resolv.conf, and check the warnings in journalctl.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Wednesday, 06 May 2015, 19:25 GMT
Reason for closing:  Fixed
Additional comments about closing:  networkmanager 1.0.2-3
Comment by Doug Newgard (Scimmia) - Wednesday, 06 May 2015, 18:12 GMT
Related to http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=bg/resolv-conf-bgo747821&id=e573977b808409ccb26562ca8536d46be701f833

By configuring NM with --with-resolvconf=/usr/bin/resolvconf, it seems that becomes the default.
Comment by Jan Alexander Steffens (heftig) - Wednesday, 06 May 2015, 18:21 GMT
Hm, seems it does not automatically fall back anymore. Gonna disable resolvconf by default.
Comment by Jan Alexander Steffens (heftig) - Wednesday, 06 May 2015, 18:40 GMT
Egh, never mind, was working with information about NM master, not 1.0.2.
Comment by Doug Newgard (Scimmia) - Wednesday, 06 May 2015, 18:51 GMT
Sorry about that, my fault
Comment by Jan Alexander Steffens (heftig) - Wednesday, 06 May 2015, 19:25 GMT
Was a bug in the code. Fix sent upstream.

Loading...