← Back to team overview

touch-packages team mailing list archive

[Bug 1356409] Re: Confined scopes are using the wrong path for the writable directory

 

** Changed in: unity-scopes-api (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1356409

Title:
  Confined scopes are using the wrong path for the writable directory

Status in API for Unity scopes integration:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-api source package in Utopic:
  Fix Released

Bug description:
  Confined scopes are trying to use the wrong path for their writable
  data directory:

  Jan 1 20:24:13 ubuntu-phablet kernel: [ 203.538083]
  (1)[4915:scoperunner]type=1400 audit(1388607853.401:143):
  apparmor="DENIED" operation="mkdir"
  profile="com.ubuntu.scopes.youtube_youtube_1.0.7"
  name="/home/phablet/.local/share/unity-scopes/leaf-
  net/com.ubuntu.scopes.youtube_youtube/" pid=4915 comm="scoperunner"
  requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011

  The runtime is trying to create the path:

  $HOME/.local/share/unity-scopes/leaf-net/$APP_PKGNAME_$APP_APPNAME
  ==
  $HOME/.local/share/unity-scopes/leaf-net/com.ubuntu.scopes.youtube_youtube

  which is not quite correct for confined scopes. They should actually
  be using:

  $HOME/.local/share/unity-scopes/leaf-net/$APP_PKGNAME
  ==
  $HOME/.local/share/unity-scopes/leaf-net/com.ubuntu.scopes.youtube

  The scope ID is made of two components, the APP_PKGNAME and the
  APP_APPNAME. Therefore it should not be used to determine the writable
  path.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scopes-api/+bug/1356409/+subscriptions