I just tested the latest Xdialog (2.3.1) and suffers from the same problem. As reported in the Xdialog FAQ: "Q13: This said, someone did send me a patch to turn Xdialog into a GTK2 app. Of course, I reworked it so that the default is still to compile Xdialog against GTK1 (...) . The GTK2 port is still incomplete and buggy (problem with output of accented characters on systems using ISO charsets)..." I also noticed that Xdialog ignores the --default-no command when using the GTK2 enabled version. Therefore if someone has the knowledge to get a fix... or else add the gtk2 as a flag and not as default since it breaks. This is more like an upstream problem, but since gtk2 is the default and it's buggy, gtk1 should still be the default. Thanks. Reproducible: Always Steps to Reproduce: 1. Build xdialog with gtk1 2. try something like # Xdialog --title "Yes or no?" --defaultno --yesno "Do you want foo?" 0 0 3. Rebuild xdialog with gtk2 4. Repeat step 2 (notice the selection on yes instead of no)
Correction, Question in FAQ is 12 and not 13
I've bumped Xdialog to 2.3.1 but it appears your problem is still there but still we won't be adding deprecated GTK+-1.2 version back to tree. File a bug of this to upstream.
Bug mailed upstream... x11-libs/gtk+-1.2.10-r12 is still available in portage...
