Content provider interfaces introduced to snaps aren't correctly set up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Fix Released
|
High
|
Zygmunt Krynicki |
Bug Description
This happened in the telegram-snap (and others that I don't manage, so I can't define a list or detailed changes), but it happened the first time when I introduced the usage of the `desktop` plug, and now again once adding the content interfaces provided by gtk-common-themes.
Here's what happened:
1) telegram-desktop was providing fonts and etc
2) Added the `desktop` plug
3) Most of users who have auto-refreshed the snap have an
empty /usr/share/fonts mount point
3) I started using the gtk-common-themes interface to provide resources:
https:/
4) Fresh install works fine
5) After auto-refreshing the snap in some machines (here too) nothing is
mounted in my $SNAP/usr/share/
All this is generally fixed by uninstalling and reinstalling the snap. Next refreshes are fine.
This has been already briefly discussed at the previous engineering sprint.
Changed in snappy: | |
assignee: | nobody → Zygmunt Krynicki (zyga) |
Changed in snappy: | |
status: | New → Triaged |
importance: | Undecided → High |
I will attempt to reproduce this but you could provide some additional details that would help:
- the before and after revision numbers (so that I can reproduce this precisely) ns/snap. telegram- desktop. fstab snapd/mount/ snap.telegram- desktop. fstab snapd/ns/ telegram- desktop. mnt mountinfo
- the content of /run/snapd/
- the content of /var/lib/
- the output of:
run: $ nsenter -m/run/
in the new shell run: cat /proc/self/