[Touch-packages] [Bug 1570922] Re: Initial notifications never shown and not destroyed until unity8 is stopped
> You can debug this a bit by adding more info into your onCompleted print:
> like "summary", "body", and "type". If type == 0, it's a
> placeholder (and summary and body will be empty). And you can ignore it if so.
Thanks for looking into this.
What I am seeing is indeed caused by this peculiar "placeholder"
notification. This is still a bug, in the sense that unity8 emits a
powerd notification event for a notification that's not real and this
confuses the new power daemon (repowerd). I will need to create a fix
for this issue in unity8.
** Changed in: unity8 (Ubuntu)
Status: Incomplete => Triaged
** Changed in: unity8 (Ubuntu)
Assignee: Michael Terry (mterry) => Alexandros Frantzis (afrantzis)
** Summary changed:
- Initial notifications never shown and not destroyed until unity8 is stopped
+ "Placeholder" notification emits powerd notification event
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1570922
Title:
"Placeholder" notification emits powerd notification event
Status in unity-notifications package in Ubuntu:
New
Status in unity8 package in Ubuntu:
Triaged
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/unity-notifications/+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
[Touch-packages] [Bug 1570922] Re: Initial notifications never shown and not destroyed until unity8 is stopped
Are you sure that you're testing was actually observing the voice mail
notification?
My *guess* is that the voice mail notification happened too early for
unity8 to see it, so it just went to the void. And the notification
you're seeing is actually the "placeholder" notification. Which unity-
notification creates and is just an empty notification with the
"placeholder" type.
"What the heck is a placeholder notification?" I hear you ask. Very
good question. I'm not 100% sure. It *seems* to be a hack to move the
notifications lower on the screen? But I don't know why that's not done
in the UI layer instead of in the notification model... Honestly, I
don't know if it has any good purpose. I didn't know about it until I
looked into this bug.
So... it might be confusing your testing.
You can debug this a bit by adding more info into your onCompleted
print: like "summary", "body", and "type". If type == 0, it's a
placeholder (and summary and body will be empty). And you can ignore it
if so.
** Changed in: unity8 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1570922
Title:
Initial notifications never shown and not destroyed until unity8 is
stopped
Status in unity-notifications package in Ubuntu:
New
Status in unity8 package in Ubuntu:
Incomplete
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/unity-notifications/+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
[Touch-packages] [Bug 1570922] Re: Initial notifications never shown and not destroyed until unity8 is stopped
** Also affects: unity-notifications (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1570922
Title:
Initial notifications never shown and not destroyed until unity8 is
stopped
Status in unity-notifications package in Ubuntu:
New
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/unity-notifications/+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
