Ubuntu One client showed an X. I clicked on it and the bug report was sent automatically. I no longer see the Ubuntu One gadget in the task bar

[Stew]

Binary package hint: ubuntuone-client

stewart@Lenny:~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

What I did: I had upgraded to 10.4 beta, but had problems with Firefox dieing. I reinstalled 9.10 dual boot. On entry to my account, the Ubuntu One client in the task bar showed a red X. I clicked it. The icon disappeared and the but report was generated.

What I expected: Almost anything but that.

ProblemType: Bug
.home.stewart..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 0
 write_limit = 0
 on = False
.home.stewart..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = True
 connect = 0
 show_applet = 1
 bookmarked = True
Architecture: i386
Date: Sat Apr 10 21:48:25 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic-pae
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-20-generic-pae i686

[Mitch Towner (kermiac)]

I'm sorry to hear Ubuntu One isn't working properly for you. Can you try the following and let me know the results?
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

You should be connected after you follow these steps. If you are not connected, can you please attach your Ubuntu One logs to this bug report? Please zip your $HOME/.cache/ubuntuone/log/ folder and attach the zip here.?

Thanks in advance!

[Stew (stew-schneider)]

Mitch Towner wrote:
> I'm sorry to hear Ubuntu One isn't working properly for you. Can you try the following and let me know the results?
> 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
>
stewart@Lenny:~$ u1sdtool -q
ubuntuone-syncdaemon still running.
stewart@Lenny:~$ sudo u1sdtool -q
[sudo] password for stewart:
ubuntuone-syncdaemon still running.
stewart@Lenny:~$ u1sdtool -q
ubuntuone-syncdaemon still running.
stewart@Lenny:~$

> 2. Delete the old metadata. In a Terminal run.
>
> rm -rf ~/.local/share/ubuntuone
>
stewart@Lenny:~$ ps aux|grep ubuntuone
stewart 14240 0.5 0.5 49580 22980 ? Sl 19:48 0:00
/usr/bin/python /usr/bin/ubuntuone-client-applet
stewart 14360 0.0 0.0 3040 800 pts/0 S+ 19:50 0:00 grep
ubuntuone
stewart@Lenny:~$ kill 14240
stewart@Lenny:~$ ps aux|grep ubuntuone
stewart 14364 0.0 0.0 3040 788 pts/0 R+ 19:50 0:00 grep
ubuntuone
stewart@Lenny:~$ rm -fr /home/stewart/.local/share/ubuntuone/

> 3. Start Ubuntu One as you normally would Applications > Internet >
> Ubuntu One
>
->Ubuntu One is now updating your files.

HTH
stew
> You should be connected after you follow these steps. If you are not
> connected, can you please attach your Ubuntu One logs to this bug
> report? Please zip your $HOME/.cache/ubuntuone/log/ folder and attach
> the zip here.?
>
> Thanks in advance!
>
> ** Changed in: ubuntuone-client (Ubuntu)
> Status: New => Incomplete
>
>

--
J. Stewart Schneider, J.D.
Stated Supply Pastor
Community Presbyterian Church of Bellefonte
http://CommunityPresbyterian.org
http://commpresbyterian.blogspot.com/
God does peace work. Shouldn't you?

[Mitch Towner (kermiac)]

Hi Stew. I am happy to see that your issue has now been resolved. I am uncertain why "u1sdtool -q" did not quit the syncdaemon for you. However, deleting ~/.local/share/ubuntuone appears to have resolved your metadata issue.

This particular bug has already been reported and is a duplicate of bug 517505, 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.