Hello Robert, or anyone else affected, Accepted shadow into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shadow/1:4.1.5.1-1.1ubuntu2.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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1342875 Title: Unable to delete currently logged in user Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Trusty: Fix Committed Status in shadow source package in Utopic: Fix Committed Bug description: [SRU justification] Regression from previous releases, this prevents cloud instance setup processes from removing the default admin account that's exists solely for the purpose of the setup itself. [Test case] 1. Create a trusty schroot environment 2. Log into the trusty schroot environment as a non-root admin user: schroot -c trusty 3. Attempt to remove the admin account: sudo userdel -f vorlon (warning! do not use -r if your host system's home directory is mounted!) 4. Observe the following error: userdel: user vorlon is currently used by process 5253 userdel: cannot open /etc/subuid 5. Upgrade to the passwd package from trusty-proposed 6. Attempt to remove the admin account again 7. Verify that the command has succeeded. [Regression potential] Minimal, as this is a targeted bugfix to the error handling for subuids. A user can not delete themselves using the command 'sudo userdel -rf <username>', this is common in cloud tools that clean up running images prior to capture. A quick test shows that this worked from Precise (didn't look back further) to Raring and stopped working with Saucy. Here's a quick example of the failure (from trusty): # sudo adduser test # sudo usermod -aG sudo test ## As the 'test' user # sudo userdel -rf test userdel: user test is currently used by process 9600 userdel: cannot open /etc/subuid ## User is not removed Previously (output from precise) # sudo userdel -rf test userdel: user test is currently logged in userdel: warning: can't remove /var/mail/test: No such file or directory ## User is removed This is being run as the last command by tools that remove the 'ubuntu' user to clean the image prior to capture. This had previously worked and it is preferable that this could be made to work again. The alternative is removal by root, but the root user on cloud images is locked down and we would not want the user to enable root to run userdel on the risk of it not getting disabled properly prior to image capture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1342875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
