FS#26085 - [networkmanager] can't remember secure wireless passwords

Attached to Project: Arch Linux
Opened by Jim Yang (yangjeep) - Wednesday, 21 September 2011, 06:23 GMT
Last edited by Ionut Biru (wonder) - Monday, 03 October 2011, 19:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Jan Alexander Steffens (heftig)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When I try to connect to an encrypted wireless network it just keeps asking for a password, over and over.
And I did tried the steps given in https://bbs.archlinux.org/viewtopic.php?id=117971 #7
But it doesn't work.
Anyone could help me on that?

# nm-connection-editor

** (nm-connection-editor:21929): WARNING **: nm_connection_list_new: failed to load VPN plugins: Couldn't read VPN .name files directory /etc/NetworkManager/VPN.

(nm-connection-editor:21929): Gtk-WARNING **: No object called: wireless_device_mac

(nm-connection-editor:21929): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)

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


Additional info:
* package version(s)
extra/gnome-keyring 3.0.3-1
extra/libgnome-keyring 3.0.3-1

* config and/or log files etc.


Steps to reproduce:
1. Try connecting to a secure wireless network
2. Log out
3. Log in, the networkmanager will ask you the password again.
The password cannot be remembered. And the box: "Avaliable to everyone on this computer" cannot be checked as well.
This task depends upon

Closed by  Ionut Biru (wonder)
Monday, 03 October 2011, 19:15 GMT
Reason for closing:  Works for me
Comment by Jelle van der Waa (jelly) - Wednesday, 21 September 2011, 08:17 GMT
please add the [] with the package for this bugreport.
Comment by Jelle van der Waa (jelly) - Wednesday, 21 September 2011, 08:19 GMT
You probably need to start this, since your not using gnome
/usr/lib/notification-daemon-1.0/notification-daemon &
/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1&
Comment by Ionut Biru (wonder) - Wednesday, 21 September 2011, 10:36 GMT
you are just doing it wrong.

don't try to be smarter than nm. run nm-connection-editor as regular user.
next, nm doesn't store wireless passwords in keyring anymore. it does it in /etc/NetworkManager. Only WPA enterprise, vpn are stored in keyring.

Loading...