From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#24948: Illegible GRUB menu Date: Mon, 21 Nov 2016 12:43:22 -0500 Message-ID: <20161121174322.GA29839@jasmine> References: <20161115215443.GA28213@jasmine> <8737ilnx11.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36359) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c8sdV-00044s-Vp for bug-guix@gnu.org; Mon, 21 Nov 2016 12:44:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c8sdO-00056G-Ga for bug-guix@gnu.org; Mon, 21 Nov 2016 12:44:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:50161) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c8sdO-000566-C8 for bug-guix@gnu.org; Mon, 21 Nov 2016 12:44:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1c8sdO-0001Mm-68 for bug-guix@gnu.org; Mon, 21 Nov 2016 12:44:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <8737ilnx11.fsf@netris.org> 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: 24948@debbugs.gnu.org On Mon, Nov 21, 2016 at 01:54:02AM -0500, Mark H Weaver wrote: > Hi Leo, > > Leo Famulari writes: > > On my Thinkpad x200s running GuixSD, the graphical GRUB menu is > > scrambled and illegible. I've attached a photograph of the problem. > [...] > > This is not a recent regression; I've been working around it with the > > diff below for a few months now. > > A few months ago we updated our grub from 2.00 to 2.02beta3, in commit > 4c7260011e219eb3ebf5da976ab107dbd5997829, dated June 16. Was that > roughly when this problem began? > > If so, I suggest reverting that commit in your local tree, to see if > downgrading to grub 2.00 fixes the problem. Thanks for the advice. I'll try this in a few days when I have physical access to that machine again.