bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#35996: User account password got locked when booting old generation


From: Gábor Boskovits
Subject: bug#35996: User account password got locked when booting old generation
Date: Mon, 3 Jun 2019 08:14:09 +0200

Hello, 




pelzflorian (Florian Pelz) <address@hidden> ezt írta (időpont: 2019. jún. 3., Hét 8:04):
After I booted to a Guix install USB, chrooted as described on the
Arch wiki and started a Guix daemon, I could reconfigure as before.
There was no need to fiddle with grub-install.

After multiple reconfigures, it happened again, my /etc/shadow has !
again in the password field.  My recently changed root password became
empty as well, like 35902.  I did not even run sudo concurrently.  The
password just got locked.
This is the same thing that happened to me, and there is another report, regarding passwords being reset. I believe we should merge these two bugs. I am on a mobile with no convinient way to look up the issue number.

The /etc from the “populating from /gnu/store/*-etc” messages has no
significant differences either.



On Sat, Jun 01, 2019 at 11:37:51PM +0200, Ludovic Courtès wrote:
> "pelzflorian (Florian Pelz)" <address@hidden> skribis:
> > AccountsService appears to only be usable for reading /etc/shadow, not
> > for writing it, contrary to what the Guix manual claims (??).
>
> That might be a bug.
>

AccountsService obviously can change passwords.  No bug here.  Sorry.
I was confused.


> > For writing passwords, gnome-control-center does not use
> > AccountsService, it calls /usr/bin/passwd directly in its source code
> > in panels/user-accounts/run-passwd.c.
>
> That’s definitely a bug to fix: it should invoke
> /run/setuid-programs/passwd instead.
>

Find attached two patches that fix GNOME password changing.  Both are
required.

Regards,
Florian

On my machine it turned out that the hdd is faulty, so this might be a hardware error, I will get a replacement drive tomorrow, and check if the problem still persist.

Best regards,
g_bor

reply via email to

[Prev in Thread] Current Thread [Next in Thread]