From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#40652: #36924 way solves the problem for me Date: Thu, 16 Apr 2020 23:03:02 +0200 Message-ID: <87eesnf8jd.fsf@gnu.org> References: <20200416002020.GA381@tulip> <20200416053137.GA787@tulip> <87pnc7yjgd.fsf@yamatai> <877dyfkegp.fsf@gnu.org> <87o8rryfih.fsf@yamatai> <87mu7bye95.fsf@yamatai> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:36304) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jPBg6-00054V-DH for bug-guix@gnu.org; Thu, 16 Apr 2020 17:04:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jPBg4-00031N-Qq for bug-guix@gnu.org; Thu, 16 Apr 2020 17:04:06 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:56154) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jPBg2-0002yQ-Am for bug-guix@gnu.org; Thu, 16 Apr 2020 17:04:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jPBg2-00073K-5d for bug-guix@gnu.org; Thu, 16 Apr 2020 17:04:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87mu7bye95.fsf@yamatai> (Guillaume Le Vaillant's message of "Thu, 16 Apr 2020 11:24:38 +0200") 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-mx.org@gnu.org Sender: "bug-Guix" To: Guillaume Le Vaillant Cc: 40652@debbugs.gnu.org Guillaume Le Vaillant skribis: > Guillaume Le Vaillant skribis: > >> Ludovic Court=C3=A8s skribis: >> >>> Hi Guillaume, >>> >>> Guillaume Le Vaillant skribis: >>> >>>> I don't know if it's related, but recently I had GDM crashes at boot >>>> after reconfiguring a system using gdm-service-type (generation n) to >>>> make it use slim-service-type instead (generation n+1), and then >>>> reconfiguring to gdm-service-type again (generation n+2). >>>> >>>> The problem was that the 'gdm' user id number (or group id number) was >>>> not the same in generations n and n+2, which prevented GDM from >>>> accessing the '/var/lib/gdm' directory. >>> >>> When did that happen? >>> >>> Commit a43e9157ef479e94c19951cc9d228cf153bf78ee (Sep. 2019) supposedly >>> ensures that /var/lib/gdm has proper ownership. >>> >>> Thanks, >>> Ludo=E2=80=99. >> >> I think it was around 2 weeks ago. > > Concerning the service extensions of gdm-service-type, is it guaranteed > that %gdm-activation will be run after %gdm-accounts and not before? > If it's not the case it could explain the problem... =E2=80=98%gdm-activation=E2=80=99 would throw an exception if the =E2=80=9C= gdm=E2=80=9D user didn=E2=80=99t exist, so apparently it=E2=80=99s run before the activation snippet of =E2=80=98account-service-type=E2=80=99 (the ordering guarantee is not expli= cit.) Hmm I wonder what I=E2=80=99m missing then. Would you like to try again? Now, I think we should generalize this chown thing and apply it to all the user accounts. =E2=80=98user-homes=E2=80=99 would chown recursively if= needed or use the newfangled shiftfs, like systemd-homed does=C2=B9. Thoughts? Ludo=E2=80=99. =C2=B9 https://systemd.io/HOME_DIRECTORY/