From mboxrd@z Thu Jan 1 00:00:00 1970 From: "pelzflorian (Florian Pelz)" Subject: bug#35996: User account password got locked when booting old generation Date: Sat, 1 Jun 2019 07:52:38 +0200 Message-ID: <20190601055238.jkhefpupavz7aipi@pelzflorian.localdomain> References: <20190529204517.mqn5xrw23xib4i3u@pelzflorian.localdomain> <877ea6l1on.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:40710) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hWwwx-0002Kk-0d for bug-guix@gnu.org; Sat, 01 Jun 2019 01:53:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hWwww-0000Ye-1i for bug-guix@gnu.org; Sat, 01 Jun 2019 01:53:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:51509) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hWwwv-0000YX-UJ for bug-guix@gnu.org; Sat, 01 Jun 2019 01:53:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hWwwv-0005aV-RG for bug-guix@gnu.org; Sat, 01 Jun 2019 01:53:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <877ea6l1on.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 35996@debbugs.gnu.org On Sat, Jun 01, 2019 at 12:05:44AM +0200, Ludovic Courtès wrote: > Did the old generation you booted have user ‘florian’? > Yes, this is my main machine. The users are the same. > Also, how old was it? User account management changed in March (commit > 0ae735bcc8ff7fdc89d67b492bdee9091ee19e86). > The git commit for both old and new generation is commit ad7466aafd7f166d0b6be5eb32dda1d3ee8a6445 (origin/master, origin/HEAD) Author: Ludovic Courts Date: Sun May 26 23:18:21 2019 +0200 with unrelevant patches (for USB_ModeSwitch) applied on both, as well as a non-working patch adding syslogd as a requirement to udev-shepherd-service (making the generation unbootable and making something display Stack overflow) and a working patch to add a --debug argument to udevd for the new, unbootable generation. The old generation has a patch that adds wrong arguments to udevd that udevd ignores. All seems harmless. I still cannot reproduce despite rebooting the broken generation multiple times and then booting back into the old generation. I wonder what would change /etc/shadow. Regards, Florian