Closing since migration issues from three years ago will never be
tackled now, sorry. And the issues described by comments 10 and 11 are
in NetworkManager, nothing to do with the gnome-system-tools (I guess
they're fixed now anyway).
** Changed in: gnome-system-tools (Ubuntu)
Status:
profiles are not migrated by the new upstream version
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Medium
Status: Needs Info = Confirmed
--
[network-admin] network preferences gone after dapper - edgy upgrade
https://launchpad.net/bugs/67201
--
ubuntu-bugs
I experience the same as Eric on a clean Herd-1 install. (prism2_usb
card, I have installed linux-wlan-ng from the CD). The GUI presents
wlan0 as a wired device, so I had to manually edit
/etc/network/interfaces to get online.
--
[network-admin] network preferences gone after dapper - edgy
FYI, when I tried a system upgrade from 6.06 LTS to 6.10, the Wireless
card in a desktop box, which is recognised as such in dapper's Network
Manager, changed to an 'ethernet' card in edgy's Network Manager, so
connectivity was lost. I was unable to set ESSID or WAP key.
I reinstalled 6.06 LTS,
I found the file /etc/gnome-system-tools/network/profiles.xml which
contains the network profiles from dapper. This is probably the file we
want to migrate from.
--
[network-admin] network preferences gone after dapper - edgy upgrade
https://launchpad.net/bugs/67201
--
ubuntu-bugs mailing list
on dapper the profiles were probably under /var/cache/system-tools-
backends/data/network/profiles.xml
--
[network-admin] network preferences gone after dapper - edgy upgrade
https://launchpad.net/bugs/67201
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
rather /var/cache/setup-tools-backends/data/network/profiles.xml
according to upstream
--
[network-admin] network preferences gone after dapper - edgy upgrade
https://launchpad.net/bugs/67201
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I found backups under /var/cache/setup-tool-backends/backup/network
I guess it will be impossible to fix migration of these data on upgrade
before edgy is released.
Isn't it odd that the network data is now in a user directory while I
believe it is system wide configuration?
--
[network-admin]
Before fixing the migration we should make sure it's bugged. The
location issue would be a good question for upstream, it can make sense
to have locations stored by user
--
[network-admin] network preferences gone after dapper - edgy upgrade
https://launchpad.net/bugs/67201
--
ubuntu-bugs
** Summary changed:
- network preferences gone after dapper - edgy upgrade
+ [network-admin] network preferences gone after dapper - edgy upgrade
** Tags added: network-admin
--
[network-admin] network preferences gone after dapper - edgy upgrade
https://launchpad.net/bugs/67201
--
10 matches
Mail list logo