unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: "Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de>,
	"help guix" <help-guix@gnu.org>
Subject: Re: Running graphical apps with guix shell --container
Date: Sat, 29 Jan 2022 20:15:39 +0000	[thread overview]
Message-ID: <CDJaB5F18WHmPnamzDGpkA0jOI_bEQU0X3cgoHTdr5ZL5TGHqvhwZCtdif1LatwMGFwZvGDuat3SwaRyeBHbfYdy02sEK9YaUl1Phb9776Q=@protonmail.com> (raw)
In-Reply-To: <YK9mkkoTCM3GjI7FrBlgosIi59nyQoh77rhNDDY2OUeEzkoVxefD3Y50x6C_vqBao3awaCK1DHFmqMwBtMgDD47f3WVpbExxm3j7YHxpqoU=@protonmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1724 bytes --]

On Friday, January 28th, 2022 at 4:01 PM, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
> 

> So this worked:
> 

> EXAMPLE:
> guix shell -C -E "^DISPLAY$" -E "^XAUTHORITY$" --expose="$XAUTHORITY" --share=/tmp/.X11-unix/ --share=$HOME/.Xauthority
> END EXAMPLE
> 

> But I'm just typing things without much consideration and hoping for the best :) For example, the application now starts but it has no icons. So I guess I'll go find some information about all the fundamental variables and resources required by GTK apps to run.

I took a shortcut and just added "gnome" package to the manifest. After this, I also noticed a dbind-related warning¹ when starting the app and lots of dconf-related warnings² when using a file chooser dialog from the app. I got rid of the former by exposing the socket mentioned in the warning, while the latter went away after exposing the machine-id. So the command now looks like this:

EXAMPLE:
guix shell -C -E "^DISPLAY$" -E "^XAUTHORITY$" --expose="$XAUTHORITY" --expose=/tmp/.X11-unix/ --expose=$HOME/.Xauthority --expose=/tmp/dbus-P03C3WeCs0 --expose=/etc/machine-id
END EXAMPLE

At this point, the app is displayed and works as expected :)


1. dbind-WARNING **: 19:19:29.619: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-P03C3WeCs0: No such file or director
2. dconf-WARNING **: 19:39:19.279: failed to commit changes to dconf: Cannot spawn a message bus without a machine-id: Unable to load /gnu/store/qqs98rxwjrji6aaf6dqwp7q4m545g2sn-glib-2.70.0/var/lib/dbus/machine-id or /etc/machine-id: Failed to open file ?/gnu/store/qqs98rxwjrji6aaf6dqwp7q4m545g2sn-glib-2.70.0/var/lib/dbus/machine-id?: No such file or directory

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

      reply	other threads:[~2022-01-29 20:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 23:51 Running graphical apps with guix shell --container Luis Felipe
2022-01-28 10:11 ` Edouard Klein
2022-01-28 15:42   ` Luis Felipe
2022-01-28 21:12     ` Edouard Klein
     [not found] ` <877daks3vs.fsf@ruhr-uni-bochum.de>
2022-01-28 15:22   ` Luis Felipe
2022-01-28 16:01     ` Luis Felipe
2022-01-29 20:15       ` Luis Felipe [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='CDJaB5F18WHmPnamzDGpkA0jOI_bEQU0X3cgoHTdr5ZL5TGHqvhwZCtdif1LatwMGFwZvGDuat3SwaRyeBHbfYdy02sEK9YaUl1Phb9776Q=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=daniel.meissner-i4k@ruhr-uni-bochum.de \
    --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).