unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>,
	help-guix@gnu.org
Subject: Re: Setting up a development environment for guile-g-golf based software in KDE
Date: Sat, 03 Sep 2022 12:29:15 +0200	[thread overview]
Message-ID: <87sfl8px60.fsf@elephly.net> (raw)
In-Reply-To: <PD4zdjYV3Cv2qHfk85ADfpzZDf3_Fhvrvox1z-RVW3MNa4LwbXNKEWUBnyX1uVybAk77BXAHuyvvh9CRiGnl7pt0ffzl8FWaIPhfe4nQwNY=@protonmail.com>


Luis Felipe <luis.felipe.la@protonmail.com> writes:

> [[PGP Signed Part:Undecided]]
> On Friday, September 2nd, 2022 at 18:30, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
>
>> In my case (guix 16a6cbe), the example doesn't work at all,
>> regardless of the desktop environment or whether I use a pure
>> environment or container without grafts.
>
> Hmm, I changed "gtk" to "gtk@4" and now it runs. Which is weird.
>
> I noticed, though, that there are several GLib-GIO-CRITICAL errors related to dbus. Adding "dbus" to the package list make them go away.

I had to run the guile-gi example under “dbus-launch” to make the errors
disappear.  guile-gi works fine with grafts and GTK4; g-golf requires
grafts to be disabled because it doesn’t address problems with gobject
introspection that is triggered by the presence of grafts.

-- 
Ricardo


  reply	other threads:[~2022-09-03 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02 10:25 Setting up a development environment for guile-g-golf based software in KDE Jérémy Korwin-Zmijowski
2022-09-02 11:36 ` Ricardo Wurmus
2022-09-02 20:08   ` Jérémy Korwin-Zmijowski
2022-09-02 18:30 ` Luis Felipe
2022-09-03  1:13   ` Luis Felipe
2022-09-03 10:29     ` Ricardo Wurmus [this message]
2022-09-03 20:24       ` Luis Felipe

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=87sfl8px60.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=jeremy@korwin-zmijowski.fr \
    --cc=luis.felipe.la@protonmail.com \
    /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).