From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guillaume Le Vaillant Subject: bug#40652: #36924 way solves the problem for me Date: Thu, 16 Apr 2020 11:24:38 +0200 Message-ID: <87mu7bye95.fsf@yamatai> References: <20200416002020.GA381@tulip> <20200416053137.GA787@tulip> <87pnc7yjgd.fsf@yamatai> <877dyfkegp.fsf@gnu.org> <87o8rryfih.fsf@yamatai> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:51967) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jP0lb-0008CT-ET for bug-guix@gnu.org; Thu, 16 Apr 2020 05:25:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jP0la-0001mV-CT for bug-guix@gnu.org; Thu, 16 Apr 2020 05:25:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:54239) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jP0la-0001mR-AC for bug-guix@gnu.org; Thu, 16 Apr 2020 05:25:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jP0la-00047w-6a for bug-guix@gnu.org; Thu, 16 Apr 2020 05:25:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87o8rryfih.fsf@yamatai> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 40652@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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... --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQQkUwKxurH4Z/3KlryPP4Yfgut6mgUCXpgkVgAKCRCPP4Yfgut6 mh8HAQDcTyzfd0U8WgSDd3se3QirTUntpe2rlbo/z9LT9QHvQgEAh3SZrg1jOHuF cnQr+OBFCcWE/Ttqvcs7KQo99OF8SQ8= =AA+U -----END PGP SIGNATURE----- --=-=-=--