remote_register_to_signals() error

[James Thorrold]

After updating Ubuntu One for Windows from the version previous to version 3.0.0 Ubuntu one no longer works. When launching the control panel, the client attempts to gather information. It continues to do this for several minutes before eventually displaying the following error message:

RemoteError
'remote_register_to_signals() takes exactly 2 arguments (3 given)'

I have attached a screenshot for clarity.

I have tried reinstalling the program, but this turns up the same results. I've also tried removing the ubuntuone folder in my user's 'AppData\Local\' folder, but this makes no difference.

If someone can let me know where the Ubuntu One logs are for the Windows client, i'll post those too.

If there's any info i've missed, let me know.

[Roberto Alsina (ralsina)]

Thanks for the bug report! This is probably caused by having some process from the old version and another from the new version running at the same time.

A reboot should clear it. Could you please confirm that it does? In the next version we will include a nicer solution.

[Brian Curtin (brian.curtin)]

This is because there is a mismatch between the ubuntuone-syncdaemon staying around from the older version and ubuntuone-control-panel from 3.0.0 after upgrading. Have you restarted your computer?

Unfortunately the upgrade process does not specify to restart nor does it stop the old Ubuntu One processes, but either restarting or stopping all existing ubuntuone processes should allow you to have a functioning Ubuntu One 3.0.0 installation.

[James Thorrold (jthorrold)]

Thanks for the quick replies! I've restarted the computer and it no longer throws that error now. However, I get another. I've seen that there have been reports for this in launchpad but none of the suggestions seem to fix it.

Would it be best to add to those bug reports instead of carrying on here?

thanks

[James Thorrold (jthorrold)]

oh, the error I get is:

AttributeError
"'NoneType' object has no attribute 'get_rootdir'"

[Doug Fultz (dougfultz)]

Rebooting fixed this bug for me, however I'm now getting another error message that I documented in Bug 985343.

[Rick McBride (rmcbride)]

James, yes, it would be best to follow up on the other error in related bugs, or to file a new report if nothing covers this new message.

Thanks for your report and followup.

[Dennis Shimer (dshimer)]

Rather than reboot, I first tried going into task manager and killing all tasks related to ubuntuone as there seemed to be a couple of strays. I then restarted UbuntuOne and for me this also worked fine.