From: grib@gnumatic.com (Bill Gribble)
To: Ariel Rios <ariel@linuxppc.org>
Cc: guile-user@gnu.org, guile-gtk@sourceware.cygnus.com
Subject: Re: Current status of guile-gnome/guile-gtk?
Date: Fri, 20 Apr 2001 06:56:00 -0000 [thread overview]
Message-ID: <20010420085639.A29249@gnumatic.com> (raw)
In-Reply-To: <987720726.1048.2.camel@soleil>
On Thu, Apr 19, 2001 at 06:52:06PM -0400, Ariel Rios wrote:
> What do you mean by broken? Which version of gnome-guile?
> What is the problem?
firetrap> guile
guile> (use-modules (gnome gnome))
guile> (gnome-init-hack "test" #f '())
[GNOME segmentation fault dialog]
The backtrace would be rather useless because it's all scm_ functions
with no debugging info. My guess is that the wrapper definitions are
somehow out of date WRT current GNOME. The the Debian maintainer
says he sent a bug report but I can't find it on bugzilla; the
original Debian bug report is at
http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=69144
It's against an older version but the problem is the same.
BTW, both the libguilegnome / libguilegtk and guile Debian maintainers
listed below work for Gnumatic too, and I'm pretty much in continuous
communication with both of them on irc.gnome.org #gnucash so I can
help with communication if necessary.
Thanks,
Bill Gribble
Gnumatic
firetrap> dpkg --status libguilegnome0
Package: libguilegnome0
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 547
Maintainer: James LewisMoss <dres@debian.org>
Source: gnome-guile
Version: 1:0.19-pre0.20-5
firetrap> dpkg --status guile1.4
Package: guile1.4
Status: install ok installed
Priority: optional
Section: interpreters
Installed-Size: 124
Maintainer: Rob Browning <rlb@cs.utexas.edu>
Source: guile-core
Version: 1:1.4-10
firetrap>
next prev parent reply other threads:[~2001-04-20 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010419160201.A16701@gnumatic.com>
2001-04-19 17:54 ` Ariel Rios
2001-04-20 6:56 ` Bill Gribble [this message]
2001-04-20 8:51 ` Ariel Rios
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=20010420085639.A29249@gnumatic.com \
--to=grib@gnumatic.com \
--cc=ariel@linuxppc.org \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=guile-user@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.
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).