snapd

  1. Bug #1808821
  2. Comment #5

Comment 5 for bug 1808821

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

I've debugged the issue now. For the sake of leaving a trace:

2019/08/13 14:54:36.626895 change.go:340: DEBUG: umount "/tmp/.snap/usr/share" (error: <nil>)
2019/08/13 14:54:36.626999 trespassing.go:183: DEBUG: trespassing violated "/usr/share/alsa" while striving to "/usr/share/alsa/alsa.conf"
2019/08/13 14:54:36.627021 trespassing.go:184: DEBUG: restricted mode: true
2019/08/13 14:54:36.627029 trespassing.go:185: DEBUG: unrestricted paths: ["/tmp" "/var/snap" "/snap/test-snapd-lp-1808821"]

The problem is directly caused by snap-update-ns keeping track of allowed locations to write to. When /usr/share/ tmpfs is unmounted the corresponding permission to use it goes with it. I need to check if this is a bug in the change tracking code or change reuse code.