d-feet can no longer parse boolean values for method

[James Hunt]

Attempting to invoke a D-Bus method that takes a boolean value fails. For example, if a method takes:

    (String s, Boolean b)

specifying:

    'foo', 1

... fails with error:

    '12:expected value'

Whereas specifying:

    'foo', True

... fails with error:

    '8-9:unknown keyword'

Same errors occur if a false value is specified using False or 0 (zero).

This is a regression.

Confirmed that application behaves as expected when using dbus-send(1).

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: d-feet 0.3.1-1
ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
Uname: Linux 3.7.0-7-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.7-0ubuntu2
Architecture: i386
Date: Tue Jan 8 14:43:12 2013
InstallationDate: Installed on 2010-10-21 (810 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_CA.UTF8
 SHELL=/bin/bash
SourcePackage: d-feet
UpgradeStatus: Upgraded to raring on 2012-12-20 (18 days ago)

[Thomas Bechtold (toabctl)]

please try "true".See http://developer.gnome.org/glib/2.30/gvariant-text.html for possible values.

[James Hunt (jamesodhunt)]

true also fails.

[James Hunt (jamesodhunt)]

The dbus method I discovered this with is in software I'm currently developing. However, on an Ubuntu system you can see the problem by attempting to call:

  EmitEvent (String name, Array of [String] env, Boolean wait)

With d-feet in raring, the following fails:

  'foo', [], True

Whereas that works in precise (haven't tried in quantal). I can successfully call the EmitEvent() method however in all version of Ubuntu using dbus-send(1) like this:

dbus-send --session --print-reply --dest=com.ubuntu.Upstart /com/ubuntu/Upstart com.ubuntu.Upstart0_6.EmitEvent string:'foo' array:string:'' boolean:true

[Thomas Bechtold (toabctl)]

true (lowercase, no quotes) works fine for me. I tried with org.freedesktop.NetworkManager.Enable() and org.freedesktop.Accounts.User.SetAutomaticLogin(). But your example doesn't work. I'll have a look what's going on there.