role picked before policy changes checked in

But there's an error when I run vacm; I wonder if one of you could have a look?
I'm not sure if this error occurred before these changes, but here's what it does
now. Choose:

Configure Your network
  Manage Access Control
  Create a new role
  Create a new policy
  Manage Group Membership
     Choose a Group (Create a new one)
     Add Access Privs, check Done adding privs
     Add users to group you just created
        enter a user name, then check Done adding users
Commit

Then, if you're like me, you'll get an error: 
"That user/security model combination is already a member of a group".

But that's not true. I did some debugging, and the sub is_duplicate
appears to be getting a match on blank = blank, thus finding it is
a duplicate. Was this always broken? If not, any ideas what I've
done to break it? I've wasted at least 1/2 day looking at it, and I'm
fresh out of ideas.

thanks,

lindy




-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3