Comment 10 for bug 488413

Revision history for this message
Mariano Cabrera (mariano-cabrera) wrote : Re: [Bug 488413] Re: NoAccessToken: SD crashes when no access token found

I am using the beta repositories for ubuntuone and I do not see an upgrade
for the last 15 days.

Is that correct?

Regards,

Mariano

2010/2/18 Robson <email address hidden>

> now working good.
> Thanks
>
> On 18 de fevereiro de 2010 13:09, Rodney Dawes
> <email address hidden>wrote:
>
> > ** Changed in: ubuntuone-client (Ubuntu)
> > Status: In Progress => Fix Released
> >
> > ** Changed in: ubuntuone-client
> > Status: Fix Committed => Fix Released
> >
> > --
> > NoAccessToken: SD crashes when no access token found
> > https://bugs.launchpad.net/bugs/488413
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
> > Status in Ubuntu One Client: Fix Released
> > Status in “ubuntuone-client” package in Ubuntu: Fix Released
> > Status in “ubuntuone-client” source package in Karmic: Fix Released
> >
> > Bug description:
> > For Karmic users this bug is currently in proposed Karmic updates, which
> > you can install by following this FAQ:
> > https://answers.edge.launchpad.net/ubuntuone-client/+faq/930
> >
> > For Jaunty users, his bug is released (rev 288) in the Ubuntu One beta
> PPA.
> >
> > Sometimes the SD is started but the user hasn't the necessary auth
> > information yet. Right now, it crashes:
> >
> > 2009-10-24 09:53:32,606 - ubuntuone.SyncDaemon.DBus - ERROR - Can't get
> the
> > auth token
> > Traceback (most recent call last):
> > File
> >
> "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/dbus_interface.py",
> > line 1053, in connect
> > access_token = self.main.get_access_token()
> > File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/main.py",
> > line 286, in get_access_token
> > return self.oauth_client.get_access_token()
> > File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/main.py",
> > line 326, in get_access_token
> > raise NoAccessToken("No access token found.")
> > NoAccessToken: No access token found.
> >
> > What we should do is to alert the applet somehow that we've been started
> > without the user having the proper auth info, and quit.
> >
> > To reproduce: delete the existing access token from the keyring with the
> > client stopped, then start the client. It should go through the
> > authorization process and not die.
> >
> >
> >
> > To unsubscribe from this bug, go to:
> > https://bugs.launchpad.net/ubuntuone-client/+bug/488413/+subscribe
> >
>
>
> --
>
> Robson Franklin Vieira Silva
>
> --
> NoAccessToken: SD crashes when no access token found
> https://bugs.launchpad.net/bugs/488413
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Ubuntu One Client: Fix Released
> Status in “ubuntuone-client” package in Ubuntu: Fix Released
> Status in “ubuntuone-client” source package in Karmic: Fix Released
>
> Bug description:
> For Karmic users this bug is currently in proposed Karmic updates, which
> you can install by following this FAQ:
> https://answers.edge.launchpad.net/ubuntuone-client/+faq/930
>
> For Jaunty users, his bug is released (rev 288) in the Ubuntu One beta PPA.
>
> Sometimes the SD is started but the user hasn't the necessary auth
> information yet. Right now, it crashes:
>
> 2009-10-24 09:53:32,606 - ubuntuone.SyncDaemon.DBus - ERROR - Can't get the
> auth token
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/dbus_interface.py",
> line 1053, in connect
> access_token = self.main.get_access_token()
> File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/main.py",
> line 286, in get_access_token
> return self.oauth_client.get_access_token()
> File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/main.py",
> line 326, in get_access_token
> raise NoAccessToken("No access token found.")
> NoAccessToken: No access token found.
>
> What we should do is to alert the applet somehow that we've been started
> without the user having the proper auth info, and quit.
>
> To reproduce: delete the existing access token from the keyring with the
> client stopped, then start the client. It should go through the
> authorization process and not die.
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntuone-client/+bug/488413/+subscribe
>