UST is doing the right thing here. The error arises as access to the
shared memory segment is mediated by AppArmor. For that, we should strip
all lttng tracepoints from production builds for QtUbuntu and the
Platform API.
** Also affects: platform-api
Importance: Undecided
Status: New
** Also affects: qtubuntu
Importance: Undecided
Status: New
** Changed in: qtubuntu
Assignee: (unassigned) => Ted Gould (ted)
** Changed in: platform-api
Assignee: (unassigned) => Ted Gould (ted)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ust in Ubuntu.
https://bugs.launchpad.net/bugs/1404302
Title:
liblttng-ust0 Error opening shm /lttng-ust-wait-5
Status in Platform API:
New
Status in QT Ubuntu:
New
Status in ust package in Ubuntu:
Confirmed
Bug description:
Confined apps don't have access to this and continuously produce this
error message in stderr:
libust[31283/31285]: Error: Error opening shm /lttng-ust-wait-5 (in
get_wait_shm() at lttng-ust-comm.c:958)
This is printed to the application's log about once every other second and
makes it hard to read the application's own debug output. For a better app
developer experience this message should be silenced.
To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1404302/+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
