Description of problem:
Reading code of src/virtManagerTui/userworker.py (and running similar test programs):

* Setting libuser.USERPASSWORD directly is not portable; if libuser is configured for a LDAP backend, this will not use the correct format.
* admin.initUser() automatically sets a (locked) shadow password; if a shadow password exists, admin.addUser() overrides libuser.USERPASSWORD to the "password is in /etc/shadow" marker.  In other words, the password setting code code never worked.  (And if it _did_ work, it would set a plaintext password in /etc/passwd!)

For both of the above, the recommended way is to:
1) create an user (which will by default have a locked password), call admin.addUser()
2) then call admin.setpassUser() to set the new password.

* The 'pw_gid' (libuser.GIDNUMBER) attribute of an user contains only the primary group ID.  The API does allow you to pass multiple values, but that's impossible to represent in the backend.  In other words, the code adding the user to the "wheel" group never worked either.

To add a user to the "wheel" group, look up the "wheel" group, and add the user's name to the libuser.MEMBERNAME attribute (without removing the existing values), then call admin.modifyGroup().

Aesthetics:
* The code uses 'pw_*' constants directly instead of using the API-provided names, e.g. libuser.GIDNUMBER.  Both are stable, but using the constants would make it easier to grep libuser users a little.


Version-Release number of selected component (if applicable):
virt-manager-0.9.4-3.fc19.src.rpm