After further investigation, notifications to make it from apps in a
Libertine container to U8. The problematic case is using notify-send
from within the container.
The way NotificationServer tries to figure out if notify-send is being
used is not compatible with using it in a container. NotificationServer
uses a function called isCmdLine() which checks if a pid's path is the
notify-send path, but this does not work in an LXC due to namespacing.
It would probably be better to check if the notifications app_name is
"notify-send" instead.
I will probably open a new bug against unity-notifications to see about
changing the behavior for isCmdLine(). In the meantime, I'm closing
this bug Invalid.
** Changed in: libertine (Ubuntu)
Status: New => Invalid
** Changed in: unity8 (Ubuntu)
Status: New => Invalid
** Changed in: canonical-devices-system-image
Status: New => Invalid
--
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:
Invalid
Status in libertine package in Ubuntu:
Invalid
Status in unity8 package in Ubuntu:
Invalid
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
