ubuntu-sdk-bugs team mailing list archive
-
ubuntu-sdk-bugs team
-
Mailing list archive
-
Message #06956
[Bug 1609616] [NEW] Alarm/AlarmModel should be confined per app
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
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1609616
Title:
Alarm/AlarmModel should be confined per app
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1609616/+subscriptions
Follow ups