From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jonathan Lane" Subject: adding environment variables to /etc/config.scm Date: Mon, 02 Sep 2019 13:20:46 -0700 Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57411) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i4sol-0007eW-0p for help-guix@gnu.org; Mon, 02 Sep 2019 16:20:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i4soj-0002TF-9I for help-guix@gnu.org; Mon, 02 Sep 2019 16:20:50 -0400 Received: from mx.dorsal.tk ([2001:470:b163::9]:15665) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1i4soj-0002T5-5u for help-guix@gnu.org; Mon, 02 Sep 2019 16:20:49 -0400 Received: from localhost (unknown [IPv6:2601:600:c700:3730:85f:1310:51bf:d8d1]) by mx.dorsal.tk (Postfix) with ESMTPSA id 6064D123DFB for ; Mon, 2 Sep 2019 16:20:48 -0400 (EDT) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org Hello, I have a laptop with Intel graphics and I need to set the environment variable "COGL_ATLAS_DEFAULT_BLIT_MODE=3Dframebuffer" to fix GPU=20 corruption issues as described here: https://wiki.archlinux.org/index.php/Intel_graphics#Troubleshooting https://bugs.freedesktop.org/show_bug.cgi?id=3D88584 Unfortunately, it's supposed to go in /etc/environment, and that file gets clobbered every time I reboot or run `guix system reconfigure`. I see that $GUIXSRC/gnu/system.scm does some logic to generate that file, but I don't see an exported variable to manipulate from config.scm like I do %desktop-services and the like. What is the recommended way to add global variables here? It has to be a global variable because it alters the behavior of the X server before gdm starts or my user logs in - I've tested putting it in .profile and .bashrc to no avail. Alternatively, this bug is not present on Wayland, so an update to make gdm run via Wayland by default and expose Wayland sessions would solve the root problem. Thanks, Jonathan Lane