GNOME Bugzilla – Bug 711251
zenity 3.8 --list outputs first answer twice separated by a pipe
Last modified: 2013-11-23 22:38:23 UTC
Selecting the first item from $ zenity --list --column "Item" Apples Oranges Pears Toothpaste now returns `Apples|Apples` while in 3.6 it returned just `Apples`. Similarly, $ zenity --list --column "id" --column "Item" 1 Apples 2 Oranges 3 Pears 4 Toothpaste now returns `1|1` instead of `1`. This messes up a lot of scripts expecting the old behaviour.
That's weird. Which distro? I'm running ubuntu here with 3.8.0 and I'm not seeing this behavior. I also test from master, and it's working as expected. Can you check if from master you're getting this behavior? Perhaps it's some patch applied from the maintainer of the distro?
I see the pipe on Xubuntu 13.10 and Arch Linux. I do _not_ see it on Xubuntu 13.04. xubuntu$ apt-cache policy zenity zenity: Installert: 3.8.0-1 Kandidat: 3.8.0-1 Versjonstabell: *** 3.8.0-1 0 500 http://no.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status arch$ pacman -Qi zenity Name : zenity Version : 3.8.0-1 Description : Display graphical dialog boxes from shell scripts Architecture : x86_64 URL : http://www.gnome.org Licenses : LGPL Groups : None Provides : None Depends On : gtk3 libnotify Optional Deps : None Required By : None Optional For : purity winetricks Conflicts With : None Replaces : None Installed Size : 7596,00 KiB Packager : Jan de Groot <jgc@archlinux.org> Build Date : ty. 26. mars 2013 kl. 12.06 +0100 Install Date : to. 25. april 2013 kl. 09.39 +0200 Install Reason : Explicitly installed Install Script : No Validated By : Signature Where's the git repo? https://wiki.gnome.org/Zenity is not too informative ;)
git clone http://git.gnome.org/browse/zenity :)
after installing from git to --prefix=/tmp/local $ /tmp/local/bin/zenity --list --column foo bar bar while the 3.8 in xubuntu and arch still give $ zenity --list --column foo bar bar|bar I'll report it downstream then (strange that both have the same bug when upstream doesn't?)
> I'll report it downstream then (strange that both have the same bug when > upstream doesn't?) I just updated the arch package to 3.10, and the bug has disappeared there now :-)
Closing