UbuntuOne icon crashes by try to connect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubuntuone-client
If i want to connect ubuntu one with that cloud the applet crashes down.
ProblemType: Bug
.home.grauelj.
[ubuntuone]
bookmarked = True
connected = True
connect = 2
show_applet = 1
Architecture: i386
CheckboxSubmission: 69137c019895db4
CheckboxSystem: daed2f3d6643b4a
Date: Sun Aug 29 20:56:38 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitec
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-22-generic i686
Joseph,
Sorry to hear you are having problems with Ubuntu One. Looking at your logs it looks like you have a newer version of metadata on your computer. Did you install the trunk version of Ubuntu One then go back to the stable version in the repository?
To fix this you need to repopulate your metadata with the version currently in use by your version of Ubuntu One. If you have anything of great importance in your Ubuntu One folder you you might want to back it up before proceeding (never can be too safe)
1. Quit the Ubuntu One client. From the applet select Quit. Then open a Terminal (Applications > Accessories > Terminal) and run the following to quit the syncdaemon.
u1sdtool -q
2. Delete the old metadata. In a Terminal run.
rm -rf ~/.local/ share/ubuntuone
3. Start Ubuntu One as you normally would Applications > Internet > Ubuntu One
It'll run for a bit as it recreates the metadata.
This bug has been reported by someone else so I am marking this bug as a duplicate of bug 517505. When your bug is marked as a duplicate, you become a subscriber of the other bug report and you will start receiving all messages that are related to the original bug report. You can unsubscribe from your bug at any time. Please make any further comments about this issue on bug 517505.
thank you,
duanedesign