Déjà Dup fails with "Got status code 500" when starting backup

[Jess Bring-Larsen]

LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 11.10
Release: 11.10
Codename: oneiric

deja-dup 20.1-0ubuntu0.1
duplicity 0.6.15-0ubuntu2

org.gnome.DejaDup backend 'u1'
org.gnome.DejaDup delete-after 7
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup include-list ['/home/jbl/Dokumenter/Fritid/MTB']
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup last-run ''
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup prompt-check '2011-10-13T18:07:01.661276Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup welcomed true
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File relpath @ay []
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.Rackspace container 'jbl-laptop'
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'jbl-laptop'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.U1 folder '/deja-dup/jbl-laptop'

[Christopher O. Nash (conwrite)]

https://answers.launchpad.net/deja-dup/+question/175524

The error doesn't appear until after it has tried to make a backup for me.

[Michael Terry (mterry)]

Jess, does this happen every time?

Ubuntu One Server folk, is there anything we can do with a status 500 response for a GET request that doesn't include an Oops-ID? The request is against https://files.one.ubuntu.com/content/~/deja-dup/jbl-laptop/duplicity-full.20111013T204554Z.manifest

[Jess Bring-Larsen (jebl)]

Yes, this happen every time.

[Jess Bring-Larsen (jebl)]

Resolved in this case by entering another foldername (e.g. deja-dup/T500-laptop) in the storage options menu. It was not obvious though ;)

[Christopher O. Nash (conwrite)]

I created another folder to backup data in as suggested above. However, now I have two folders with Backup data. They have almost identical content at this point. The program is working again, but will I need to create a 3rd folder soon? If I go back and select the original folder, I get the 500 error again. 8-(

[Michael Terry (mterry)]

OK, so this clearly seems to be some bug with Ubuntu One's servers accessing that particular file. The server folks are subscribed to this bug, hopefully they can help. But good that there's a workaround.

[Christopher O. Nash (conwrite)]

I don't mean to sound negative Michael, just daily dramas adding up I guess. Much thanks for your support. And yeah, I'm just a know-nothing user, but it seems like the issue to me is with U1.

[Hans Harhoff Andersen (hansharhoff)]

I just got an error 500 with an oops id:
Got status code 500
Oops-ID: 2132appserverZGebGddICDeBAEaJfJDeBbDJGdABAGACf407302

I am backing up ~40 GB of data to Ubuntu one and have gotten that several times (after uploading several gb each time). I am not sure whether deja dup is starting over everytime or whether it is picking up where it left off. I have been running on and off for almost a week now and I still don't think my files are backup up.

[Martin Albisetti (beuno)]

Thanks for the oops id hans, I'll chase this.

[Martin Albisetti (beuno)]

So, the error is the following (sorry, private, here for the developers): https://pastebin.canonical.com/55249/

It's essentially a locking problem on the database, which points to 2 write operations happening very close together.
Michael, is it possible deja dup is doing parallel operations?

If not, is there a way to reproduce this problem consistently? If there is, we can spend some time debugging on our end what's causing the lock-up.

[John Lenton (chipaca)]

On Wed, 02 Nov 2011 19:27:21 -0000, Martin Albisetti <email address hidden> wrote:
> So, the error is the following (sorry, private, here for the
> developers): https://pastebin.canonical.com/55249/
>
> It's essentially a locking problem on the database, which points to 2 write operations happening very close together.
> Michael, is it possible deja dup is doing parallel operations?
>
> If not, is there a way to reproduce this problem consistently? If
> there is, we can spend some time debugging on our end what's causing the
> lock-up.
>
> --
> You received this bug notification because you are a member of Ubuntu
> One, which is subscribed to Ubuntu One Servers.
> https://bugs.launchpad.net/bugs/882699
>
> Title:
> Déjà Dup fails with "Got status code 500" when starting backup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/deja-dup/+bug/882699/+subscriptions

we have considerable contention on that table (look at the oops
reports), which is one of the main reasons we're refactoring the file
sync servers (which has triggered some performance regressions).

So. Working on it.

[Chris Hudson (mindzeebeez-b)]

I get the same error code whilst trying to restore my system after a fresh install because of a video driver bug.
Not sure if it's a problem with Ubuntu One, where my files are stored, or Deja Dup.
Please, at the risk of sounding ignorant here, are the files Deja Dup restores (almost my full 5GB allowance of free storage here,) those same files I can see in my Ubuntu One folder? Couldn't I just manually copy them across if I can't get Deja Dup to work?

[Michael Terry (mterry)]

Chris, here are steps for manual recovery, if you can't get Deja Dup to work: http://live.gnome.org/DejaDup/Help/Restore/WorstCase

[Chris Hudson (mindzeebeez-b)]

Thanks mterry, in fact it did restore my files eventually after a lot of fiddling, before I saw your link in fact. Have same error code 500 now with Precise Pangolin trying to back up however.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Benedict Holland (benedict-m-holland)]

Adding to the fray. This worked perfectly for me in 11.12 and broke in 12.04 apparently with the upgrade. I am creating a new folder and changing backup location. This bug should be considered critical mostly because users (such as myself) do pay for this service and the nature of this service is critical.

If you need any more help with testing this let me know. I can reproduce this bug every time on my system which is the default setup directly from install of 11.04 and currently runs 12.04.

[Benedict Holland (benedict-m-holland)]

There was another strange bug which happened when I created a new backup folder, it wouldn't backup. It would sit there a spin and use all of my ram and eventually crash my computer. I didn't back up for about 2 months which was terribly disappointing and very dangerous for me. I wish someone had said that this is the fix:

1) log onto the Ubuntu One account and remove from sink all of your backup folders
2) start "Backup" (deja-dupe)
3) configure it to back up whatever folders you want
4) hit start and this will create a new fresh backup.

This is not ideal as it wipes the previous set and the upload of around 15GB isn't a trivial amount of time but this is far better than getting a 500 error or crashing my computer. Hopefully a new backup will not be required every time I upgrade ubuntu but for now it seems to work well.

[Neil Woolford (neil-neilwoolford)]

Don't like to post impatiently, but is there any idea of timescale for resolving this?

It's plagued my attempts to use DejaDup with Ubuntu One; having to apply the folder change workaround once would be bearable, but the problem has returned for me with the new folder name.

If there isn't a prospect of a timely fix I'm going to have to consider installing the S3 extension(s) for DejaDup and going over to using Amazon directly, or possibly the FTP version to my web hosting.

But really I'd prefer to use Ubuntu One, and to move several others to it. But I can't at the moment...

[rac (justwtf)]

I second that fully, and would be happy to help with debugging where I can.

[Eric Ongerth (ericongerth)]

I third that... Ubuntu backup (deja-dup to Ubuntu One) has not worked for me for many months due to this bug, and after so much time I think I probably need to just stop waiting for a fix and FTP or SSH to my own web host. But I already do that, and I was thinking of Ubuntu One as a very nice additional and automatic backup.

I'm sorry it's not working. I'm not going to change backup folders every few days to try to keep it working. I am on a fresh clean install of 12.04. I wish the teams involved the best of luck in working it out and I only wish I had the specific expertise to help.

[Michael Terry (mterry)]

Martin, you asked some questions of me last year, but I did not notice them until now.

> Michael, is it possible deja dup is doing parallel operations?

It shouldn't be. It prevents the user from doing two backups at the same time. And it doesn't upload more than one item at a time.

> If not, is there a way to reproduce this problem consistently? If there is, we can spend some time debugging on our end what's causing the lock-up.

No reliable way to reproduce to my knowledge. Though some people say it is happening very frequently.

[Slick (slick666)]

To throw my two cents in I ran into.the same problem but after deleting and
re-creating the backup it hasn't happened since. Sorry to the deb's for not
making my machine available but it is my primary laptop an couldn't afford
it to be down.

Michael & Martin, if you two can sync up and find the root of this I think
it would go a long way to moving deja-dup into a mature, reliable backup.

Landon
On Oct 25, 2012 12:45 PM, "Michael Terry" <email address hidden>
wrote:

> Martin, you asked some questions of me last year, but I did not notice
> them until now.
>
> > Michael, is it possible deja dup is doing parallel operations?
>
> It shouldn't be. It prevents the user from doing two backups at the
> same time. And it doesn't upload more than one item at a time.
>
> > If not, is there a way to reproduce this problem consistently? If
> there is, we can spend some time debugging on our end what's causing the
> lock-up.
>
> No reliable way to reproduce to my knowledge. Though some people say it
> is happening very frequently.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/882699
>
> Title:
> Déjà Dup fails with "Got status code 500" when starting backup
>
> Status in Déjà Dup Backup Tool:
> New
> Status in Ubuntu One Servers:
> Confirmed
> Status in “deja-dup” package in Ubuntu:
> Confirmed
>
> Bug description:
> LSB Version:
> core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch
> Distributor ID: Ubuntu
> Description: Ubuntu 11.10
> Release: 11.10
> Codename: oneiric
>
> deja-dup 20.1-0ubuntu0.1
> duplicity 0.6.15-0ubuntu2
>
>
> org.gnome.DejaDup backend 'u1'
> org.gnome.DejaDup delete-after 7
> org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
> org.gnome.DejaDup include-list ['/home/jbl/Dokumenter/Fritid/MTB']
> org.gnome.DejaDup last-backup ''
> org.gnome.DejaDup last-restore ''
> org.gnome.DejaDup last-run ''
> org.gnome.DejaDup periodic true
> org.gnome.DejaDup periodic-period 7
> org.gnome.DejaDup prompt-check '2011-10-13T18:07:01.661276Z'
> org.gnome.DejaDup root-prompt true
> org.gnome.DejaDup welcomed true
> org.gnome.DejaDup.File icon ''
> org.gnome.DejaDup.File name ''
> org.gnome.DejaDup.File path ''
> org.gnome.DejaDup.File relpath @ay []
> org.gnome.DejaDup.File short-name ''
> org.gnome.DejaDup.File type 'normal'
> org.gnome.DejaDup.File uuid ''
> org.gnome.DejaDup.Rackspace container 'jbl-laptop'
> org.gnome.DejaDup.Rackspace username ''
> org.gnome.DejaDup.S3 bucket ''
> org.gnome.DejaDup.S3 folder 'jbl-laptop'
> org.gnome.DejaDup.S3 id ''
> org.gnome.DejaDup.U1 folder '/deja-dup/jbl-laptop'
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/deja-dup/+bug/882699/+subscriptions
>

[Neil Woolford (neil-neilwoolford)]

Ok. To enlarge on my experience, the sequence of events is as follows;

I set up Deja Dup to back up to a named folder on U1.

My machine scans, prepares and uploads files.

A successful backup is reported, there are uploaded files on U1, including various control files. All appears good.

Future backups may well run correctly.

However, if an attempt to backup results in the code 500 error, that is the end of backing up to the named folder. Future attempts will not work.

Thus, once code 500 has been encountered it is a fatal error for that backup setup.

The only cure appears to be to start again with a new destination folder.

So the error is reproducible once it has started to occur.

[Zisu Andrei (matzipan)]

Hey, devs, seriously, how long does it take to make deja dup a fucking competitive product? I see this error has been around for a year now.

I cannot wait to get Google Drive on Ubuntu.

[Zisu Andrei (matzipan)]

And I have it too after it scans the filesystems and attempts to uplaod the files.

[Humphrey van Polanen Petel (hpvpp)]

After suggestion https://bugs.launchpad.net/deja-dup/+bug/882699/comments/5 I created another folder ("also-dup/David") on Ubuntu One and everything appeared to be working. It was backing up for a while, but this morning I got this "code 500" error again. So that work-around didn't work for me.

[Zisu Andrei (matzipan)]

Ubuntu one team... I might be paying for your service if it would at least work. Do something.

[Zisu Andrei (matzipan)]

Did a distupgrade for 13.04. The error is now something like (not exact text) "Gave up after 5 retries. Error 500"

[teledyn (garym-teledyn)]

I'm not sure I have ever seen Deja-Dup work, and it certainly doesn't work now. Adding a comment here only on the chance that someday it may get fixed and I can finally find out what it is intended to do.

[David Jakstys (david-jakstys)]

Is there some other way to backup this wonderful system?

David

________________________________
 From: teledyn <email address hidden>
To: <email address hidden>
Sent: Saturday, March 30, 2013 7:53 PM
Subject: [Bug 882699] Re: Déjà Dup fails with "Got status code 500" when starting backup

I'm not sure I have ever seen Deja-Dup work, and it certainly doesn't
work now.  Adding a comment here only on the chance that someday it may
get fixed and I can finally find out what it is intended to do.

--
You received this bug notification because you are subscribed to a
duplicate bug report (1129321).
https://bugs.launchpad.net/bugs/882699

Title:
  Déjà Dup fails with "Got status code 500" when starting backup

Status in Déjà Dup Backup Tool:
  New
Status in Ubuntu One Servers:
  Confirmed
Status in “deja-dup” package in Ubuntu:
  Confirmed

Bug description:
  LSB Version:    core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch
  Distributor ID:    Ubuntu
  Description:    Ubuntu 11.10
  Release:    11.10
  Codename:    oneiric

  deja-dup    20.1-0ubuntu0.1
  duplicity    0.6.15-0ubuntu2

  org.gnome.DejaDup backend 'u1'
  org.gnome.DejaDup delete-after 7
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
  org.gnome.DejaDup include-list ['/home/jbl/Dokumenter/Fritid/MTB']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup last-run ''
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 7
  org.gnome.DejaDup prompt-check '2011-10-13T18:07:01.661276Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup welcomed true
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.Rackspace container 'jbl-laptop'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'jbl-laptop'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.U1 folder '/deja-dup/jbl-laptop'

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/882699/+subscriptions

[Phil Dobbin (bukowskiscat)]

On 04/01/2013 12:38 PM, David Jakstys wrote:

> Is there some other way to backup this wonderful system?

It works fine to S3 via Deja Dup. Cheaper too.

Cheers,

  Phil...

--
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal
GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc

[David Jakstys (david-jakstys)]

Phil, What do you mean S3?

David

________________________________
 From: Phil Dobbin <email address hidden>
To: <email address hidden>
Sent: Tuesday, April 2, 2013 3:40 AM
Subject: Re: [Bug 882699] Re:Déjà Dup fails with "Got status code 500" when starting backup

On 04/01/2013 12:38 PM, David Jakstys wrote:

> Is there some other way to backup this wonderful system?

It works fine to S3 via Deja Dup. Cheaper too.

Cheers,

  Phil...

--
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal
GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc

--
You received this bug notification because you are subscribed to a
duplicate bug report (1129321).
https://bugs.launchpad.net/bugs/882699

Title:
  Déjà Dup fails with "Got status code 500" when starting backup

Status in Déjà Dup Backup Tool:
  New
Status in Ubuntu One Servers:
  Confirmed
Status in “deja-dup” package in Ubuntu:
  Confirmed

Bug description:
  LSB Version:    core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch
  Distributor ID:    Ubuntu
  Description:    Ubuntu 11.10
  Release:    11.10
  Codename:    oneiric

  deja-dup    20.1-0ubuntu0.1
  duplicity    0.6.15-0ubuntu2

  org.gnome.DejaDup backend 'u1'
  org.gnome.DejaDup delete-after 7
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
  org.gnome.DejaDup include-list ['/home/jbl/Dokumenter/Fritid/MTB']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup last-run ''
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 7
  org.gnome.DejaDup prompt-check '2011-10-13T18:07:01.661276Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup welcomed true
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.Rackspace container 'jbl-laptop'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'jbl-laptop'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.U1 folder '/deja-dup/jbl-laptop'

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/882699/+subscriptions

[Phil Dobbin (bukowskiscat)]

On 04/02/2013 04:51 PM, David Jakstys wrote:

> Phil, What do you mean S3?

Amazon S3. Just sign up for it & get your secret key/ID details & then
enter them in Deja Dup. I schedule mine to run every night at 01:00hrs.
It hasn't failed so far in over nine months.

I pay around $4 a month for about half a dozen machines. I only use S3
to back up $HOME/. For full backups I use a mixture of Mondoarchive &
Clonezilla dependant on the distro.

Cheers,

  Phil...

--
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal
GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc

[jori lahteela (jori-lahteela-w)]

Hello!

I am having the same problem using Deja Vu and Ubuntu One cloud service. It was working well and now suddenly it popped out the error message. (i read the messages above and changing the folder is only the temporary cure)

My laptop is :
Release 12.04 (precise) 64-bit
Kernel Linux 3.8.0-26-generic
GNOME 3.4.2
Memory: 7,7 GiB
Processor: Intel® Core™ i5-2540M CPU @ 2.60GHz × 4
Model: ThinkPad T420s

Thanks for any help!

-Jori

[David Jakstys (david-jakstys)]

I don't know Jori.  The Ubuntu Community is being uncharacteriously silent.  I have Intel dual core stuff also which it usually does so well with.  I will let you know if I hear anything.

David

________________________________
 From: jori lahteela <email address hidden>
To: <email address hidden>
Sent: Monday, September 30, 2013 8:50 PM
Subject: [Bug 882699] Re: Déjà Dup fails with "Got status code 500" when starting backup

Hello!

I am having the same problem using Deja Vu and Ubuntu One cloud service.
It was working well and now suddenly it popped out the error message. (i
read the messages above and changing the folder is only  the temporary
cure)

My laptop is :
Release 12.04 (precise) 64-bit
Kernel Linux 3.8.0-26-generic
GNOME 3.4.2
Memory: 7,7 GiB
Processor: Intel® Core™ i5-2540M CPU @ 2.60GHz × 4
Model: ThinkPad T420s

Thanks for any help!

-Jori

--
You received this bug notification because you are subscribed to a
duplicate bug report (1129321).
https://bugs.launchpad.net/bugs/882699

Title:
  Déjà Dup fails with "Got status code 500" when starting backup

Status in Déjà Dup Backup Tool:
  New
Status in Ubuntu One Servers:
  Confirmed
Status in “deja-dup” package in Ubuntu:
  Confirmed

Bug description:
  LSB Version:    core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch
  Distributor ID:    Ubuntu
  Description:    Ubuntu 11.10
  Release:    11.10
  Codename:    oneiric

  deja-dup    20.1-0ubuntu0.1
  duplicity    0.6.15-0ubuntu2

  org.gnome.DejaDup backend 'u1'
  org.gnome.DejaDup delete-after 7
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
  org.gnome.DejaDup include-list ['/home/jbl/Dokumenter/Fritid/MTB']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup last-run ''
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 7
  org.gnome.DejaDup prompt-check '2011-10-13T18:07:01.661276Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup welcomed true
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.Rackspace container 'jbl-laptop'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'jbl-laptop'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.U1 folder '/deja-dup/jbl-laptop'

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/882699/+subscriptions

[isomorphismes (isomorphismes)]

I'm still having this problem in 2014.

[isomorphismes (isomorphismes)]

bump

[Martin Albisetti (beuno)]

Ubuntu One is being shut down, so this is no longer expected to work: http://blog.canonical.com/2014/04/02/shutting-down-ubuntu-one-file-services/