Hide Forgot
I created a VPN connection in network manager. When it wants to connect, asks for password and I check the remember in keyring option. But when I restart the computer, when I want to connect that, again the password is asked from me.
Can you please specify versions of gnome-keyring, libgnome-keyring and NetworkManager? Are passwords saved from other applications? What desktop environment are you running?
I'm using default gnome3 environment. I'm not sure, but if empathy is saving passwords using keyring, it's working. mmmm, let me mention that I have problem with that too, when I restart the computer, I should import settings and accounts from pidgin again into empathy, is it related of adding any good information? gnome-python2-gnomevfs-2.28.1-4.fc15.x86_64 gnome-bluetooth-libs-3.0.0-1.fc15.x86_64 gnome-settings-daemon-3.0.1-1.fc15.x86_64 gnome-games-3.0.1.1-1.fc15.x86_64 gnome-backgrounds-3.0.1-1.fc15.noarch libgnome-keyring-3.0.1-1.fc15.x86_64 gnome-menus-3.0.1-1.fc15.x86_64 gnome-power-manager-3.0.0-1.fc15.x86_64 gnome-python2-libwnck-2.32.0-1.fc14.x86_64 gnome-python2-gconf-2.28.1-4.fc15.x86_64 gnome-icon-theme-3.0.0-1.fc15.noarch gnome-keyring-pam-3.0.1-1.fc15.x86_64 gnome-js-common-0.1.2-4.fc15.noarch gnome-packagekit-3.0.0-1.fc15.x86_64 gnome-icon-theme-extras-3.0.0-1.fc15.noarch NetworkManager-gnome-0.8.998-3.git20110419.fc15.x86_64 gnome-speech-0.4.25-5.fc15.x86_64 im-chooser-gnome3-1.4.2-1.fc15.x86_64 gnome-python2-2.28.1-4.fc15.x86_64 libgnomeui-2.24.5-2.fc15.x86_64 gnome-utils-libs-3.0.0-1.fc15.x86_64 gnome-mag-0.16.2-2.fc15.x86_64 gnome-system-monitor-3.0.0-1.fc15.x86_64 gnome-user-docs-3.0.3-1.fc15.noarch gnome-python2-gnomekeyring-2.32.0-1.fc14.x86_64 libgnome-2.32.1-2.fc15.x86_64 gnome-python2-canvas-2.28.1-4.fc15.x86_64 gnome-python2-gnome-2.28.1-4.fc15.x86_64 polkit-gnome-0.101-1.fc15.x86_64 gnome-disk-utility-3.0.0-1.fc15.x86_64 gnome-bluetooth-3.0.0-1.fc15.x86_64 gnome-desktop3-3.0.1-1.fc15.x86_64 gnome-utils-3.0.0-1.fc15.x86_64 gnome-icon-theme-legacy-3.0.0-1.fc15.noarch libgnome-media-profiles-3.0.0-1.fc15.x86_64 imsettings-gnome-1.2.2-1.fc15.x86_64 gnome-keyring-3.0.1-1.fc15.x86_64 gnome-session-xsession-3.0.1-1.fc15.x86_64 gnome-shell-3.0.1-1.fc15.x86_64 gnome-disk-utility-nautilus-3.0.0-1.fc15.x86_64 gnome-icon-theme-symbolic-3.0.0-1.fc15.noarch gnome-video-effects-0.3.0-1.fc15.noarch gnome-disk-utility-libs-3.0.0-1.fc15.x86_64 gnome-panel-libs-3.0.0.1-3.fc15.x86_64 lovelock-backgrounds-stripes-gnome-14.91.1-1.fc15.noarch gnome-screensaver-3.0.0-1.fc15.x86_64 gnome-terminal-3.0.1-1.fc15.x86_64 gnome-disk-utility-ui-libs-3.0.0-1.fc15.x86_64 desktop-backgrounds-gnome-15.0.0-8.fc15.noarch gnome-games-help-3.0.1.1-1.fc15.noarch libgnomekbd-3.0.0-2.fc15.x86_64 libgnomecanvas-2.30.3-2.fc15.x86_64 gnome-python2-bonobo-2.28.1-4.fc15.x86_64 gnome-themes-standard-3.0.1-1.fc15.x86_64 gnome-vfs2-2.24.4-5.fc15.x86_64 gnome-python2-desktop-2.32.0-1.fc14.x86_64 gnome-session-3.0.1-1.fc15.x86_64 gnome-panel-3.0.0.1-3.fc15.x86_64 gnome-dvb-daemon-0.1.23-2.fc15.x86_64 evolution-NetworkManager-2.91.92-2.fc15.x86_64 NetworkManager-openvpn-0.8.998-1.git20110405.fc15.x86_64 NetworkManager-gnome-0.8.998-3.git20110419.fc15.x86_64 NetworkManager-openconnect-0.8.1-9.git20110419.fc15.x86_64 NetworkManager-vpnc-0.8.998-1.git20110405.fc15.x86_64 NetworkManager-pptp-0.8.998-1.fc15.x86_64 NetworkManager-0.8.998-3.git20110419.fc15.x86_64 NetworkManager-glib-0.8.998-3.git20110419.fc15.x86_64
(In reply to comment #2) > I'm using default gnome3 environment. I'm not sure, but if empathy is saving > passwords using keyring, it's working. mmmm, let me mention that I have problem > with that too, when I restart the computer, I should import settings and > accounts from pidgin again into empathy, is it related of adding any good > information? That's weird. Empathy shouldn't ask you for accounts all over again. This indicates your homedir is readonly or is somehow losing data. Running `seahorse` should give you a list of stored passwords in the keyring.
actually they're saved now. I don't know what happened. but network-manager is still asking for my VPN connection passwords, although I check the remember option every time.
Seems to be NM issue then. Please check saving passwords from other applications to prove gnome-keyring is working properly. For example connecting to sftp://localhost/ in Nautilus and saving password is a great way to begin. Verify that the password is saved in Seahorse and try reconnecting in Nautilus (you'd need to manually unmount the active mount prior doing that).
nautilus is working. can you edit the bug and assign it to nm-applet?
(In reply to comment #6) > nautilus is working. can you edit the bug and assign it to nm-applet? Done. Thanks for confirming this.
The password handling is a bit changed in NetworkManager 0.9. Passwords are not necessarily stored to keyring. Actually, they are saved by NetworkManager itself by default, not into keyring. Although clients can implement an secret agent that is free to manage secrets as it sees fit, including keyring. I am not able to reproduce the bug. The secrets are stored for me, when configured as "Saved" in nm-connection-editor. Please check that there is [vpn-secrets] section in /etc/NetworkManager/system-connections/<your_VPN_connection_name> There should also be this in [vpn]: IPSec secret-flags=0 Xauth password-flags=0 indicating that the passwords are saved. (1 would mean agent-owned, 2 not saved) I think you are using vpnc VPN, right? Please consider upgrading to latest packages, and try gain.
Hi, I edited my connections and checked the Saved tick again there, previously I was checking the save password option when it asked for password while connecting. Now passwords are saved, but I think that windows which asks for passwords while connecting still has the problem. Thanks.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping