oneconf-service crashed with TypeError in get_oauth_params(): Unicode-objects must be encoded before hashing

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

I constantly get this bug! Very annoying, please fix!

I got this bug too after upgrading from Ubuntu 15.04 to Ubuntu 15.10

looks like I "solved" the bug by reinstalling oneconf

sudo apt-get install --reinstall oneconf
sudo dpkg-reconfigure oneconf

The bug re-appears after 2/3 boot...

Same problem after upgrade from 15.04 to 15.10, the error occur after I empty the trash and the home directory is suddenly opened in a new window

Same problem after upgrade from 15.04 to 15.10.

Same problem on fresh 15.10 install.

I thought Ubuntu One was obsolete?? Why are related packages still being used?

I have this problem also on a fresh install of 15.10 x64

The advice at
http://osdir.com/ml/ubuntu-bugs/2015-11/msg03922.html
appears to provide a temporary solution.
The problem reappears after some event occurs: Possibly that event described by marcoeminente158 - regardless of whether the device is running a clean or upgraded installation.

Attached is a copy of the oneconf crash log.

I've located the cause of this in my machine, and it's environmental: python3.4 has a pip3-sourced oauthlib, while oneconf depends on the apt-get-sourced version (python3-oauthlib). The following procedure fixed it.

    # capture the list of apt packages that depend on oauthlib
    APTNAME=python3-oauthlib
    PIPNAME=oauthlib
    DEPS=$(sudo apt-get remove $APTNAME -sy | grep $APTNAME | head -1)
    # Need to do this; pip's lib gets "hidden" from pip by the OS-managed lib, even though it takes precedence.
    sudo apt-get remove $APTNAME -y
    # Remove the offending pip version
    sudo pip3 uninstall $PIPNAME
    # Restore the applications we just removed.
    sudo apt-get install $DEPS -y

It might be possible to do a workaround in code to compensate for different versions of oauthlib, but that's above my paygrade in terms of python code. Possibly just encoding the unicode content to ascii before b64 encoding, as the traceback states.

Ok, I worked out a place where the `body` argument could be wiggled into place to stop breaking the sha1 hasher. Attached a patch that overloads infraclient_pristine.WebCatalogAPI#_prepare_body to encode the string correctly.

The attachment "Patch creating `infraclient_pristine.WebCatalogAPI#_prepare_body` to utf-8 encode the `body` for requests." seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]