AppArmor profile does not allow creating of ~/.cache/dconf
Bug #939126 reported by
David Edmundson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-mission-control-5 (Ubuntu) |
Fix Released
|
High
|
Jamie Strandboge | ||
Precise |
Won't Fix
|
High
|
Unassigned |
Bug Description
This causes telepathy-gabble (and other CMs) to throw a critical_error when creating this directory if it does not exist already.
To reproduce:
delete ~/.cache/dconf
killall telepathy-gabble
start GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/lib/
this will error when the first account is connected.
Related branches
Changed in telepathy-mission-control-5 (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in telepathy-mission-control-5 (Ubuntu Precise): | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
The full list we need permissions for is as following:
${HOME}/.cache/ /.cache/ telepathy/ /.cache/ wocky/ /.cache/ wocky/caps/ /.config/ indicators/ /.config/ indicators/ messages/ /.config/ indicators/ messages/ applications- blacklist/ /.{cache, config} /dconf/ user /.local/ share/telepathy / /.local/ share/TpLogger/ /.mission- control/
${HOME}
${HOME}
${HOME}
${HOME}
${HOME}
${HOME}
${HOME}
${HOME}
${HOME}
${HOME}