From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: =?utf-8?B?4oCYc3RhZ2luZ+KAmQ==?= and GNOME updates Date: Tue, 23 Apr 2019 09:17:53 +0200 Message-ID: <87zhoh5gwu.fsf@elephly.net> References: <871s3a4xd4.fsf@gnu.org> <87wokjyuw4.fsf@fastmail.com> <87muld8xuo.fsf@gnu.org> <87y34xzez8.fsf@elephly.net> <87zhpaydem.fsf_-_@gnu.org> <87imvler9u.fsf@elephly.net> <87bm1d8sxv.fsf@gnu.org> <87ef68ibfy.fsf@elephly.net> <87r2a3o39s.fsf@gnu.org> <87sgujgchr.fsf@gnu.org> <878swa3nm9.fsf@elephly.net> <87h8ayfstx.fsf@ngyro.com> <87zhopd7x4.fsf@gnu.org> <87d0le1h38.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:56089) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hIpgy-0005Jd-22 for guix-devel@gnu.org; Tue, 23 Apr 2019 03:18:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hIpgx-00038H-0q for guix-devel@gnu.org; Tue, 23 Apr 2019 03:18:12 -0400 In-reply-to: <87d0le1h38.fsf@gnu.org> 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.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Guix-devel Ludovic Court=C3=A8s writes: > Hello, > > Ludovic Court=C3=A8s skribis: > >> Timothy Sample skribis: >> >>> Ricardo Wurmus writes: >>> >>>> Ludovic Court=C3=A8s writes: >>>>> I removed pretty both .cache directories, moved .config sub-directori= es >>>>> around, etc., and yet I am still unable to log in into the GNOME acco= unt >>>>> (logging in to a non-GNOME account from GDM is fine.) >>>>> >>>>> I even tried upgrading the user=E2=80=99s profile just in case is con= tained >>>>> incompatible schemas or who knows what, but that didn=E2=80=99t help. >>>>> >>>>> What extra bit of state am I missing? >>>> >>>> Do you have ~/.local? In my earlier tests this contained binary >>>> notification data that when loaded would lead to a crash. >>> >>> I=E2=80=99m testing GNOME on =E2=80=98staging=E2=80=99 now, and had the= same problem (GDM worked >>> okay, but I could not login). I fixed it by deleting >>> =E2=80=9C~/.local/share/gnome-shell/notifications=E2=80=9D. I left eve= rything else in >>> my home directory as it was. >> >> That=E2=80=99s the one! I moved ~/.local/share/gnome-shell out of the w= ay and >> after that I could log in. \o/ > > So I=E2=80=99d really like to merge that branch, but this GNOME upgrade i= ssue is > holding us back. > > Does anyone have ideas on how to address it? With this system definition I cannot log into GNOME: --8<---------------cut here---------------start------------->8--- (use-modules (gnu) (gnu system nss)) (use-service-modules desktop xorg) (use-package-modules certs gnome) (operating-system (host-name "antelope") (timezone "Europe/Paris") (locale "en_US.utf8") (keyboard-layout (keyboard-layout "us" "altgr-intl")) (bootloader (bootloader-configuration (bootloader grub-efi-bootloader) (target "/boot/efi") (keyboard-layout keyboard-layout))) (file-systems (cons (file-system (device (file-system-label "my-root")) (mount-point "/") (type "ext4")) %base-file-systems)) (users (cons (user-account (name "bob") (comment "Alice's brother") (group "users") (supplementary-groups '("wheel" "netdev" "audio" "video"))) %base-user-accounts)) (packages (append (list nss-certs gvfs) %base-packages)) (services (append (list (service gnome-desktop-service-type) (set-xorg-configuration (xorg-configuration (keyboard-layout keyboard-layout))) (service (service-type (name 'break-gnome) (extensions (list (service-extension activation-service-type (lambda _ #~(mkdir-p "/home/bob/.local/= share/gnome-shell"))))) (default-value #t)))) %desktop-services)) (name-service-switch %mdns-host-lookup-nss)) --8<---------------cut here---------------end--------------->8--- Note the =E2=80=9Cbreak-gnome=E2=80=9D service. When the service does not = exist, everything is fine. It seems to me that the contents of the directory really do not matter after all. Now I wonder how this affects the gnome-shell startup, because once the upgrade is complete things do work fine. I wonder if there may be a dconf setting that is flipped after initialization. --=20 Ricardo