network-manager loses edits in network address form, apply button doesn't change connection

Bug #395896 reported by Craig Hansen
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Invalid
Undecided
Unassigned
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When attempting to set a manual configuration in the IPv4 settings panel, the address fields behave badly - clicking on an empty field make the editable field appear a little out of place, using the tab key or pressing the apply button (instead of pressing the enter key) after typing in a value loses the value.

Finally, pressing the apply button doesn't set the new IP address immediately; it doesn't change until I turn the "enable networking" check box off and then on.

The latter workaround makes it impossible to perform the edit remotely, as turning off the check box does immediately turn off the network.

Revision history for this message
sheldonross (ross-sheldon) wrote :

I would just like to add that having the tab key switch from ip address to subnet mask to gateway would be nice. When manually configuring an ip, I have to click on the ip address, hit enter, click on the next field, etc. for each field.

Revision history for this message
Brad Krause (brad-krause) wrote :

I find the same thing in Xubuntu 9.10 (current). Instead of pressing Tab you have to press Enter each time a value is entered.

Also, Network Manager does not report when the connection becomes broken and a system restart is needed. (see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/464559 for an example)

Also, NM can't stay connected to hidden (no SSID in the beacon broadcast) networks. NM can connect to a "hidden" network initially, but has trouble reconnecting, especially if there are two "hidden" networks (SSID=""). The "hidden" networks can be on different channels, but since NM has no channel selector, this isn't an option. NM does have a BSSID field that can be used, but doesn't appear to be, although it could be because some cards (i.e. Linksys) ignore the BSSID request.

Revision history for this message
Vish (vish) wrote :

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue, in the default Ubuntu install, that affects many people and is quick and easy to fix. So this bug can't be addressed as part of this project.

- Manually editing IP settings is not a task we expect an average user to be performing.
For further information about papercuts criteria, please read https://wiki.ubuntu.com/PaperCut.

Don't worry though, this bug has been marked as "Invalid" only in the papercuts project.

Changed in hundredpapercuts:
status: New → Invalid
Revision history for this message
Martin (ub71-martin) wrote :

about what Craig said at first

 "Finally, pressing the apply button doesn't set the new IP address immediately; it doesn't change until I turn the "enable networking" check box off and then on.

The latter workaround makes it impossible to perform the edit remotely, as turning off the check box does immediately turn off the network."

I am 99% sure it is the same issue I've just confirmed here:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/297745

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

The original request of saving what's currently entered in the address fields has been fixed some time ago already, and so is being able to switch from field to field within the address entry using Tab; so closing as Fix Released.

no longer affects: network-manager
Changed in network-manager (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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