GNOME Bugzilla – Bug 667356
can't enter password when changing settings
Last modified: 2012-01-26 00:10:04 UTC
When using the Gnome 3 front-end for Network Manager ("Network Settings"), choosing a connection and clicking "Configure" brings up nm-connection-editor. Upon saving the changes in nm-connection-editor, a password prompt is presented, but it disappears too quickly to enter a password, and the settings are not saved. The workaround has been to run nm-connection-editor manually to make changes. The same password prompt works fine when changing other settings. I found this while using Arch Linux; it's been like this since I installed it several months ago. I just updated the whole system on 01/04/2012, and it still has this problem.
Is this 3.2 or 3.0? Which NetworkManager version is this about?
Okay, I did some more research. It is "gnome-control-center network" v3.2.2 that launches "nm-connection-editor --edit <some long UUID>" in Arch, that is owned by the network-manager-applet package, and that is v0.9.2.0. If I launch nm-connection-manager without any options, it works fine (as previously stated). If I launch it with --edit, I get the bug where the password prompt disappears when pressing "Save...". I get some errors on the console when I launch either with or without the "--edit" line. I believe they are unrelated, but I'm including them to be thorough. When the edit dialog comes up, I get "(nm-connection-editor:31517): Gtk-WARNING **: No object called: wired_device_mac". When I make a modification and save the settings, I get seven of "** (nm-connection-editor:31523): WARNING **: Invalid setting IPv4 Settings" (these errors do not appear if I click save without making any changes).
I can confirm this bug exactly as described. I am also running Arch Linux. Here is what happens when I attempt to modify my DHCP wired connection to a manual IP, netmask, default gateway, and DNS server: [njbair@nicks-desktop ~]$ nm-connection-editor --edit 83c29493-5a43-4728-93b9-e69462d1295f ** (nm-connection-editor:2145): WARNING **: nm_connection_list_new: failed to load VPN plugins: Couldn't read VPN .name files directory /etc/NetworkManager/VPN. (nm-connection-editor:2145): Gtk-WARNING **: No object called: wired_device_mac At this point I make my edits and press Save: ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings: addresses ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings: addresses ** (nm-connection-editor:2145): WARNING **: ui_to_setting: IPv4 address '<none>' missing or invalid! ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings ** (nm-connection-editor:2145): WARNING **: Invalid setting IPv4 Settings [njbair@nicks-desktop ~]$
Regarding the VPN error in my previous comment: ** (nm-connection-editor:2145): WARNING **: nm_connection_list_new: failed to load VPN plugins: Couldn't read VPN .name files directory /etc/NetworkManager/VPN. I manually created the directory /etc/NetworkManager/VPN and the below error went away. All other behavior remained the same. As stated by Shawn, the `Invalid setting IPv4 Settings' errors only appear if changes were made before clicking Save. If I click Save without making changes, no errors appear but the password dialog still closes. The only other error is `No object called: wired_device_mac'. If I run nm-connection-editor with no arguments, that same error appears when I highlight the connection and click Edit. However, running it with no arguments, as Shawn stated, does not cause the password dialog to close. Long story short, none of the errors displayed relate to this bug.
What do you get when you run this command? dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.GetPermissions you're looking specifically for the "modify.system" and "modify.own" permissions. What values are they?
Never mind, found and fixed as: 515195990c5b36171d30cdd9e62c76f117f25c7e editor: fix interaction of single-edit mode with PolicyKit authentication (bgo #667356)