Windows client error: unknown encoding: ascii

Bug #1094424 reported by Phoenix Stormcrow
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Confirmed
High
Ubuntu One Client Engineering team

Bug Description

I have just unwrapped a new laptop, with Windows 8 preinstalled. I downloaded and installed the Ubuntu One client, apparently without any problems. When I try to sign in, though, I type in my email address and my password, click the sign in button, and get a message that states: "unknown encoding: ascii".

I've verified, by checking with my other devices, that my log in information is correct. I have uninstalled and reinstalled the client, with no change in my results. I've even tried typing each piece of information into a text editor set to utf-8 encoding, and then copy-pasting into the fields, just in case that turned out to be a workaround... it did not.

Attached is a screen shot of the error.

Thanks for your time, and for the otherwise awesome product.

Revision history for this message
Phoenix Stormcrow (phoenixstormcrow) wrote :
Revision history for this message
Joshua Hoover (joshuahoover) wrote :

Windows 7 users have reported this as well via support

summary: - Can't sign in to Windows 8 client
+ Windows client error: unknown encoding: ascii
Changed in ubuntuone-client:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Ubuntu One Client Engineering team (ubuntuone-client-engineering)
tags: added: u1-support-escalated
Revision history for this message
Joshua Hoover (joshuahoover) wrote :

If you are impacted by this problem, can you tell us if you have a non-ascii character in your username or password?

Revision history for this message
Phoenix Stormcrow (phoenixstormcrow) wrote :

The password I am using for this service does not have a non-ascii character.

UPDATE:

I again uninstalled the client on Windows 8, and reinstalled once more. This time, after installation, I declined to install an upgdate that a popup told me was available. After the installation (without the update) completed, I was able to sign in. Sorry that I failed to mention the update in my original post, as it seems now that it is relevant.

Revision history for this message
Joshua Hoover (joshuahoover) wrote :

Based on comment #4, this is related to the latest release, 4.0.0. Thanks for including that info!

Julien Funk (jaboing)
tags: added: by-user on-production
Julien Funk (jaboing)
tags: added: u1-on-production
Julien Funk (jaboing)
tags: added: u1-by-user
Julien Funk (jaboing)
tags: removed: by-user
Julien Funk (jaboing)
tags: removed: on-production
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.