From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.2.1) Gecko/20030225 Description of problem: I recently used up2date in gnome on RH9 and updated redhat-config-network to version 1.2.15 (this may or may not be related to the problem). Now, whenever I run the rcn tool as non-root user, I get the following warning: redhat-config-network: Error copying //etc/hosts to //etc/sysconfig/networking/profiles//default/hosts: [Errno 13] Permission denied: '//etc/sysconfig/networking/profiles//default/hosts'! This does not occur if I'm in Gnome as root user. Note though, if I just click OK at this warning, it dissappears and the rcn tool and associated network devices appear to operate fine (its damn annoying though). I can see its somehow related to permissions and network configuration profiles. I found a similar bug that came up with the same warning (amongst others), bugzilla'd at 84752 (perhaps unrelated tho), but that was apparently fixed back in phoebe. Any help/ideas would be great. Thanks. Version-Release number of selected component (if applicable): redhat-config-network-1.2.15-1 How reproducible: Always Steps to Reproduce: 1.Log in to Gnome on rh9 as non-root user 2.Open up redhat-network-config 1.2.15 3.Voila Actual Results: Got the following warning box: redhat-config-network: Error copying //etc/hosts to //etc/sysconfig/networking/profiles//default/hosts: [Errno 13] Permission denied: '//etc/sysconfig/networking/profiles//default/hosts'! It is possible to click OK in the box, and the tool and network devices appear to operate normally though. Expected Results: Before, The warning box never appeared and rcn tool just opened straight up. Additional info: I found a similarish report containing the same warning (amongst others), bugzilla'd at 84752 (perhaps unrelated tho), but that was apparently fixed back in phoebe.
I managed to fix this - looks like it had something to do with the network profiles in Network device Control. I created a new network profile, which made the warning go away, but then that new profile refused to delete using the network device configuration applet, so I deleted the folder containing the new profile instead. bizarrely seems to have sorted it all out.