all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Remco van 't Veer <remco@remworks.net>
Cc: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
	55516@debbugs.gnu.org, "Wamm K. D" <jaft.r@outlook.com>
Subject: [bug#55516] [PATCH] gnu: Add quod-libet.
Date: Fri, 27 May 2022 23:54:45 +0200	[thread overview]
Message-ID: <874k1ad4ka.fsf_-_@gnu.org> (raw)
In-Reply-To: <87pmk7ueoq.fsf@remworks.net> (Remco van t. Veer's message of "Sat, 21 May 2022 16:45:57 +0200")

Hi,

Remco van 't Veer <remco@remworks.net> skribis:

>> tests/test_browsers__base.py::new_test::test_active_filter /gnu/store/1hg26c00lzj6kcgzia77gmrs5wx89cjr-xvfb-run-1.20.10-3/bin/xvfb-run: line 184:   221 Trace/breakpoint trap   DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE "$@"

This is the crux of the problem.  I searched a bit on the intertubes and
the xorg-server code couldn’t find under what circumstances Xvfb would
get SIGTRAP.

In some packages, rather than use xvfb-run, we’d spawn Xvfb directly,
without further ado.  I wonder if this makes any difference?

Thanks,
Ludo’.




  parent reply	other threads:[~2022-05-27 21:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  4:41 [bug#55516] [PATCH] gnu: Add quod-libet Wamm K. D
2022-05-19  6:15 ` Liliana Marie Prikler
2022-05-19  7:49   ` Jaft
2022-05-19  7:58     ` Liliana Marie Prikler
2022-05-22  1:27       ` Jaft
2022-05-21 14:45 ` Remco van 't Veer
2022-05-21 14:48   ` [bug#55516] [PATCH] gnu: Add quodlibet Remco van 't Veer
2022-05-27 21:54   ` Ludovic Courtès [this message]
2022-05-28  8:55     ` [bug#55516] [PATCH] gnu: Add quod-libet Remco van 't Veer
2022-05-30  2:06       ` Wamm K. D.
2022-05-28  8:57     ` [bug#55516] [PATCH v2] gnu: Add quodlibet Remco van 't Veer
2022-05-28 11:13       ` bug#55516: " Liliana Marie Prikler
2022-05-28 12:36       ` [bug#55516] " Maxime Devos

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

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

  git send-email \
    --in-reply-to=874k1ad4ka.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=55516@debbugs.gnu.org \
    --cc=jaft.r@outlook.com \
    --cc=liliana.prikler@ist.tugraz.at \
    --cc=remco@remworks.net \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.