** Also affects: telepathy-mission-control-5 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: history-service (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1646611
Title:
mission-control should use different paths when in a snap environment
Status in Canonical System Image:
Confirmed
Status in telepathy-mission-control-5 package in Ubuntu:
New
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646611/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
