| 2022-10-10 07:08:58 |
James Dingwall |
bug |
|
|
added bug |
| 2022-10-10 07:10:50 |
James Dingwall |
description |
This is an issue I have encountered on two (both 22.04) different systems, one with the 'teams' snap and a second with the 'slack' snap.
$ pwd
/home/user/snap/slack
$ ls -la
total 27
drwxr-xr-x 5 user @user 6 Oct 9 21:34 .
drwx------ 11 user @user 11 Oct 9 21:32 ..
drwxr-xr-x 4 user @user 6 Sep 23 07:45 65
drwx------ 4 root root 5 Oct 9 20:43 66
drwxr-xr-x 3 user @user 3 Mar 16 2022 common
lrwxrwxrwx 1 user @user 2 Oct 9 21:26 current -> 66
In this case the snap fails to start with permission errors. My guess is that the migration of user data failed part way through presumably in a code path which doesn't handle interruption or is capable of being resumed.
$ sudo du -sm 65 66
1115 65
406 66
My workaround is to point the the 'current' link at the old version and then start the snap:
$ rm -f current; sudo rm -rf 66; ln -s 65 current; snap
$ apt-cache policy snapd
snapd:
Installed: 2.56.2+22.04ubuntu1
Candidate: 2.56.2+22.04ubuntu1
Version table:
*** 2.56.2+22.04ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.55.3+22.04 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy |
This is an issue I have encountered on two (both 22.04) different systems, one with the 'teams' snap and a second with the 'slack' snap.
$ pwd
/home/user/snap/slack
$ ls -la
total 27
drwxr-xr-x 5 user @user 6 Oct 9 21:34 .
drwx------ 11 user @user 11 Oct 9 21:32 ..
drwxr-xr-x 4 user @user 6 Sep 23 07:45 65
drwx------ 4 root root 5 Oct 9 20:43 66
drwxr-xr-x 3 user @user 3 Mar 16 2022 common
lrwxrwxrwx 1 user @user 2 Oct 9 21:26 current -> 66
In this case the snap fails to start with permission errors. My guess is that the migration of user data failed part way through presumably in a code path which doesn't handle interruption or is capable of being resumed. There is approximately 1.2T free space (df -h) for /home/user so I don't think this
is a free space problem.
$ sudo du -sm 65 66
1115 65
406 66
My workaround is to point the the 'current' link at the old version and then start the snap:
$ rm -f current; sudo rm -rf 66; ln -s 65 current; snap
$ apt-cache policy snapd
snapd:
Installed: 2.56.2+22.04ubuntu1
Candidate: 2.56.2+22.04ubuntu1
Version table:
*** 2.56.2+22.04ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.55.3+22.04 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy |
|
| 2022-10-10 07:19:51 |
James Dingwall |
description |
This is an issue I have encountered on two (both 22.04) different systems, one with the 'teams' snap and a second with the 'slack' snap.
$ pwd
/home/user/snap/slack
$ ls -la
total 27
drwxr-xr-x 5 user @user 6 Oct 9 21:34 .
drwx------ 11 user @user 11 Oct 9 21:32 ..
drwxr-xr-x 4 user @user 6 Sep 23 07:45 65
drwx------ 4 root root 5 Oct 9 20:43 66
drwxr-xr-x 3 user @user 3 Mar 16 2022 common
lrwxrwxrwx 1 user @user 2 Oct 9 21:26 current -> 66
In this case the snap fails to start with permission errors. My guess is that the migration of user data failed part way through presumably in a code path which doesn't handle interruption or is capable of being resumed. There is approximately 1.2T free space (df -h) for /home/user so I don't think this
is a free space problem.
$ sudo du -sm 65 66
1115 65
406 66
My workaround is to point the the 'current' link at the old version and then start the snap:
$ rm -f current; sudo rm -rf 66; ln -s 65 current; snap
$ apt-cache policy snapd
snapd:
Installed: 2.56.2+22.04ubuntu1
Candidate: 2.56.2+22.04ubuntu1
Version table:
*** 2.56.2+22.04ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.55.3+22.04 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy |
This is an issue I have encountered on two (both 22.04) different systems, one with the 'teams' snap and a second with the 'slack' snap.
$ pwd
/home/user/snap/slack
$ ls -la
total 27
drwxr-xr-x 5 user @user 6 Oct 9 21:34 .
drwx------ 11 user @user 11 Oct 9 21:32 ..
drwxr-xr-x 4 user @user 6 Sep 23 07:45 65
drwx------ 4 root root 5 Oct 9 20:43 66
drwxr-xr-x 3 user @user 3 Mar 16 2022 common
lrwxrwxrwx 1 user @user 2 Oct 9 21:26 current -> 66
In this case the snap fails to start with permission errors. My guess is that the migration of user data failed part way through presumably in a code path which doesn't handle interruption or is capable of being resumed. There is approximately 1.2T free space (df -h) for /home/user so I don't think this
is a free space problem.
$ sudo du -sm 65 66
1115 65
406 66
My workaround is to point the the 'current' link at the old version and then start the snap:
$ rm -f current; sudo rm -rf 66; ln -s 65 current; snap
Importing existing Slack profile from /home/user/.config/Slack to /home/user/snap/slack/66/.config
Import done in 831.232 s
$ apt-cache policy snapd
snapd:
Installed: 2.56.2+22.04ubuntu1
Candidate: 2.56.2+22.04ubuntu1
Version table:
*** 2.56.2+22.04ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.55.3+22.04 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy |
|
| 2022-10-10 10:51:34 |
Alberto Mardegan |
snapd (Ubuntu): status |
New |
Confirmed |
|
| 2022-10-10 10:51:36 |
Alberto Mardegan |
snapd (Ubuntu): importance |
Undecided |
High |
|
