Snap doesn't start anymore: Permission denied

snapcraft
1

Hi there.

Since yesterday my Snap build doesn’t start any longer on users computers. I did not chance anything on the snap’s side except for bumping up the version number in snapcraft.yaml.

Here is my yaml: https://github.com/ransome1/sleek/blob/master/snap/snapcraft.yaml

Building and installation through snap still runs without any issue, but starting the app ends in:

$ sleek

/snap/sleek/1100/snap/command-chain/desktop-launch: line 602: /snap/sleek/1100/sleek/sleek: Permission denied /snap/sleek/1100/snap/command-chain/desktop-launch: line 602: exec: /snap/sleek/1100/sleek/sleek: cannot execute: Permission denied

This has been reported to me by an Ubuntu user and I see the same permission issue on my Arch Linux machine.

Does anybody have an idea where this is coming from all of the sudden?

2

this might be another kernel 6.x issue like described in:

https://forum.snapcraft.io/t/unsupported-version-0-of-verneed-record-linux-6-0/32160/16

3

I’m afraid this might not be it. I am on a 5.15.77-1-lts kernel :confused:

1 Like
4

I can confirm this is happening to me! I’m on BunsenLabs, a debian release.

snap        2.57.6
snapd       2.57.6
series      16
bunsenlabs  11
kernel      5.10.0-19-amd64
5

I’ve just tested the Sleek snap (revision 1090), and it seems to run as expected on my Kinetic machine running snapd 2.57.6 and kernel 5.19.

snap    2.57.6
snapd   2.57.6
series  16
ubuntu  22.10
kernel  5.19.0-23-generic
6

@cmatsuoka I downgraded the production release to the last revision, which is known to be working. And that is 1090 (v1.2.8).

The issue @jasonmehmel describes and I am experiencing myself, occurs from revision 1094 onwards. The latest revision 1105 is in the edge channel. If you install it sudo snap install --edge sleek you will most likely see the error.

7

I can confirm that revision 1105 fails with the aforementioned permission denied error. A quick inspection, however, shows that the sleek directory at the package’s top level directory has very restrictive permissions, is this expected?

drwxr-xr-x 9 root root  124 nov 28 05:24 .
drwxr-xr-x 3 root root 4096 nov 30 10:47 ..
drwxr-xr-x 5 root root   56 nov 28 05:24 data-dir
drwxr-xr-x 2 root root    3 nov 28 05:23 gnome-platform
drwxr-xr-x 3 root root   39 nov 28 05:24 lib
drwxr-xr-x 4 root root   56 nov 28 05:24 meta
drwx------ 5 root root  457 nov 28 05:23 sleek
drwxr-xr-x 3 root root   79 nov 28 05:24 snap
drwxr-xr-x 4 root root   39 nov 28 05:23 usr
8

I’m not explicitly setting those permissions. I assume this is done my the Snapcraft build process.

This is the .yaml configuration Snap builds the release on: https://github.com/ransome1/sleek/blob/master/snap/snapcraft.yaml

Also: I checked the permissions on the v1.2.8 release, which apparently is working, and those look exactly like the ones of the v1.3.0.

9

Here the permissions on 1.2.8 are different, and you can actually enter the sleek directory.

drwxr-xr-x 5 root root  56 out 25 04:29 data-dir
drwxr-xr-x 2 root root   3 out 25 04:29 gnome-platform
drwxr-xr-x 3 root root  39 out 25 04:29 lib
drwxr-xr-x 4 root root  56 out 25 04:29 meta
drwxr-xr-x 5 root root 445 out 25 04:29 sleek
drwxr-xr-x 3 root root  79 out 25 04:29 snap
drwxr-xr-x 4 root root  39 out 25 04:29 usr