nothing happens when i click on the ubuntu one icon from the menu or the me menu

I'm sorry to hear Ubuntu One is not working properly for you. If you would like to help debug the problem that would be greatly appreciated. You can do the following in order to provide important details that will help determine the root cause of this issue.

1) Quit the Ubuntu One client. Open Applications->Accessories->Terminal, then run the command:
u1sdtool -q

2) Run the following in the Terminal:
mv ~/.cache/ubuntuone/log ~/.cache/ubuntuone/log_old && mkdir ~/.cache/ubuntuone/log

3) Run the following in the Terminal to open/create this file:
gedit ~/.config/ubuntuone/syncdaemon.conf

#Add the following two (2) lines to this file and save:
[logging]
level.default = TRACE

4) Run the following in the Terminal to start the ubuntu one deamon/service:
u1sdtool -c

5) Let Ubuntu One run for a while, copy some files into your Ubuntu One Folder.
Then attach your ubuntuone logs to this bug. Please zip your $HOME/.cache/ubuntuone/log/ folder and attach the zip here.

You can attach logs to this bug report by clicking the 'Add Attachment or patch' button at the bottom of the page. Thank you for filing this bug report and helping to make Ubuntu better.

thanks for the help man..
i tried what you suggested and have attached the log files.
also when i try the third step there are lots of errors in the terminal and then the file opens.
the errors are as follows;-
and i tried opening the ubuntu one client again but nothing.
when i use the me menu nothing happens but when i use the preferences menu i get a minimized window in the bottom panel saying "Starting ubuntu one" but it disappears and nothing happens.

error: line 53087: bad flag vector alias
error: line 53088: bad flag alias index: 0
error: line 53088: bad flag vector alias
error: line 53090: bad flag alias index: 0
error: line 53090: bad flag vector alias
error: line 53094: bad flag alias index: 0
error: line 53094: bad flag vector alias
error: line 53095: bad flag alias index: 0
error: line 53095: bad flag vector alias
error: line 53096: bad flag alias index: 0
error: line 53096: bad flag vector alias
error: line 53097: bad flag alias index: 0
error: line 53097: bad flag vector alias
error: line 53098: bad flag alias index: 0
error: line 53098: bad flag vector alias
error: line 53099: bad flag alias index: 0
error: line 53099: bad flag vector alias
error: line 53101: bad flag alias index: 0
error: line 53101: bad flag vector alias
error: line 53103: bad flag alias index: 0
error: line 53103: bad flag vector alias
error: line 53104: bad flag alias index: 0
error: line 53104: bad flag vector alias
error: line 53105: bad flag alias index: 0
error: line 53105: bad flag vector alias
error: line 53106: bad flag alias index: 0
error: line 53106: bad flag vector alias
error: line 53107: bad flag alias index: 0
error: line 53107: bad flag vector alias
error: line 53108: bad flag alias index: 0
error: line 53108: bad flag vector alias
error: line 53109: bad flag alias index: 0
error: line 53109: bad flag vector alias
error: line 53110: bad flag alias index: 0
error: line 53110: bad flag vector alias
error: line 53111: bad flag alias index: 0
error: line 53111: bad flag vector alias
error: line 53112: bad flag alias index: 0
error: line 53112: bad flag vector alias
error: line 53115: bad flag alias index: 0
error: line 53115: bad flag vector alias
error: line 53116: bad flag alias index: 0
error: line 53116: bad flag vector alias
error: line 53117: bad flag alias index: 0
error: line 53117: bad flag vector alias
error: line 53119: bad flag alias index: 0
error: line 53119: bad flag vector alias
error: line 53120: bad flag alias index: 0
error: line 53120: bad flag vector alias
error: line 53121: bad flag alias index: 0
error: line 53121: bad flag vector alias
error: line 53122: bad flag alias index: 0
error: line 53122: bad flag vector alias
error: line 53123: bad flag alias index: 0
error: line 53123: bad flag vector alias
error: line 53124: bad flag alias index: 0
error: line 53124: bad flag vector alias
error: line 53125: bad flag alias index: 0
error: line 53125: bad flag vector alias
error: line 53126: bad flag alias index: 0
error: line 53126: bad flag vector alias
error: line 53127: bad flag alias index: 0
error: line 53127: bad flag vector alias
error: line 53128: bad flag alias index: 0
error: line 53128: bad flag vector alias
error: ...

Can you please check to see whether seahorse can start (Applications --> Accessories --> Passwords & Encryption Keys). Also please see whether starting gnome-keyring fixes this issue. This can be done by running "gnome-keyring" (without the quotes) from the run dialogue box (ALT+F2) or from a terminal window.

Thanks in advance!

seahorse window comes up but has the following written on the status bar..

Couldn't communicate with key ring daemon

and gnome-keyring in the terminal gives:-

karan@ubuntu:~$ gnome-keyring
usage: gnome-keyring command [options]
commands: import

Sorry for the confusion, that should have been "gnome-keyring-daemon"

Please run "gnome-keyring-daemon" (without the quotes) from a terminal window & then open Ubuntu One preferences as you normally would.

Thanks in advance!

karan@ubuntu:~$ gnome-keyring-daemon
GNOME_KEYRING_CONTROL=/tmp/keyring-lOPhyR
SSH_AUTH_SOCK=/tmp/keyring-lOPhyR/ssh
GNOME_KEYRING_PID=4020

the output of gnome-keyring-daemon is above..

and then the ubuntu one client worked like a charm..
what can i do to do this at boot(by default)..

I am glad to hear that has temporarily worked around your issue. Can you please do the following:

1. Go to System --> Preferences --> Startup Applications

2. Click on the Item: "Certificate and Key Storage" and then click on "Edit"

3.Paste the text from the text box next to "Command" into this bug report (See attached command.png screenshot)

4. Click on "cancel" & then close the "Startup Applications" window.

Thanks in advance!

the text in the command box is:-
gnome-keyring-daemon --start --components=pkcs11

Thank you for replying with the requested information. Please do the following & report your results:

1. Change this text in the text box (mentioned in comment #7 - see "command.png") from "gnome-keyring-daemon --start --components=pkcs11" to "gnome-keyring-daemon" (without the quotes)
2. Click on the "save" button.
3. Close "Startup Applications Preferences"
4. Restart your computer
5. Open Ubuntu One as you normally would

Please advise if Ubuntu One now works as expected after a reboot. Thanks in advance!

ubuntu one works after reboot.
but i get a dialog box asking for password everytime i restart..
the dialog box has something like this..

            Enter password to unlock your login keyring

            The login keyring did not get unlocked when you logged into your computer.

Is this due to the command i changed

Hi kps, I am glad the work-around has resolved your issue with gnome-keyring. I believe that you *may* be receiving the dialogue asking to unlock your keyring due to applying this workaround.

One way to overcome this issue is to reset your gnome keyring password by following the steps outlined at https://answers.edge.launchpad.net/ubuntu/+question/97580. When prompted to enter a new password, change it to be the same as your login password or leave it blank & click on the "OK" button.

i follow the steps but get stuck at this
apparently there is no such file;;

rm: cannot remove `default.keyring': No such file or directory

Just to tell that I also also am affected by this bug, and I noticed something:

- I configured my account in "users-admin" (System -> Administration -> Users and Groups) in such way that my user session can be started without my password to be entered manually.

- When I log in with this setting, then I open Seahorse (Applications -> Accessories -> Password and Encryption Keys), I get the same problem Mitch Towner ran in: Seahorse "couldn't communicate with key ring daemon". Ubuntu One doesn't work. I have to start "gnome-keyring-daemon" manually, then Seahorse can communicate with my key ring daemon, and Ubuntu One works again.

- Now, in "users-admin", I configure my user account to force my password to be entered for my user session to be started. I log out. I log in again, enter my account password in GDM, my session starts.

- In Seahorse, I don't have any error (Seahorse can communicate with my key ring daemon), and Ubuntu One works properly.

So, maybe Mitch Towner is in the same situation? Could this problem appear when a user can log in without a password?

If you need more information, logs, command outputs, etc., I'd be glad to send them.

Hi kps. Unfortunately I did not realise the keyring filename was changed in Lucid. Sorry for the confusion. Please follow these new instructions.

Copy & paste the following 2 commands into your terminal. This will delete your default keyring password.

cd ~/.gnome2/keyrings
rm default.keyring

Now you will need to reboot. When prompted to enter a new password, change it to be the same as your login password or leave it blank & click on the "OK" button.

Thanks in advance!

cd ~/.gnome2/keyrings
rm default.keyring

these are the same commands as the previous ones and i get the same error once again..

Sorry. Copy+Paste fail. The commands to try are:

cd ~/.gnome2/keyrings
rm login.keyring

i tried that now i get another dialog box saying the following:-
An application wants access to the keyring 'Default', but it is locked

Did you have anything else open that was accessing your keyring at the time?

This now appears to be a gnome-keyring related bug as opposed to an ubuntuone related bug.

Perhaps the following *may* work:
cd ~/.gnome2/keyrings
sudo rm login.keyring

Then reboot your computer

Making bug 567194 the master bug for this. 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.

thank you,
duanedesign