Public bug reported:
Currently, when you use the AlarmModel and calendar apparmor policy,
your app can view, add, edit and delete alarms even those that were
created by other apps like for example the core clock app.
I think it would be better if the model only gives your app the permission to
view, edit and delete alarms created by your app. Then when the alarm is
triggered, the appropriate app will open and not alwayd the clock app.
This means that alarms in the AlarmModel can be distinguished by app and bot as
whole.
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609616
Title:
Alarm/AlarmModel should be confined per app
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1609616/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
