[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Errors running kicad GUI package in container
From: |
Luis Felipe |
Subject: |
Re: Errors running kicad GUI package in container |
Date: |
Mon, 31 Oct 2022 20:35:56 +0000 |
Hi Peter,
------- Original Message -------
On Monday, October 31st, 2022 at 16:50, Peter Polidoro <peter@polidoro.io>
wrote:
> 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?
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
‾‾‾‾‾‾‾‾‾‾
The command above is what I use to try out an application I'm developing (GTK
4). You should at least change the values to the last two "--expose".
publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature