| 2013-12-11 22:28:38 |
Jamie Strandboge |
description |
Without the following dconf rules, there are apparmor denials when using Oxide:
owner /run/user/[0-9]*/dconf/user rw,
owner @{HOME}/.config/dconf/user r,
gsettings is not supported in the SDK at this team and access to dconf is not allowed. Oxide appear to work ok without these rules, but the logs are noisy and will almost certainly lead to confusion.
It is conjectured that this is for proxy settings. Indeed, stderr shows this:
[1211/162140:WARNING:proxy_service.cc(890)] PAC support disabled because there is no system implementation |
Without the following dconf rules, there are apparmor denials when using Oxide:
owner /run/user/[0-9]*/dconf/user rw,
owner @{HOME}/.config/dconf/user r,
gsettings is not supported in the SDK at this team and access to dconf is not allowed. Oxide appear to work ok without these rules, but the logs are noisy and will almost certainly lead to confusion.
It is conjectured that this is for proxy settings. Indeed, stderr shows this:
[1211/162140:WARNING:proxy_service.cc(890)] PAC support disabled because there is no system implementation
We could silence the apparmor denials, but it is possible that we will support gsettings some day and more importantly, silencing these denials will make it difficult for people writing apps to diagnose that they shouldn't be using gsettings. |
|
