Ubuntu One Broken

[dominus_sapiens]

Binary package hint: ubuntuone-client

The notification icon does not show the same information as the "Connect" box in the Ubuntu One folder, changing various options, such as whether the client connects on startup, does nothing to affect the actual behaviour of the application and synchronisation of files is shaky at best. In addition to this, the client often breaks or crashes without so much as an error message or sign that something is wrong. I made the big mistake of using Ubuntu One to transfer data from my home computer to my system at University. Well, silly me just lost two days' worth of work! This is not good.

It seems to decide at random whether to update files to the ones available online, which it did at first, or to use the ones available on the system that is being used which is all well and good up until you connect a new computer with an empty folder to the account. What it has done in this situation is delete all my stored files and now, despite me replacing them with older versions on another hard drive and having the client "update" for quite some time, there is still virtually nothing stored online. This is also not good.

I have spent many hours trying to get this to work, which is not a nice experience with approaching deadlines, and now I have to do my work all over again. I am not very happy with this and, for my part, will strongly advise anyone I encounter to avoid this piece of software!

ProblemType: Bug
.home.david..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = False
 connect = 0
 show_applet = 1
 bookmarked = True
Architecture: amd64
Date: Mon Nov 16 21:51:03 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic x86_64

[Joshua Hoover (joshuahoover)]

Hi Dominus,

I apologize for the inconvenience Ubuntu One has caused you. We are continually improving the software and appreciate your patience and willingness to help us make it better by using it and taking the time to submit bug reports. I'm going to assign this to a developer to look into further. It will likely be helpful if you can also attach the following log file to this bug report: ~/.cache/ubuntuone/log/syncdaemon.log

Thank you,

Joshua

[Joshua Hoover (joshuahoover)]

Hi Dominus,

I re-read your report and noticed you said the following which is very concerning:

"It seems to decide at random whether to update files to the ones available online, which it did at first, or to use the ones available on the system that is being used which is all well and good up until you connect a new computer with an empty folder to the account. What it has done in this situation is delete all my stored files..."

Did you have this problem just recently (within the past 3 weeks or so)? There was a known issue that we fixed that exhibited similar behavior. If so, can you please attach the ~/.cache/ubuntuone/log/syncdaemon.log files from these other computers as well and label them in a way that we can identify which log file goes to which computer (something like: computer1, computer2, etc.)

Thank you,

Joshua

[dominus_sapiens (dominussapiens)]

Thanks for the quick reply Joshua. Unfortunately the fact that made the problem so frustrating was that I no longer have access to the other machine and won't have for quite some time, though I have attached the log from the laptop. The main problem, I believe, is not so much in the way of a faulty app but one that doesn't really offer enough feedback as to what it is actually doing; if it did so it would probably remove a great deal of worry and nervous disconnecting and reconnecting from the users.

The problem was encountered at about an hour before the posting of the error report, so on around the 16th November, if it's any help.

[Joshua Hoover (joshuahoover)]

Hi Dominus,

Thank you for the quick reply! We have an idea on what the problem is based on your logs. Unfortunately, we need to have debug logs in order to get more information about what is going on. If you could, please try the following:

1. Open (or create if it doesn't exist): ~/.config/ubuntuone/syncdaemon.conf
2. Add the following 2 lines to this file and save:
      [__main__]
      log_level = DEBUG
3. Restart the Ubuntu One client

If Ubuntu One is showing some syncing activity - great! If not, you'll need to try to reproduce the problem by syncing more files/folders. Once you've done this, please attach the ~/.config/ubuntuone/syncdaemon.conf file(s) to this bug report and we'll look into them.

Thank you,

Joshua

[dominus_sapiens (dominussapiens)]

Hmm, it doesn't seem to connect after I try this. I have attached the syncdaemon.conf file as requested along with the new syncdaemon.log. I hope it helps!

[Joshua Hoover (joshuahoover)]

Hi Dominus,

It appears your ~/.config/ubuntuone/syncdaemon.conf has some spaces in it before you pasted the following to it. That is my fault. My apologies. Please replace the contents of your ~/.config/ubuntuone/syncdaemon.conf file with the following (with no spaces before either line):

[__main__]
log_level = DEBUG

Then restart the Ubuntu One client and try to sync your files. Then attach ~/.cache/ubuntuone/log/syncdaemon.log

Thank you,

Joshua

[Facundo Batista (facundo)]

dominus_sapiens: your logs seem to be find. However, there're some errors related to the debug lines you added.

Please, do not leave any spaces at the beginning of the lines in the file.

Like:

[__main__]
log_level = DEBUG

and then follow Joshua's instructions.

Thanks for your time and help!

[dominus_sapiens (dominussapiens)]

Here we go. Looks like it worked this time.

[dominus_sapiens (dominussapiens)]

It actually seems to be working fine from this computer at the moment, it's just the transition between two different machines that I think caused the problem.

[ivn (ivanpassport)]

> Date: Thu, 19 Nov 2009 13:46:48 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 483850] Re: Ubuntu One Broken
>
> Hmm, it doesn't seem to connect after I try this. I have attached the
> syncdaemon.conf file as requested along with the new syncdaemon.log. I
> hope it helps!
>
> ** Attachment added: "syncdaemon.conf"
> http://launchpadlibrarian.net/35853240/syncdaemon.conf
>
> --
> Ubuntu One Broken
> https://bugs.launchpad.net/bugs/483850
> You received this bug notification because you are subscribed to Ubuntu
> One Client.
>
> Status in Ubuntu One Client: Incomplete
> Status in “ubuntuone-client” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: ubuntuone-client
>
> The notification icon does not show the same information as the "Connect" box in the Ubuntu One folder, changing various options, such as whether the client connects on startup, does nothing to affect the actual behaviour of the application and synchronisation of files is shaky at best. In addition to this, the client often breaks or crashes without so much as an error message or sign that something is wrong. I made the big mistake of using Ubuntu One to transfer data from my home computer to my system at University. Well, silly me just lost two days' worth of work! This is not good.
>
> It seems to decide at random whether to update files to the ones available online, which it did at first, or to use the ones available on the system that is being used which is all well and good up until you connect a new computer with an empty folder to the account. What it has done in this situation is delete all my stored files and now, despite me replacing them with older versions on another hard drive and having the client "update" for quite some time, there is still virtually nothing stored online. This is also not good.
>
> I have spent many hours trying to get this to work, which is not a nice experience with approaching deadlines, and now I have to do my work all over again. I am not very happy with this and, for my part, will strongly advise anyone I encounter to avoid this piece of software!
>
> ProblemType: Bug
> .home.david..config.ubuntuone.ubuntuone.client.conf:
> [ubuntuone]
> connected = False
> connect = 0
> show_applet = 1
> bookmarked = True
> Architecture: amd64
> Date: Mon Nov 16 21:51:03 2009
> DistroRelease: Ubuntu 9.10
> InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
> NonfreeKernelModules: nvidia
> Package: ubuntuone-client 1.0.2-0ubuntu2
> PackageArchitecture: all
> ProcEnviron:
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
> SourcePackage: ubuntuone-client
> Uname: Linux 2.6.31-14-generic x86_64

I
do not understand how you can help me because I do not speak English I
would like to learn if you have patience you listening. This is a
translation of google translator

_________________________________________________________________
Messenger su ogni PC, prova la Web Bar!
http://www.messenger.it/

[Vincenzo Di Somma (vds)]

ivn: potresti provare a descrivere il problema in italiano?

[Rick McBride (rmcbride)]

dominus_sapiens, were you able to get the second machine working by making the same changes?

[dominus_sapiens (dominussapiens)]

It seems to be working OK so far; I just need to get used to the way it transfers files. The notification icon, however, is still causing problems as far as I'm aware. The issue seems to occur when it's disconnected while performing an operation in which case the notification icon and the button in the "Ubuntu One" folder show different information and neither will respond to any prompting. Being aware of this issue, however, has prevented it becoming a problem most of the time.

[Facundo Batista (facundo)]

Dobey, I'm reassigning this to you as it decanted in a notification icon issue.

[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 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 483850 and any other logs that are relevant for this particular issue.