I have the same problem on Gutsy with keyring and networkmanager. The problem might only occeur if one deletes the default keyring with keyring-manager. Creating a valid new (default) keyring always fails. Some investigation of my old Feisty install in comparison to the Gutsy install brought some insights:
Feisty: default keyring is located in ~/.gnome2/keyrings/default.keyring. This one works fine with nm-applet and is displayed in keyring-manager as "default". Gutsy: all keyrings created by the user (e.g. with keyring-manager or the "passphrase for keyring" dialogue from nm-applet) are stored in ~/keyrings/some_name.keyring. The keyrings located here are NOT shown in keyring-manager! In ~/.gnome2/keyrings/ there is a file "default" instead of "default.keyring" that is not shown in keyring-manager either. If you copy over the *.keyring files from ~/keyrings to ~/gnome2/keyrings they are accessable trough keyring-manager. For me it looks like there is a problem in the interplay between gnome- keyring and gnome-keyring-manager. This might be a bug or maybe due to the fact that gnome-keyring-manager is still 2.18.x while all the other gnome-keyring-* stuff is allready 2.19.x. -- gnome-keyring seems broken in gutsy https://bugs.launchpad.net/bugs/129833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
