The user should be informed about the u1 file service shutdown

[Diego Sarmentero]

[Impact]
The client should:
- Show a message when the client is started indicating that the service will be suspended on June 1st.
- After June 1st, don't contact the server.

[Regression potential]
Minimal. This adds a new dialog, and shuts down the client after June 1. Since the service itself is offline after June 1, the risk of regression is small.

[Test case]
When running the client, you should see a pop-up letting you know the service is shutting down June 1st.
If you set your system clock into the future, after June 1st, the client should shut down instead of connecting to the server.

[Steve Langasek (vorlon)]

Hello Diego, or anyone else affected,

Accepted ubuntuone-client into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubuntuone-client/3.0.2-0ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Bryan Quigley (bryanquigley)]

I tried to test this.. but didn't see any message come up. A message should at boot right? (and not wait until june 1st?)

[dobey (dobey)]

I've tested this in a VM (where I did have some issues with notifications in general), and the notification does pop up, but seems to do so when the ubuntuone-syncdaemon process is told to quit, rather than at startup.

[Adam Conrad (adconrad)]

Hello Diego, or anyone else affected,

Accepted ubuntuone-client into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubuntuone-client/13.10-0ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[dobey (dobey)]

On 13.10 the notification pops up correctly when starting the client. So, I'm resolved to think the issue with the notification on 12.04 is part of a larger issue, and is not going to get fixed.

However, there is an issue with the syncdaemon when the date is set to one after June 1. The syncdaemon in this condition does avoid connecting to the server, but the process itself is not exiting cleanly. Also, the dbus service is not started, which leaves any client programs which interact with the syncdaemon, hanging until dbus times out, which can be a fairly long time. I've only tested with the command line tool u1sdtool, but I expect the ubuntuone-control-panel and Nautilus to hit similar problems in this situation.

[Adam Conrad (adconrad)]

Hello Diego, or anyone else affected,

Accepted ubuntuone-client into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubuntuone-client/13.10-0ubuntu1.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Adam Conrad (adconrad)]

Hello Diego, or anyone else affected,

Accepted ubuntuone-client into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubuntuone-client/3.0.2-0ubuntu2.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[dobey (dobey)]

This is working correctly for me now with the date set to after June 1 2014. In that case, the client does not connect (but does remain running locally, so that other applications will still work properly).

The notification on precise is not popping up on start, but rather does pop up on client exit, so there is likely a larger bug there that we don't have time to fix at this point. On saucy the notification is working on start up as expected.

I think it's good to push this update out as it is now, as June 1 is drawing very close, and this does prevent connection on and after that date.

[Adam Conrad (adconrad)]

The verification of the Stable Release Update for ubuntuone-client has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntuone-client - 3.0.2-0ubuntu2.2

---------------
ubuntuone-client (3.0.2-0ubuntu2.2) precise-proposed; urgency=medium

  * debian/patches/00_farewell-u1.patch:
    - Pop up a notice when connecting the service will stop on June 1 2014.
    - Avoid trying to connect after June 1 2014. (LP: #1306225)
 -- Rodney Dawes <email address hidden> Thu, 22 May 2014 21:26:57 -0400

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntuone-client - 13.10-0ubuntu1.2

---------------
ubuntuone-client (13.10-0ubuntu1.2) saucy-proposed; urgency=medium

  * debian/patches/00_farewell-u1.patch:
    - Pop up a notice when connecting the service will stop on June 1 2014.
    - Avoid trying to connect after June 1 2014. (LP: #1306225)
 -- Rodney Dawes <email address hidden> Thu, 22 May 2014 21:15:10 -0400