unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: GNU G-Golf 0.8.0-rc-3 available for testing
Date: Sat, 20 Apr 2024 01:51:58 -0300	[thread overview]
Message-ID: <20240420015158.50031f08@tintin> (raw)
In-Reply-To: <87cyql1e56.fsf@pelzflorian.de>

[-- Attachment #1: Type: text/plain, Size: 5000 bytes --]

Hello Florian,

Before i get to the other points of your email, let me exceptionally
raise the last point first:

	> https://ci.guix.gnu.org/build/3767854/details
	This refers to g-golf-0.8.0-a.1

	Can you re-ensure me and confirm you are using the latest
	version, 0.8.0-rc-3, because a number of critical bugs have
	been fixed on the way to and one in 0.8.0-rc-3 ?

> This is a bug in Guix territory; not your g-golf.

Right -

> I have successfully run gtk-4/hello-world.scm, fully responsive
> ...

Great -
Can you 'permanently' fix the problem, in guix i mean, and 'for all',
or is it something every user has(will have to) to know about and 'do',
for every session?

> drawing-widget.scm continued segfaulting, even during the time when
> hello-world.scm worked.

Hum, it is a short and simple example, however, it uses (it has to)
define-vfunc, and this is very likely where the problem is, we'll see
...

But for now, if you don't mind, let's focus on all examples but:

	drawing-widget.scm
	simple-paintable.scm
	animated-paintable.scm

All other gtk-4 example should work, under the condition you set to
successfully run the hello-world.scm example

The adw-1 examples should work as well, both the hello-world.scm and the
adw1-demo.scm

> ...
> My hope was you knew debugging tricks.  After fruitless debug attempts
> with Guile’s ,trace meta-command, I began attaching GDB to Guile,
> where I then run
> ...

I don't have any debugging 'special' tricks or tips - in debian (you'll
have to adapt for guix ofc):

	sudo apt-get install systemd-coredump

then, when facing such a segfault problem, run the example, which
produces a coredump, then:

	cd /var/lib/systemd/coredump/
	# list the files and grab the id of the last coredump, if
	# more then one ... for example ... 1670341
	
	# install the missing symbols
	sudo -- sh -c 'rm -f core ; \
	    coredumpctl dump 1670341 > core ; \
	    find-dbgsym-packages --install core ; \
	    rm -f core'

	# get a backtrace
	sudo coredumpctl debug 1670341
	...
	(gdb) bt

> ...
> scheme@(guile-user)> (load "/home/florian/src/g-golf/examples/gtk-4/hello-world.scm")
> scheme@(guile-user)> (main '("guile"))

No big deal, but i usually run using/calling:
	(main '())

> I’m rarely on IRC and prefer asynchronous communication.

Fine, ping me if you do ... (my nick is daviid)

> The Adwaita hello-world fails in the same way as GTK hello-world

It should not,
nor the adw1-demo, under the circumstances that
makes the gtk-4 hello-world running fine that is ...

> thank you for advising me to use Adwaita; I did not know it is a good
> idea to use it over plain GTK).

Welcome -
You definitely should learn and use adwaita ...
and use gtk-4 for what ever is not in adwaita ofc ...

> Thank you for confirming the real error is this

> > (hello-world.scm:12627): GLib-GObject-CRITICAL **: 23:59:51.067:
> > cannot register existing type 'GdkPixbuf'  

I don't think 'it matters', the thing is to understand and solve is why guix is
trying to load more then once (any of) the typelib(s) involved in the
session/example you are 'running' - 

> The warning when not running d-bus

> (guile:3310): Gtk-WARNING **: 17:06:29.832: Unable to acquire session
> bus: Failed to execute child process “dbus-launch” (No such file or
> directory)
 
> occurs for gnome-calculator as well and is not fatal to it.  Also it,
> strangely, disappeared for g-golf’s hello-world.scm, at the time when
> it worked.

But you should try to solve this, with the help of guix guru ... g-golf
does not depend on dbus, but indirectly, gtk-4 (and or Gio, i can't
recall the full details now) do, to (notably) register the application ...)

Guix g-golf users should be able to assume a zero warning, zero error on
all provided g-golf examples - unless reproducible in other distro ofc.

> There are no per-package services in Guix, so it cannot be guaranteed
> d-bus is running everywhere (and missing d-bus is not fatal).  I did
> try in a Guix System’s GNOME desktop environment and D-Bus and
> something A11Y run there by default.  But the GdkPixbuf error was
> still present.

Caution - the warning that leads to the recommendation to either solve
or set the GTK_A11Y env var has nothing to do with the GdkPixbuf error

> ...
> Now run ./configure [--prefix=/your/prefix] [--with-guile-site]
> $ ./configure --with-guile-site
> configure: error: cannot find install-sh, install.sh, or shtool in
> build-aux "."/build-aux

I'll let you solve this with guix wizard(s)
 
> But the g-golf Guix package does run configure and make check
> successfully after some workarounds.  Their log file is at

> https://bordeaux.guix.gnu.org/build/c6bd0e09-70cc-4b78-8b78-808b6bb9d9b1

The above link doesn't work for me:	502 Bad Gateway

> https://ci.guix.gnu.org/build/3767854/details

This refers to g-golf-0.8.0-a.1

David

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

  reply	other threads:[~2024-04-20  4:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17  5:56 GNU G-Golf 0.8.0-rc-3 available for testing David Pirotte
2024-04-17 22:30 ` pelzflorian (Florian Pelz)
2024-04-18 22:21   ` David Pirotte
2024-04-19 17:00     ` pelzflorian (Florian Pelz)
2024-04-20  4:51       ` David Pirotte [this message]
2024-04-20  8:35         ` pelzflorian (Florian Pelz)
2024-04-30 17:51         ` pelzflorian (Florian Pelz)
2024-05-01  0:51           ` David Pirotte
2024-05-01  8:17             ` pelzflorian (Florian Pelz)
2024-05-07  1:39               ` David Pirotte
2024-05-07  9:36                 ` pelzflorian (Florian Pelz)
2024-05-07 23:53                   ` David Pirotte
2024-05-08 10:49                     ` pelzflorian (Florian Pelz)
2024-05-08 21:51                       ` David Pirotte
2024-05-02 18:50             ` pelzflorian (Florian Pelz)
2024-05-02 21:57               ` David Pirotte
2024-05-03  5:00                 ` David Pirotte
2024-05-03 11:35                 ` pelzflorian (Florian Pelz)
2024-05-04  5:59                   ` David Pirotte
2024-05-04 14:31                     ` pelzflorian (Florian Pelz)
2024-05-04 18:08                       ` pelzflorian (Florian Pelz)
2024-05-04 22:11                         ` David Pirotte
2024-05-04 22:23                         ` David Pirotte
2024-05-04 21:39                       ` David Pirotte
2024-05-05  1:43                         ` pelzflorian (Florian Pelz)
2024-05-05 21:30                           ` David Pirotte
2024-05-06  9:45                             ` pelzflorian (Florian Pelz)
2024-05-06  9:53                         ` Basile Starynkevitch
2024-05-06 13:08                           ` pelzflorian (Florian Pelz)
2024-05-03  0:17           ` David Pirotte

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=20240420015158.50031f08@tintin \
    --to=david@altosw.be \
    --cc=guile-user@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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).