From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#27264: gnome-shell-3.24.2 consistently dies during initialization Date: Thu, 08 Jun 2017 22:47:08 +0200 Message-ID: <87lgp2p5pv.fsf@gnu.org> References: <87o9u13e4i.fsf@netris.org> <8760g8t769.fsf@gnu.org> <87shjbwjdc.fsf@netris.org> <87ink6zo19.fsf@gnu.org> <87vao6poh7.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49110) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dJ4Ld-0006Yd-88 for bug-guix@gnu.org; Thu, 08 Jun 2017 16:48:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dJ4La-00047s-47 for bug-guix@gnu.org; Thu, 08 Jun 2017 16:48:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:32853) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dJ4LZ-00047V-W4 for bug-guix@gnu.org; Thu, 08 Jun 2017 16:48:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dJ4LZ-0003g9-QB for bug-guix@gnu.org; Thu, 08 Jun 2017 16:48:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87vao6poh7.fsf@netris.org> (Mark H. Weaver's message of "Thu, 08 Jun 2017 10:01:56 -0400") 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.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver Cc: 27264@debbugs.gnu.org Hello Mark, Mark H Weaver skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> Hi Mark, >> >> Mark H Weaver skribis: >> >>> I have a question: Does GNOME 3 work for *anyone* in Guix now? If so, >>> that would be useful information. If not, I wonder why this got merged >>> into master. >> >> I think many of us use GTK+/GNOME applications, but fewer use GNOME, so >> I suppose we just didn=E2=80=99t test a full GNOME setup. >> >> Next time we should probably do that or, even better, have an automated >> test that logs in, takes a screenshot, and does some OCR to check >> whether we got something that looks like a GNOME screen. > > I think this is unacceptable. The test you propose above is no where > near adequate to assure that the updated desktop environment is usable > for real work. > > I'm annoyed that I've been forced to either use a different desktop > environment in the meantime or else sacrifice security updates. I would > never consider pushing such a major update to master without testing it > first. I'm astonished that anyone thinks that this is acceptable > behavior. I sympathize, and I agree that it sucks. Now, I think we are all guilty. Rather than trying to find someone to blame, I=E2=80=99m more interested in seeing why we got there and what we c= an do to avoid it in the future. Of course we can call for GNOME users to test it, and we=E2=80=99ll surely do that explicitly in the future. But IM= O we should be thankful to those who worked on this upgrade branch, and I feel it would be unwise to sit back and add more on their shoulders. > While it's true that users can boot into an older generation of their > system in an emergency, and that's a *great* comfort, in general it's > not an acceptable fallback because it entails sacrificing security > updates. I'm concerned that our fallback feature has caused people to > become quite careless with breaking things on our master branch. This is wrong. None of us is careless, and suggesting that this is the case is really unpleasant. Thanks to Marius, Kei, and Roel for working on the fix. Ludo=E2=80=99.