[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment
** Changed in: canonical-devices-system-image Milestone: p1 => p2 -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 Unity8 Session Snap: New Status in telepathy-mission-control-5 package in Ubuntu: Confirmed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telepathy-mission-control-5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 Unity8 Session Snap: New Status in telepathy-mission-control-5 package in Ubuntu: Confirmed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment
** Branch linked: lp:~renatofilho/unity8-session-snap/fix-1646611 ** Also affects: unity8-session-snap Importance: Undecided Status: New ** Changed in: unity8-session-snap Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho) -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 Unity8 Session Snap: New 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment
** Changed in: telepathy-mission-control-5 (Ubuntu) Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho) -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment
** Changed in: telepathy-mission-control-5 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment
Well, mission-control is not using Qt at all, so certainly not using QStandardPaths -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment
** 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 Ubuntu Touch seeded packages, which is subscribed to history-service 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment
check if it is using: QStandardPaths::writableLocation(QStandardPaths::AppDataLocation) It should return the right path on snap or not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service 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 history-service 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment
in case of configuration files it should use the enum: QStandardPaths::AppConfigLocation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service 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 history-service 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment
** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => p1 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Bill Filler (bfiller) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service 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 history-service 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
