Hide Forgot
Description of problem: It seems that some versions of NM are creating broken connection entries, which later versions of NM refuses as invalid. Here is an example (xxx replaces some real name) ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-xxx ... ifcfg-rh: warning: invalid DEVICE name 'Automatické_xxx' ifcfg-rh: read connection 'Xxx' Where ifcfg-Xxx (created on 2012-02-05) looks like this: ESSID="xxx" MODE=Managed KEY_MGMT=WPA-PSK TYPE=Wireless BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no NAME=Borek UUID=1457eea1-4ae6-40a0-848c-1fd16ee67a0a ONBOOT=yes DEVICE=Automatické_xxx USERCTL=no HWADDR=00:1C:BF:03:02:87 PEERDNS=yes PEERROUTES=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes I assume the problem is Czech locale - which has put in 'Automatické' instead of 'Automatic'. But it seems tools like 'nm-connection-editor' do not have any problems? Are the local names supported ? (yeah it's easy to fix with 'vi')... Version-Release number of selected component (if applicable): NetworkManager-0.9.9.0-15.git20131003.fc21.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Error logged Expected results: Tool should handle what it has created itself - either by some 'self-repair' or by supporting such names. Additional info:
Hi, "Automatické_xxx" in UTF8 encoding are 16 bytes. The DEVICE property is the physical interface name as known to the kernel and this name cannot be larger than 15 bytes. So the name is indeed invalid whereas "Automaticke_xxx" is 15 bytes and valid. I don't think, that the invalid value was originally written by NetworkManager because it ignored this property until March 2013 (upstream commit cda65e1 and 2d668d7). Are you sure, that the value was written by NM and not some other tool? My guess is, that the value was written by another tool and your old version of NM simply ignored the value. The new version correctly complains about the error. I don't see, what NM could do to reasonably repair the broken value. Thomas
I'm pretty sure I've not created any NM related connections myself. So the only tools I'm using is nm-applet and nm-connection-editor. It's quite hard to guess after a year which of those 2 tools did that - but I'm using nm-connection-editor only in cases applet fails seriously. (And nm-applet run editor through 'edit connections')
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.