After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 552915 - NetworkManager fails access to keyring
NetworkManager fails access to keyring
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: nm-applet
git master
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2008-09-19 16:44 UTC by badpazzword+gnome
Modified: 2009-05-10 07:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description badpazzword+gnome 2008-09-19 16:44:56 UTC
Please describe the problem:
When I connect to a network for the first time, I am asked for the network key. The following message is displayed on stderr:

** Message: <info>  No keyring secrets found for Auto ThisIsNotYourRouter/802-11-wireless-security; asking user.

The key is however saved in my keyring and it is set to be available to nm-applet by default.

When I go to the connection editor window, browse to the Wireless tab and doubleclick the item automatically created, I expect the password to be found in Wireless Security/Key. The field is blank instead. Stderr reads:

** (nm-connection-editor:7071): WARNING **: Invalid setting Wireless Security: Invalid wireless security

Trying to set the password from this dialog has nm-applet display the "Disconnected" popup as soon as I click Ok. Further attempts to reconnect fail until I remove the item in Network Connections. From stderr:

** (nm-applet:6780): WARNING **: nma_gconf_connection_changed: Invalid connection /system/networking/connections/1: 'NMSettingWireless' / 'ssid' invalid: 2
** (nm-applet:6780): WARNING **: Invalid connection: 'NMSettingWireless' / 'ssid' invalid: 2
** (nm-applet:6780): WARNING **: _nm_object_get_property: Error getting 'Connection' for /org/freedesktop/NetworkManager/ActiveConnection/5: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
** (nm-applet:6780): CRITICAL **: applet_get_connection_for_active: assertion `path != NULL' failed
** (nm-applet:6780): WARNING **: Error in getting active connection 'Vpn' property: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
** (nm-applet:6780): WARNING **: _nm_object_array_demarshal: couldn't create object for /org/freedesktop/NetworkManager/ActiveConnection/6
** (nm-applet:6780): WARNING **: Error in getting active connection 'Vpn' property: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
** (nm-applet:6780): WARNING **: _nm_object_array_demarshal: couldn't create object for /org/freedesktop/NetworkManager/ActiveConnection/6

Once I delete the entry I am again able to connect, after manually providing the network key.

Steps to reproduce:
1. Connect for the first time to a wireless network.
2. Provide network credentials.
3. Disconnect.
4. Reconnect.


Actual results:
I am again asked network credentials.

Expected results:
NetworkManager reads the password from the keyring and completes connection.

Does this happen every time?
Yes.

Other information:
I think this also affects connections of other kinds, but I have'nt tried this.
Comment 1 Dan Williams 2008-09-25 16:20:59 UTC
which NM svn and applet svn revisions are you running?
Comment 2 badpazzword+gnome 2008-09-25 16:47:28 UTC
A trip on packages.ubuntu.com tells me ".7~~svn20080908t183521+eni0-0ubuntu4"

http://packages.ubuntu.com/intrepid/network-manager
Comment 3 badpazzword+gnome 2008-09-25 16:48:21 UTC
The applet is version 0.7~~svn20080907t033843-0ubuntu2

http://packages.ubuntu.com/intrepid/network-manager-gnome
Comment 4 Dan Williams 2009-05-10 02:41:03 UTC
Is this still an issue with latest Ubuntu 8.10 updates, or with 9.04?
Comment 5 badpazzword+gnome 2009-05-10 07:00:43 UTC
Nope. The issue (somehow) fixed itself with one of the various updates pushed with packages... and I switched to unsecured wireless anyhow. :)