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: Thu, 2 May 2024 18:57:24 -0300	[thread overview]
Message-ID: <20240502185724.29c65892@tintin> (raw)
In-Reply-To: <87ikzwdp5e.fsf@pelzflorian.de>

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

Hi Florian,

> Hi David.  I’m trying to find the true error location.

The true error location was given by the gdb backtrace, the
gtk-widget-snapshot-child call, presumably with a bad pointer or so ...

Could you please upload a full gdb backtrace somewhere tor-friendly
(and zero javascript), so i can look at it, thanks.

>  Could you tell  me if, when you run such commands in guile in your
> Debian setup, you get similar output?  First with tracepoint:

With all due respect, this will get you nowhere, please upload the full
gdb backtrace ... thanks

> ...
> (guile:8143): Gtk-WARNING **: 20:34:10.905: Unable to acquire the
> address of the accessibility bus:
> ...

Unlike you said in another mail, this can definitely be solved, please
talk to the guix gnome team, upstream devs if necessary, compare with
what other distro do, use the gnome-calendar to track and fix this
problem ... not fundamental, but you'll learn on the way to fix this,
and those warnings are quite annoying, not to mention that they
scare your (Guix) users.

Meanwhile, can you try:

	cd /your/path/to//examples/gtk-4
	export GTK_A11Y=none
	./drawing-widget.scm

and see if that suppresses the warning as suggested?

Thanks,
David

ps:	what is your guix host distro?

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

  reply	other threads:[~2024-05-02 21:57 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
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 [this message]
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=20240502185724.29c65892@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).