Public bug reported: Binary package hint: gnome-control-center
I found this in http://brainstorm.ubuntu.com/ideatorrent/idea/17813 - but it's not an enhancement request/idea, it's clearly a bug. To reproduce: 1. Create new user 2. Logon as the user 3. Connect to a wireless network that requires a password 4. Change your login (UNIX) password using the "About me..." tool and the "Change password" button. 5. Logout of your Gnome session. 6. Login (with the new password) - you will get prompted to “Enter password to unlock your login keyring” and your OLD user password will be required. Workaround: Manually change the keyring password. This bug is also described here: http://karuppuswamy.com/wordpress/2010/06/18/enter-password-to-unlock- your-keyring-prompt-in-ubuntu/ The user is not prompted in the first place that he/she is using Seahorse to store the wireless network key (which is good UI design, hiding unnecessary complexity). This makes it even more confusing when it turns out that the old password is needed to unlock the keyring. This should be synced. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-control-center 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Wed Jun 23 23:12:41 2010 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-about-me InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) ProcEnviron: SHELL=/bin/bash LANG=en_GB.utf8 SourcePackage: gnome-control-center XsessionErrors: (polkit-gnome-authentication-agent-1:1417): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (firefox-bin:1644): Gdk-WARNING **: XID collision, trouble ahead (gnome-terminal:1707): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- login password not synced with seahorse https://bugs.launchpad.net/bugs/597893 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
