Hello Marco, or anyone else affected, Accepted gnome-shell into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.28.2-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1777956 Title: Login screen reuses last written password after user selection Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Bug description: [ Impact ] Login could be delayed while a loging with a wrong password could be retried. See the screencast https://gitlab.gnome.org/GNOME/gnome- shell/uploads/9e74e74b81ef4d986a77b728e010af37/out.webm See upstream issue https://gitlab.gnome.org/GNOME/gnome- shell/issues/311 1. Try to login up to `allowed-failures` defined with a positive value and using wrong password 2. Continue writing a password as soon as the interface is sensitive again 3. The interface will go back to user selection 4. Select your user and gdm will try to start the authentication [ Test case ] 1. Try to login using a wrong password (assuming `allowed-failures` setting is default) 2. Continue writing a password as soon as the interface is sensitive again 3. The interface will go back to user selection 4. Select your user again 5. The password field is active and you can properly write the password with no wait [ Regression potential ] Login questions which might have been already requested on more complex pam configurations could not be properly handled (requesting answers again). Login/Unlock retries could not be handled properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
