in XFCE cannot unlock user&groups: "could not authenticate. An unexpected error has occurred"

hello, this bug may be a duplicate of bug 194496. ( https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/194496 )

is there any special reason for why you reported this as a bug for deluge torrent and not gnome-system-tools? the title of your bug report doesn't seem to match the body of the report.

For the record, I have experienced this same issue (as the title of your bug report, not the body of your bug report) using Xubuntu hardy. Selecting Applications > System > Users and Groups, and then Selecting "Unlock" produces the "cannot unlock user&groups: "could not authenticate. An unexpected error has occurred"" message.

Hello,

Is this bug still reproduceable for you? I show this bug as being fixed when testing it on my system.

With a fresh install of Hardy, updates added I was able to unlock for administration tasks. After adding another
admin user, neither I nor the admin user can unlock. Popup says
  Could not authenticate
  An unexpected error has occurred.
A side effect is that navigating from System --> Adminstration, there is no longer
the option to install applications. This has happened on three Hardy installs. Fortunately one of the first things I
did after install is change the root password, so that at least I can visudo, etc.

Thanks for reporting this bug and any supporting documentation.

There are 4 duplicates of this bug.

Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

Thanks for taking the time to make Ubuntu better!

Thank you for taking the time to report this bug and helping to make Ubuntu better. Deluge has had significant code changes with 1.1.2.dfsg-1, available in Ubuntu Jaunty. Could you please test with this version to see if the problem still exists? You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!