Investigating the problem, I have found out that none of the numbered sub-folders in my "~/.gconf/system/networking/connections/" folder was referring to my wired network interface (named iirc "Auto eth0"). That could easily explain the troubles I had when trying to change any settings related to that "ghost" interface. At one point I have deleted the "ghost" interface entry in nm-connection-editor and then created a new one. This newly created NetworkManager interface is now freely configurable and the corresponding folder is now to found in the gconf folder.
That said, two questions remain: 1. why the interface folder disappeared in the first place? Was this the cause or the consequence of the crash at the origin of this bug report? 2. how come the ghost interface remained visible in nm-connection-editor? Could this be explained by the fact that NetworkManager process had not been restarted after the disappearance of the interface folder? ** Visibility changed to: Public -- nm-connection-editor crashed with SIGSEGV in ce_polkit_button_get_actionable() https://bugs.launchpad.net/bugs/434579 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
