Just to put my notes in here from when I investigated, I ran dbus-
monitor on the host side session bus listening on the
org.freedesktop.Notifications interface.
This is the output of dbus-monitor when running notify-send from within
the container:
method call time=1472222077.981441 sender=:1.181 -> destination=:1.25 serial=6
path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications;
member=GetServerInformation
method call time=1472222077.983315 sender=:1.181 -> destination=:1.25 serial=7
path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications;
member=Notify
string "notify-send"
uint32 0
string ""
string "Hello"
string ""
array [
]
array [
dict entry(
string "urgency"
variant byte 1
)
]
int32 -1
signal time=1472222077.999079 sender=:1.25 -> destination=(null destination)
serial=89 path=/org/freedesktop/Notifications;
interface=org.freedesktop.Notifications; member=NotificationClosed
uint32 1
uint32 1
signal time=1472222077.999136 sender=:1.25 -> destination=(null destination)
serial=90 path=/org/freedesktop/Notifications;
interface=org.freedesktop.Notifications; member=NotificationClosed
uint32 1
uint32 1
This is the output of running notify-send outside of the container:
method call time=1472222189.263495 sender=:1.185 -> destination=:1.25 serial=6
path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications;
member=GetServerInformation
method call time=1472222189.264778 sender=:1.185 -> destination=:1.25 serial=7
path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications;
member=Notify
string "notify-send"
uint32 0
string ""
string "Hello"
string ""
array [
]
array [
dict entry(
string "urgency"
variant byte 1
)
]
int32 -1
signal time=1472222194.345422 sender=:1.25 -> destination=(null destination)
serial=119 path=/org/freedesktop/Notifications;
interface=org.freedesktop.Notifications; member=NotificationClosed
uint32 2
uint32 1
As you can see, in the failing case, there are 2 NotificationClosed
signals emitted almost immediately. In the good case the
NotificationClosed signal is emitted after ~5 seconds, which is
expected.
Not sure why the failing case gets the NotificationClosed signals
immediately. I see nothing in the unity8.log.
--
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/1617335
Title:
notifications not making their way to unity8 from libertine
Status in Canonical System Image:
New
Status in libertine package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Bug description:
Not completely sure where this bug lies.
This was an area of "this should just work" in theory.
We did perform some investigation using notification but it's not clear if
the msg is somehow getting lost on in dbus or if unity8 is somehow
rejecting/ignoring.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617335/+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
