GNU bug report logs - #39466
i3 - choosing to write a new config leaves one with an unusable environment

Previous Next

To reply to this bug, email your comments to 39466 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Scott C. MacCallum" <smaccallum <at> protonmail.com>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: i3 - choosing to write a new config leaves one with an unusable
 environment
Date: Thu, 06 Feb 2020 20:19:58 +0000

[Message part 1 (text/plain, inline)]

After starting the i3 desktop environment for the first time and choosing to write a new config, one is left with an unusable environment.

Scott
scmguru - irc.freenode.net

Sent with [ProtonMail](https://protonmail.com) Secure Email.

[Message part 2 (text/html, inline)]

Message #8 received at 39466 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
Cc: 39466 <at> debbugs.gnu.org
Subject: Re: bug#39466: i3 - choosing to write a new config leaves one with
 an unusable environment
Date: Fri, 7 Feb 2020 17:55:42 -0500

On Thu, Feb 06, 2020 at 08:19:58PM +0000, Scott C. MacCallum via Bug reports for GNU Guix wrote:
> After starting the i3 desktop environment for the first time and choosing to write a new config, one is left with an unusable environment.

Can you give more details about what goes wrong? Instructions to
reproduce? This report is too vague.

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Scott C. MacCallum" <smaccallum <at> protonmail.com>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>,
 "leo <at> famulari.name" <leo <at> famulari.name>
Cc: "39466 <at> debbugs.gnu.org" <39466 <at> debbugs.gnu.org>
Subject: bug#39466: i3 - choosing to write a new config leaves one
Date: Sat, 08 Feb 2020 17:11:13 +0000

"Can you give more details about what goes wrong? Instructions to reproduce? This report is too vague."

Yes, sorry about that. Instructions:

1. Boot freshly installed/updated Guix with i3 installed.
2. At the login screen, bottom right, note the following error in red: "Error: status_command not found or is missing a library dependency (exit 127).
3. From the i3 first configuration window, type the <Enter> key "Yes, generate the config."
4. Choose <Win> "Win as a default modifier."
5. Note that the login screen freezes.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.