mission-control should use different paths when in a snap environment

[Gustavo Pichorim Boiko]

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

[Renato Araujo Oliveira Filho (renatofilho)]

check if it is using:

QStandardPaths::writableLocation(QStandardPaths::AppDataLocation)

It should return the right path on snap or not.

[Renato Araujo Oliveira Filho (renatofilho)]

in case of configuration files it should use the enum: QStandardPaths::AppConfigLocation

[Gustavo Pichorim Boiko (boiko)]

Well, mission-control is not using Qt at all, so certainly not using QStandardPaths

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.