From: Remco van 't Veer <remco@remworks.net>
To: "Ludovic Courtès" <ludo@gnu.org>
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: Sat, 28 May 2022 10:55:38 +0200 [thread overview]
Message-ID: <87zgj23uk5.fsf@remworks.net> (raw)
In-Reply-To: <874k1ad4ka.fsf_-_@gnu.org>
2022/05/27 23:54, Ludovic Courtès:
> 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.
Just looked at it again and it wasn't xvfb getting a sigtrap but it was
the python test process and I managed to reproduce it in a shell
session. After some tracing, I finally got the real error message:
GLib-GIO-ERROR: Settings schema 'org.gnome.system.proxy' is not installed
Adding gsettings-desktop-schemas as an input fixed that! Hurray!
I'll push out a v2 patch after this email.
Jaft, I am really sorry about hijacking your work, but I am so happy the
tests finally run, I can't contain myself..
Cheers,
Remco
next prev parent reply other threads:[~2022-05-28 8:56 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 ` [bug#55516] [PATCH] gnu: Add quod-libet Ludovic Courtès
2022-05-28 8:55 ` Remco van 't Veer [this message]
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=87zgj23uk5.fsf@remworks.net \
--to=remco@remworks.net \
--cc=55516@debbugs.gnu.org \
--cc=jaft.r@outlook.com \
--cc=liliana.prikler@ist.tugraz.at \
--cc=ludo@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.
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.