After client update, the changes aren't applied (even after restarting the applet)

[Tom Haddon]

I was getting the "capabilities mismatch" notice in my client. I just finished updating to the versions in karmic-updates that fixed this, however the client wasn't restarted as part of the update process. I was still getting the same "capabilities mismatch" after quitting the applet and restarting Ubuntu One from the Applications -> Internet menu. After restarting my machine, the client is now working and I'm no longer seeing the "capabilities mismatch".

Surely the package upgrade should either restart the client, or prompt for a restart.

[Rick McBride (rmcbride)]

Agreed. We absolutely should be restarting the client when the package is updated.

I suggested this early on, but at the time the suggestion was that the user session should be restarted, since the Nautilus plugin cannot be updated when an update occurs. Now that we're out of BETA, the Nautilus plugin should not change frequently, and teh user should not be forced to stop working in their current session and re-log to update the client.

[Rick McBride (rmcbride)]

s/at the time the suggestion/at the time the counter-arguement/

[Natalia Bidart (nataliabidart)]

I've also experienced this. Besides, the "capabilities mismatch" message says that *the server* needs upgrade, not the client. Very confusing!

Attached an screenshot of the misleading message.

[Rick McBride (rmcbride)]

Basically we will have two package upgrade scenarios:

1) Most often there will be no change to the Nautilus plugin. In this case all instances of the syncdaemon/applet on the system should be terminated and then the client should start at the end of the process. User should not need to re-log/restart.

2) If the Nautilus plugin does get updated, we should prompt the user to re-log/restart. There's a flag that is set, or some method used to let upgrade-manager throw a dialog indicating that the system needs to be restarted for some updates to take effect. We should use that.

This way we can make sure that telling the user to upgrade their packages will actually fix the problem, without forcing them to interrupt their work in every single case where they upgrade.

[Stuart Langridge (sil)]

desktopcouch also needs to be restarted on a package upgrade, and we have the same issue (a system-level install restarting user processes), so using the same method would seem ideal. Don't block this bug on desktopcouch implementation, but do please assign to desktopcouch when complete so that we can tie into the signal or add our processes to those that are HUPped or whatever is used to make the processes restart.

[Alberto (albertomi)]

I've restarted my computer but I still have this message in Ubuntu One

[Jun Geng (jun)]

I restart several times, I still get the same message as Naty Bidart.

[Alberto (albertomi)]

After update, It's solved in my computer.

[Jun Geng (jun)]

I downgrade from 1.1* (ppa repository) to 1.0.2 (officially supported). Everything is OK now.