Public bug reported: When running confined into a snap environment, mission-control needs to use different paths for its files:
Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Unable to create directory '/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file system Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Failed to create file '/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY': No such file or directory Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Unable to create directory '/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file system Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: (process:4767): mcd-WARNING **: Failed to create file '/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY': No such file or Instead of using $SNAP, it probably should use $SNAP_DATA ** Affects: canonical-devices-system-image Importance: Medium Assignee: Bill Filler (bfiller) Status: Confirmed ** Affects: history-service (Ubuntu) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646611 Title: mission-control should use different paths when in a snap environment To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs