From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jack Hill Subject: bug#39281: gdm doesn't start Date: Sun, 26 Jan 2020 21:26:03 -0500 (EST) Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:60601) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ivu7C-0001LI-VN for bug-guix@gnu.org; Sun, 26 Jan 2020 21:27:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ivu7B-00032C-QG for bug-guix@gnu.org; Sun, 26 Jan 2020 21:27:02 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:51721) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ivu7B-000328-NF for bug-guix@gnu.org; Sun, 26 Jan 2020 21:27:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ivu7B-0005xP-JY for bug-guix@gnu.org; Sun, 26 Jan 2020 21:27:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: 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: Leo Prikler , 39281@debbugs.gnu.org, Raghav Gururajan Cc: sirgazil@zoho.com According to my git bisect, d36fa50fbf8169018193774782fd21f1b13b9c0e [0] is the culprit. It makes some sense that the commit is gnome-related, but I have no idea why adding more packages to the environment should cause gdm to fail to run properly. Therefore, I am inclined to believe that it is a weird timing issue as Leo suspects. [0] http://git.savannah.gnu.org/cgit/guix.git/commit/?id=d36fa50fbf8169018193774782fd21f1b13b9c0e On Sun, 26 Jan 2020, Leo Prikler wrote: > I saw the same warnings on one of my systems as well, but it boots > fine. On another one, the same behaviour occurs, but GDM can be > started manually by restarting xorg-server from a TTY. Note, that I > can not do so from an SSH remote, because SSH fails to start in a > similar manner. My system does indeed have a really slow disk, so perhaps this makes the problem more likely to happen. Obviously, it would be nice if gdm started correctly, but in a bigger picture, it would be nice if shepherd had a better way of dealing with misbehaving services. For example, if shepherd know how to check the health of a service and restarted it wasn't responding correctly. I don't know where to go from here. Hopefully someone more knowledgeable about gnome and gdm can help us out. Best, Jack