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

Bug #1646611 reported by Gustavo Pichorim Boiko
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Confirmed
Medium
Bill Filler
Unity8 Session Snap
New
Undecided
Renato Araujo Oliveira Filho
telepathy-mission-control-5 (Ubuntu)
Confirmed
Medium
Renato Araujo Oliveira Filho

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

Related branches

Changed in canonical-devices-system-image:
assignee: nobody → Bill Filler (bfiller)
importance: Undecided → Medium
milestone: none → p1
status: New → Confirmed
Revision history for this message
Renato Araujo Oliveira Filho (renatofilho) wrote :

check if it is using:

QStandardPaths::writableLocation(QStandardPaths::AppDataLocation)

It should return the right path on snap or not.

Revision history for this message
Renato Araujo Oliveira Filho (renatofilho) wrote :

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

no longer affects: history-service (Ubuntu)
Revision history for this message
Gustavo Pichorim Boiko (boiko) wrote :

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

Bill Filler (bfiller)
Changed in telepathy-mission-control-5 (Ubuntu):
importance: Undecided → Medium
Changed in telepathy-mission-control-5 (Ubuntu):
assignee: nobody → Renato Araujo Oliveira Filho (renatofilho)
Changed in unity8-session-snap:
assignee: nobody → Renato Araujo Oliveira Filho (renatofilho)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in telepathy-mission-control-5 (Ubuntu):
status: New → Confirmed
Changed in canonical-devices-system-image:
milestone: p1 → p2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.