ubuntuone-client-applet crashed - Expired timestamp

[Jan Obrátil]

Binary package hint: ubuntuone-client

It crashed after login.

ProblemType: Crash
.home.obrys..cache.ubuntuone.log.syncdaemon.exceptions.log:

.home.obrys..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 show_applet = 1
 connected = False
 connect = 0
 bookmarked = True
Architecture: amd64
Date: Sun Oct 25 18:55:09 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ubuntuone-client-applet
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: ubuntuone-client-gnome 1.0.2-0ubuntu1
ProcCmdline: /usr/bin/python /usr/bin/ubuntuone-client-applet
ProcEnviron:
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/bin/ubuntuone-client-applet']
SourcePackage: ubuntuone-client
Title: ubuntuone-client-applet crashed with AttributeError in from_token_and_callback()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:2186): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2186): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2276): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2296): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #460445, 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.

[Joshua Hoover (joshuahoover)]

Hi Jan, Thank you for taking the time to submit this bug report. I believe this issue is occurring because your clock is not set properly. Can you try the following and see if it fixes the problem for you? Go into System->Administration->Time and Date... click "Unlock" and ensure that the Timezone is whereever you live/work. (Not "GMT" or "Europe/London"). Thank you, Joshua