From: Peter Polidoro <peter@polidoro.io>
To: help-guix@gnu.org
Subject: Errors running kicad GUI package in container
Date: Mon, 31 Oct 2022 12:50:25 -0400 [thread overview]
Message-ID: <87eduo2afd.fsf@polidoro.io> (raw)
I am trying to run a GUI package (kicad) in a container on a
foreign distro (xubuntu) and I am running into several errors.
When I run the command:
guix shell kicad --container --preserve='^DISPLAY$'
--share=/tmp/.X11-unix -- kicad
I get a warning about the accessibility bus:
(kicad:1): dbind-WARNING **: 16:51:56.694: Couldn't connect to
accessibility bus: Failed to connect to socket
/run/user/1000/at-spi/bus_0: No such file or directory
Do I need to expose a directory or set some environmental variable
to properly handle this warning?
Then the GUI pops up, but when I click on any icon I get the
error:
Gtk:ERROR:gtkiconhelper.c:494:ensure_surface_for_gicon: assertion
failed (error == NULL): Failed to load
/org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized
image file format (gdk-pixbuf-error-quark, 3)
Does this mean the kicad package is missing some dependencies, say
gdk-pixbuf?
When I try the command:
guix shell kicad gdk-pixbuf --container --preserve='^DISPLAY$'
--share=/tmp/.X11-unix -- kicad
The icons appear correctly, but when I clicking on some of them
causes the GUI to suddenly exit with no errors or warnings.
The kicad package appears to run correctly with the shell --pure
command.
Do I need to fix something in the kicad package definition or add
something to my container shell command to make it work properly?
Thanks!
next reply other threads:[~2022-10-31 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 16:50 Peter Polidoro [this message]
2022-10-31 20:35 ` Errors running kicad GUI package in container Luis Felipe
2022-11-01 15:09 ` Peter Polidoro
2022-11-01 15:54 ` Luis Felipe
2022-12-05 19:22 ` Peter Polidoro
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=87eduo2afd.fsf@polidoro.io \
--to=peter@polidoro.io \
--cc=help-guix@gnu.org \
/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).