I'm running out of ideas then, that's not really my domain... Maybe something in your configuration prevents usermod from locking the file, even if no process is using it. Can you remember something you did before user creation became impossible? eCryptfs could explain it if the root partition was encrypted, but I don't think the option you chose does this.
Moving the task against usermod, since the gnome-system-tools can't do much here. ** Package changed: gnome-system-tools (Ubuntu) => shadow (Ubuntu) ** Summary changed: - [users-admin] unable to change real name + usermod fails: "cannot lock /etc/passwd" -- usermod fails: "cannot lock /etc/passwd" https://bugs.launchpad.net/bugs/432964 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
