thin-client-config-agent crashed with TypeError: string argument expected, got 'bytes'

[naveen]

Bluetooth is also not working correctly.................

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: thin-client-config-agent 0.6
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Tue Feb 5 16:36:34 2013
ExecutablePath: /usr/bin/thin-client-config-agent
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/thin-client-config-agent <email address hidden>
ProcEnviron:
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
PythonArgs: ['/usr/bin/thin-client-config-agent', '<email address hidden>']
SourcePackage: thin-client-config-agent
Title: thin-client-config-agent crashed with TypeError: string argument expected, got 'bytes'
Traceback: TypeError: string argument expected, got 'bytes'
UpgradeStatus: Upgraded to raring on 2013-02-04 (0 days ago)
UserGroups:

[Jamie Strandboge (jdstrand)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1119279, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.