Cannot delete old wifi configurations

[pyrates]

Currently if I go to delete an old wifi configuration and the hardware is not plugged in, then it appears to let me delete it but then when I open up network configuration again its still there.

1. Ubuntu 8.10
2. Latest one after running apt-get upgrade && apt-get update
3. I expect to be able to delete the old wifi configuration for that particular ssid
4. But when I close the network configuration and open it again, it hasn't been removed since I don't have the wifi device plugged in.

[Patrick Kilgore (patrick-kilgore)]

When you delete them from the network configuration manager, you should see the connections being deleted in the:
~/.gconf/system/networking/connections

folder.

Does this happen? Or are there fewer connections in that folder than there are connections listed in the network configuration manager?

Thanks for the additional information.

[pyrates (pyrates18)]

I'm not sure what you mean, all I see is the following directory and file structure in that folder.

# tree ./
./
|-- %gconf.xml
`-- 1
    |-- %gconf.xml
    |-- 802-11-wireless
    | `-- %gconf.xml
    |-- 802-11-wireless-security
    | `-- %gconf.xml
    `-- connection
        `-- %gconf.xml

4 directories, 5 files

If it helps, I also can't select among my 3 network ports on this computer. Only eth2. Network Manager calls them Auto eth0, Auto eth1, and Auto eth2. The wifi connection information is called Auto Wifi with Wifi being the SSID name.

The network manager version is NetworkManager Applet 0.7.0.

[pyrates (pyrates18)]

What else do you want? I'm still effected by this bug in Ubuntu 9.04.

[Przemek K. (azrael)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version (10.04), this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 310130, and any other logs that are relevant for this particular issue.

[pyrates (pyrates18)]

Unfortunately I couldn't wait much longer and so I wiped my installation and started from scratch. That seemed to fix it. This seems to stem from the problem if configuration files that the wifi manager is dependent on are deleted. I know the obvious answer is to reinstall the package that adds those configuration files but since I don't know what package provides that, I wasn't able to do that. Now perhaps if I knew what configuration files were missing, I could look up the package that provides them, but that seems tedious.

It be nice if wifi manager and possibly the OS itself can automatically check the format of all configuration files and if any are missing, replace them automatically. That to the end user seems to be so much easier then having to look for the package that provides those files.

So you can close this since I can't seem to reproduce it anymore.

[Przemek K. (azrael)]

Thanks for the information. I'm closing this bug based on your last comment.