[network-admin] network preferences gone after dapper -> edgy upgrade

Bug #67201 reported by Adriaan Peeters
14
Affects Status Importance Assigned to Milestone
gnome-system-tools (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

After upgrading from dapper to edgy release candidate, my network preferences in gnome-network-preferences are gone. As a result the wireless network (with key) doesn't work anymore.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. Could you attach your /etc/network/interfaces (with private datas like your wep key replaced) and run ifconfig and copy that to the bug too?

Changed in control-center:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Adriaan Peeters (apeeters) wrote :

Hmm, I reconfigured it now so I cannot recover what it contained after the upgrade :s

But afaik the problem is not /etc/network/interfaces but the different network locations that can be saved in the network settings window. I do not know where they are stored.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the locations are stored to .gnome2/network-admin-locations. Did you have some locations configured before upgrade?

Revision history for this message
Adriaan Peeters (apeeters) wrote :

Yes, I had them configured before the upgrade. The given directory exists on edgy but not on my dapper backup.

Revision history for this message
Sebastien Bacher (seb128) wrote :

on dapper the profiles were probably under /var/cache/system-tools-backends/data/network/profiles.xml

Revision history for this message
Sebastien Bacher (seb128) wrote :

rather /var/cache/setup-tools-backends/data/network/profiles.xml according to upstream

Revision history for this message
Adriaan Peeters (apeeters) wrote :

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?

Revision history for this message
Sebastien Bacher (seb128) wrote :

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

Revision history for this message
Adriaan Peeters (apeeters) wrote :

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.

Revision history for this message
Eric Oberlander (eric-oberlander) wrote :

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, and re-established connectivity.

On Edgy's official release, I downloaded the desktop iso and tried again. Running from the CD, in the Network Manager window, there are two NICs shown. Both icons are 'wired' devices, one is called wlan0, and the other eth0. So I'm still unable to configure the wireless interface.

I wondered if it was maybe a HAL issue?

Revision history for this message
Tormod Volden (tormodvolden) wrote :

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.

Revision history for this message
Sebastien Bacher (seb128) wrote :

profiles are not migrated by the new upstream version

Changed in gnome-system-tools:
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

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: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.