ubuntuone crashed during start-up/connection

[ClausStie]

Binary package hint: ubuntuone-client

might be when I turned off bluetooth on my laptop (IBM X60s). doing that also turns off wireless until one press the button again and only wireless is on (toggle I guess its called). BUT I must say it looked like it already had issues during start up when it need to connect to the ubuntuone cloud

claus

ProblemType: Bug
.home.claus..cache.ubuntuone.log.oauth.login.log:
 2010-02-07 13:32:36,394:394.157886505 UbuntuOne.Client.Applet Starting Ubuntu One client version 1.0.3
 2010-02-07 14:12:28,511:511.603116989 UbuntuOne.Client.Applet Starting Ubuntu One client version 1.0.3
 2010-02-08 16:55:56,350:350.043058395 UbuntuOne.Client.Applet Starting Ubuntu One client version 1.0.3
 2010-02-10 08:46:42,214:214.818000793 UbuntuOne.Client.Applet Starting Ubuntu One client version 1.0.3
.home.claus..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 0
 write_limit = 0
 on = False
.home.claus..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 bookmarked = True
 connected = True
 connect = 0
 show_applet = 1
Architecture: i386
Date: Wed Feb 10 08:53:49 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Xubuntu 9.10 "Karmic Koala" - Release i386 (20091028.3)
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-19-generic i686
XsessionErrors:
 (polkit-gnome-authentication-agent-1:2118): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (thunderbird-bin:2314): GLib-WARNING **: g_set_prgname() called multiple times
 (file-jpeg:2561): GLib-WARNING **: g_set_prgname() called multiple times
 (file-jpeg:2578): GLib-WARNING **: g_set_prgname() called multiple times

[Mitch Towner (kermiac)]

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