Ubuntu Push Notifications

push client services initialization ordering wrong

Bug #1383867 reported by John Lenton on 2014-10-21

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu Push Notifications	Fix Released	High	John Lenton
	ubuntu-push (Ubuntu RTM)	Fix Released	Undecided	Unassigned

Bug Description

the push client exposes things on the bus before everything is ready, leaving a window for a crash to happen if a message comes in before we're ready to handle it.

Symptoms:
User does not receive notification of new OTA updates.

See original description

Tags:

Related branches

lp:~chipaca/ubuntu-push/fix-1383867

Merged into lp:ubuntu-push/automatic at revision 344

John Lenton (community): Approve on 2014-10-23

lp:~chipaca/ubuntu-push/fix-1383867--trunk

Merged into lp:ubuntu-push at revision 133

John Lenton (community): Approve on 2014-10-23

Revision history for this message

John Lenton (chipaca) wrote on 2014-10-21:

push-client.log Edit (38.7 KiB, text/plain)

as reproduced by davmor.

Jean-Baptiste Lallement (jibel) on 2014-10-22

tags:	added: rtm14
description:	updated

Revision history for this message

Julien Funk (jaboing) wrote on 2014-10-22:

This is important because we plan to have an OTA for our first users and this bug will block OTA from displaying properly if there is one available at first boot.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-10-24:

This bug was fixed in the package ubuntu-push - 0.64.1+14.10.20141023.2~rtm-0ubuntu1

---------------
ubuntu-push (0.64.1+14.10.20141023.2~rtm-0ubuntu1) 14.09; urgency=low

  [ John R. Lenton ]
  * make the common service Start(..) method take init, so we can listen
    for methods once everything is set up and not before. (LP: #1383867)

  [ Guillermo Gonzalez ]
  * Add ClearCookie method to the session and call it from
    handleAccountsChange.
-- Ubuntu daily release <email address hidden> Thu, 23 Oct 2014 20:17:12 +0000