unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Georgios Athanasiou <yorgath@gmail.com>
To: Caleb Herbert <csh@bluehome.net>
Cc: help-guix@gnu.org
Subject: Re: Dino segfaults
Date: Fri, 8 Dec 2023 18:59:10 +0200	[thread overview]
Message-ID: <ec77fd94-106d-fdf0-edff-1f950cd1803e@gmail.com> (raw)
In-Reply-To: <87edfwitaf.fsf@bluehome.net>

Hi Caleb,

You're making progress.  Outside the container, does `dino --help' work? 
You can make the program print diagnostic messages. Option 
`--gst-debug-level=LEVEL' (where LEVEL=0..9) can print *a lot* of 
diagnostics for GStreamer.  Have you tried it? It may help you find the 
point at which the program segfaults.

Best Regards,

G.

On 12/8/23 17:54, Caleb Herbert wrote:
> Wojtek Kosior <koszko@koszko.org> writes:
>> Ahh, I forgot we also need to pass the XAUTHORITY variable to the
>> container.  How about this?
>>
>> guix shell --container --no-cwd --network \
>>      --share=/tmp/.X11-unix --expose="$XAUTHORITY" \
>>      dino bash \
>>      -- bash -c "DISPLAY='$DISPLAY' XAUTHORITY='$XAUTHORITY' dino"
> It launches!  But of course, it has no knowledge of my configuration,
> and asks to set up an account.
>


  reply	other threads:[~2023-12-08 18:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 17:48 Dino segfaults Caleb Herbert
2023-12-05 18:29 ` Georgios Athanasiou
2023-12-05 18:57   ` Wojtek Kosior via
     [not found]     ` <87ttovo60m.fsf@bluehome.net>
     [not found]       ` <20231206143431.4b40443e.koszko@koszko.org>
2023-12-07 17:17         ` Caleb Herbert
2023-12-07 17:50           ` Wojtek Kosior via
2023-12-08 15:54             ` Caleb Herbert
2023-12-08 16:59               ` Georgios Athanasiou [this message]
2023-12-09 20:34                 ` Caleb Herbert
2023-12-09 21:25                   ` Igor Gajsin
2023-12-10 11:21                   ` Georgios Athanasiou
2023-12-10 17:28                     ` Caleb Herbert
2023-12-10 19:04                       ` Igor Gajsin
2023-12-11 17:21                         ` Caleb Herbert
2023-12-11 21:51                           ` Wojtek Kosior via
2023-12-10 19:20                       ` Georgios Athanasiou

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=ec77fd94-106d-fdf0-edff-1f950cd1803e@gmail.com \
    --to=yorgath@gmail.com \
    --cc=csh@bluehome.net \
    --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).