mission-control should use different paths when in a snap environment
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
Sep 30 05:31:22 localhost org.freedesktop
Sep 30 05:31:22 localhost org.freedesktop
Sep 30 05:31:22 localhost org.freedesktop
Instead of using $SNAP, it probably should use $SNAP_DATA
Related branches
- Michael Terry (community): Needs Fixing
-
Diff: 11 lines (+1/-0)1 file modifiedoverlay/snappyenv (+1/-0)
Changed in canonical-devices-system-image: | |
assignee: | nobody → Bill Filler (bfiller) |
importance: | Undecided → Medium |
milestone: | none → p1 |
status: | New → Confirmed |
no longer affects: | history-service (Ubuntu) |
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) |
Changed in canonical-devices-system-image: | |
milestone: | p1 → p2 |
check if it is using:
QStandardPaths: :writableLocati on(QStandardPat hs::AppDataLoca tion)
It should return the right path on snap or not.