ubuntuone-syncdaemon crashed with AttributeError in _upgrade_metadata_3()

[Umbra]

DESCRIPTION: This issue appears when a newer version of the client is installed and then a downgrade is performed. Older version cannot handle new version metadata format and therefore is unable to proceed.

Binary package hint: ubuntuone-client

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ubuntuone-client 1.1.91-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sat Apr 3 13:59:53 2010
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100203.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.utf8
PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-syncdaemon']
SourcePackage: ubuntuone-client
Title: ubuntuone-syncdaemon crashed with AttributeError in _upgrade_metadata_3()
UbuntuOneOAuthLoginLog: 2010-04-03 13:59:28,654:654.304027557 ubuntuone-login Starting Ubuntu One login manager version 1.1.91
UbuntuOneSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[sheldonross (ross-sheldon)]

Is this bug ever going to get addressed? I haven't been able to use ubuntu-one in a couple weeks. There are several duplicates so It is obviously a moderately widespread bug.

[Guillermo Gonzalez (verterok)]

Hi,

I'm trying to reproduce this, and I'm not able to do it.

Did you deleted anything manually? e.g: syncdaemon metadata, "Shared With Me" symlink, etc?

Thanks

[Amedeo (amedeo-salvati)]

hi Guillermo,

thanks for your support, but in my case i didn't deleted anything, i just installed ubuntuone on ubuntu 9.04 then i upgraded it to ubuntu 9.10 and now to ubuntu 10.04.

thanks
amedeo

[Milan Bouchet-Valat (nalimilan)]

Same here, with 1.2.1-0ubuntu1 (Lucid).

It happened just after I ran:
      sudo rm -rf ~/.local/share/ubuntuone
      rm -rf ~/.cache/ubuntuone
      rm -rf ~/.config/ubuntuone

After that, 'u1sdtool -s' always triggered the crash.

I was able to fisx this by running the rm commands once again, and restarting the daemon. So I suspect it may be that the first time, I didn't kill the daemon before removing the files as I should have, which caused corruption in the db.

Still, the tool shouldn't crash... ;-)

[Darius Kulikauskas (dkulikauskas)]

The following procedure:
 * shutdown syncdaemon (u1sdtool --quit in a terminal)
 * backup your shared metadata (tar -cjf share-md.tar.bz2 ~/.local/share/ubuntuone/syncdaemon/vm/shares/)
 * remove the shares metadata (rm -rf ~/.local/share/ubuntuone/syncdaemon/vm/shares/*)
 * start again syncdaemon (u1sdtool -c)
Fixes the state of UbuntuOne Client (I mean, that it is shown "Synchronization in progress..." instead of "Unknown"), but the synchronization does not actually start.

[Stew (stew-schneider)]

I've got the gray exclamation point on the folder varient of this bug. Following the procedure in Darius's note, there is no change -- the gray exclamation mark remains.

Sync from the Me Menu first says "Syncronization complete" but does not have my credentials. My credentials then appear, and the note "Syncronization complete" The individual files within the folder show green check mark. The folder itself shows a gray exclamation mark.

These are very small files, a few K each, text. I initially stored them in Ubuntu One. I then realized that it would be a better move to put them all in one folder. I created the folder, ctl-click selected each of the files and attempted to drag/drop them into the folder. Nothing happened. I repeated. Nothing happened. I drag/dropped each file individually to the folder. All were there. I went to the Me Menu and sync'd. The gray exclamation mark appeared at that point. All the files i had moved to the folder were gone, save one. I tried to recreate the files and save them, and got back a conflict message, even though the files do not show in the folder.

HTH.

[Stew (stew-schneider)]

Hmmm...my problem may be different afterall. Creating a Folder with a space in the name leads to the gray exclamation mark

[Stew (stew-schneider)]

OK, following receipt of your email, I did the following:
Clicked Places|UbuntuOne
Right clicked and chose Create Folder, which I named Test Folder. It showed a gray exclamation point
I copied a file into the folder, then double clicked the folder. The file was there, also showing a gray exclamation point
From the Me Menu, I chose UbuntuOne. The preferences window showed "Synchronization in progress" for a few seconds, then "Disconnected" for a few seconds, then "Synchronization in Progress". This pattern repeated for 8 minutes. We never sync'd.

I canceled the sync, and, as you requested, entered apport-collect -p ubuntuone-client 592917

Crapped out on the password prompt and for the life of me I don't know why.

[Stew (stew-schneider)]

After 22 minutes, both the folder and the file still show the gray exclamation point and arrows. apport-collect says that it ran.

[Stew (stew-schneider)]

Eventually, the file shows sync. The folder, with a space in the name, does not

[Brewster Malevich (brews)]

I got this error after upgrading from 10.04 to 10.10 RC x86. I hadn't clicked on anything relating to U1. Just logged into my account and then this crash. I had upgraded to 10.10 amd64 previously on my laptop for the beta test (which is linked to my U1 account) although I have had no problem there.

[Joshua Hoover (joshuahoover)]

Metadata from a user who was having this problem: https://chinstrap.canonical.com/~jhoover/u1metadata.tar.bz2

[Leo Arias (elopio)]

Thank you for taking the time to report this bug and helping to make Ubuntu One better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu One since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 554561 and any other logs that are relevant for this particular issue.