unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Peter Polidoro <peter@polidoro.io>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: Errors running kicad GUI package in container
Date: Mon, 05 Dec 2022 14:22:30 -0500	[thread overview]
Message-ID: <878rjlfxri.fsf@polidoro.io> (raw)
In-Reply-To: <NBUOW16Mc9WDmDCSvKxbPqQFlYFEga3KUKw8uv1bajXrZlQa37VC7YkUTY51qBfMtlyZPtA1K2msRqOqfDCXii5axKcE5dQNcZyZ7uWFotM=@protonmail.com>


Luis Felipe <luis.felipe.la@protonmail.com> writes:

>> > For what it's worth, kicad seems to work for me in a 
>> > container.
>> > I'm using Guix System with GNOME (guix 4716cea):
>> > 
>
>> > __________
>> > guix shell kicad -E "^DISPLAY$" -E "^XAUTHORITY$"
>> > --expose="$XAUTHORITY"
>> > --expose=/tmp/.X11-unix/ --expose=$HOME/.Xauthority
>> > --expose=/etc/machine-id
>> > --expose=$HOME/Descargas --expose=/tmp/dbus-fnAz1hb4to

When I submitted a patch to upgrade kicad to 6.0.9 I went ahead 
and added gdk-pixbuf as an input.

Now it seems to work well, except in at least one strange case.

I noticed that kicad crashes when I run it in a pure shell with 
both kicad and python-ipython:

guix shell --pure kicad python-ipython -- kicad # crashes when you 
click on GUI open project icon
guix shell kicad python-ipython -- kicad # does not crash
guix shell --pure kicad -- kicad # does not crash

I do not know if this is a bug in kicad or in the guix package or 
something else.

I assume this means that one or more environment variables need to 
be set in the pure shell, but I do not know which.

guix shell --pure --check kicad python-ipython -- kicad
guix shell: checking the environment variables visible from shell 
'/bin/bash'...
guix shell: All is good!  The shell gets correct environment 
variables.

guix describe --format=channels
(list (channel
        (name 'guix)
        (url "https://git.savannah.gnu.org/git/guix.git")
        (branch "master")
        (commit
          "48329575c87bbee7166eedf10b1699599e67c49d")
        (introduction
          (make-channel-introduction
            "9edb3f66fd807b096b48283debdcddccfea34bad"
            (openpgp-fingerprint
              "BBB0 2DDF 2CEA F6A8 0D1D  E643 A2A0 6DF2 A33A 
              54FA")))))


      reply	other threads:[~2022-12-05 19:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 16:50 Errors running kicad GUI package in container Peter Polidoro
2022-10-31 20:35 ` Luis Felipe
2022-11-01 15:09   ` Peter Polidoro
2022-11-01 15:54     ` Luis Felipe
2022-12-05 19:22       ` Peter Polidoro [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878rjlfxri.fsf@polidoro.io \
    --to=peter@polidoro.io \
    --cc=help-guix@gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).