From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020625
Description of problem:
Gdialog is very useful in nautilus scripts but is missing from gnome-utils-2.0.0-4.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: bash: gdialog: command not found
Expected Results: Gdialog should run.
See also bug number 54415. A similar bug was submitted and fixed for a previous
Red Hat Linux release.
This time the situation is a bit different, as gdialog is disabled upstream due
to lack of maintenance. We could enable it but I don't know if it works. I'm
assuming someone turned it off for a reason.
I just started using the gdialog included in GNOME's 2.0.0 gnome-utils
distribution. In order to use it, one needs to configure gnome-utils with
"./configure --enable-gdialog=yes." It has been working fine with what I use it
for, but I plan on asking its developers why it is disabled by default.
Nautilus scripts really need gdialog.
I asked the GNOME folks about this and they reponded by adding the following to
gnome-utils' README file:
[ Gdialog is ] not built by default as the Gtk+ port is incomplete and needs
much attention. We would dearly love to bring this back building - please help
us fix it.
Works fine for me. ldd `which gdialog`:
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x4019e000)
I suspect I am not exercising all of gdialog's features. I'll play around and
see if I can flush out and fix its bugs.
Here's the gnome.org query for gdialog bugs, some may apply to gnome 1.x though:
The return value of gdialog --yesno seems to be incorrect. For example, if I
select Yes, the exit value is 248. This is with the released version of redhat 8.0.
Yes, it's broken. That's why it was turned off. People begged to have it on, now
it's there, it's broken. Amazing! ;-)
It's fixed on the GNOME 2.2 branch I believe.
I guess this bug should have been closed, as we turned gdialog on.