Public bug reported:

Steps to reproduce:

1. In Notification.qml add:

  Component.onDestruction { console.log("Notification onDestruction"); }

  and a similar log message in Component.onCompleted.
2. Install dialer-app-autopilot on the phone. This installs a fake phone sim, 
that, among other things, creates a fake voice mail every time unity8 starts.
3. Restart unity8.
4. A notification is created for the voice mail,  before unity8 is fully drawn. 
No bubble can be seen, only the green envelope on top. Note that in 
~/.cache/upstart/unity8.log the notification onCompleted log message can be 
seen, but not an onDestruction message.
5. stop unity8. Note that ~/.cache/upstart/unity8.log now contains the 
onDestruction message.

Effectively the initial notification is somehow "leaked" and not
destroyed until the end of the program. This presents a problem in the
new power architecture model, where unity8 needs to report both when a
notification is shown (it already does so) and when it is destroyed.

Notifications sent after unity8 has completed loading are properly
destroyed when their bubble disappears.

** Affects: unity8 (Ubuntu)
     Importance: Undecided
     Assignee: Michael Terry (mterry)
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1570922

Title:
  Initial notifications never shown and not destroyed until unity8 is
  stopped

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. In Notification.qml add:

    Component.onDestruction { console.log("Notification onDestruction");
  }

    and a similar log message in Component.onCompleted.
  2. Install dialer-app-autopilot on the phone. This installs a fake phone sim, 
that, among other things, creates a fake voice mail every time unity8 starts.
  3. Restart unity8.
  4. A notification is created for the voice mail,  before unity8 is fully 
drawn. No bubble can be seen, only the green envelope on top. Note that in 
~/.cache/upstart/unity8.log the notification onCompleted log message can be 
seen, but not an onDestruction message.
  5. stop unity8. Note that ~/.cache/upstart/unity8.log now contains the 
onDestruction message.

  Effectively the initial notification is somehow "leaked" and not
  destroyed until the end of the program. This presents a problem in the
  new power architecture model, where unity8 needs to report both when a
  notification is shown (it already does so) and when it is destroyed.

  Notifications sent after unity8 has completed loading are properly
  destroyed when their bubble disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1570922/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to