From mboxrd@z Thu Jan 1 00:00:00 1970 From: Amin Bandali Subject: Re: 1.1.0rc1 available for test! Date: Sat, 11 Apr 2020 09:16:45 -0400 Message-ID: <87k12mduwy.fsf@gnu.org> References: <87369c1ixm.fsf@gnu.org> <87eesv2vpd.fsf@gmail.com> <87eesvuftt.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:34280) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jNG06-0001rU-SE for guix-devel@gnu.org; Sat, 11 Apr 2020 09:16:47 -0400 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: alex sassmannshausen Cc: guix-devel --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable alex sassmannshausen writes: > Heya > > On Sat, 11 Apr 2020, 00:38 Ludovic Court=C3=A8s, wrote: > >> Hi Alex, >> >> Alex Sassmannshausen skribis: >> >> > After successfully completing system setup from the ISO using that >> > selection, rebooting the system launches GDM OK. Signing in to GDM >> > however causes the system to loop back to GDM, instead of starting a >> > ratpoison session. It is not clear to me what causes the issue, but I= 'm >> > happy to help debug if someone can provide me with pointers on doing s= o. >> > >> > Intuitively, I would hazard a guess that the initialisation of ratpois= on >> > fails and the session is aborted, at which point GDM is restarted. >> >> Isn=E2=80=99t it just that GDM defaults to GNOME (not ratpoison), but si= nce >> GNOME isn=E2=80=99t available, it loops back? >> >> What if you click on the small gear and select ratpoison? >> > > You are 100% correct! Thanks for that pointer - I hadn't considered it > would still default to gnome! :) > Not sure if this was ever reported, but IMHO, that GDM defaults to a (nonexistent) GNOME shell option by default even when e.g. Xfce is installed rather than GNOME, is a bug. I recall that for a default installation, GDM would be correctly set to start Xfce by default, but after the first upgrade and reboot, it would automatically be changed to GNOME, which would obviously not work when trying to log in, and one would have to set it back to Xfce once again. I remember being puzzled by this when it first occurred to me. > > Cheers, > > Alex > > > >> Thanks for your feedback! >> >> Ludo=E2=80=99. >> --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEObM8jZRIDS3cwqSYi0Sgzce5VvIFAl6Rwz0ACgkQi0Sgzce5 VvI5VxAAkjAnFZp/0P6S9jKJUwR5UiVm2SCZTGDZ1QiquS8dB+jXxWSm89RXjWh2 sa7hFJV7LwEHNrqxrYjEUkXGJhSr5Xh0tp3xctVyCEbqYR4B9Q5Pypz1LA863//1 BV6T+4sD126GPisAs7MfFKWug8MKNwIzJp85wDNTFlm3vGoF+Rgy1Wd1eDr+AZvn /tfKzlBS+J9rjQeLE46rgBKDwTMPl0AErvMMqj8yE9ipL/UwdWUQYWvVgiHfgpWS mzILv/x/WX2wx98ZOvc6sim/M9ExdV3CZK0SS5SqJFvJ3pZH0GphC4xmtFe20nbq ujqlof7LE7pyalTN5IzkvhvRNMDdovke/Z5aG4/mz85bQaz7+T1qslXJ+LvlvNiv aJpM0raCaJ6vUiSj1aHLHEGVxvEe0aK99l0lScdhis3n9kcOj4A3aISxjPg7JPUQ Rwc/jQavfaWHytFDE/oQj4xBmRPLoDVbjUTcjCW2/rCbJdiGsdFRf9yMcCYwu9BG WZWxdro6ZBCPVzmwh3SsAf7NNPNhhbxnN3dTRz4IqMqHbroAFsbIwdfpoTpR1OUY w6G+5uQj58fDqxS+MbMlLKmrr7wx5snnObBLh252dAcAVZc3VNyNE5V5sj7YtmPV 1RneQw3gAv7SRdjPJaJKJHrY8EKfioOnHXRmjL/OkP+Bpzu4upY= =DqKL -----END PGP SIGNATURE----- --=-=-=--