Comment 0 for bug 1260101

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