Since some time over the holidays I’ve had problems refreshing/installing the Wekan snap  on my home server and also my desktop. The installation stalls at the configuration phase, which on the surface looks a bit like bug #1674193 , but here core gets installed just fine, and the hang occurs just alike if I first install just core, then the `wekan` snap separately.
14.52 jani@saegusa:~$ sudo snap install wekan
[sudo] salasana henkilölle jani:
error: cannot perform the following tasks:
– Run configure hook of ”wekan” snap if present (run hook ”configure”: <exceeded maximum runtime of 5m0s>)
Installing other snaps works (the couple that I tried just to be able to say this did anyway).
I’ve reported this on the Wekan snap Github page , but there’s been no confirmation from anyone else affected so far. Also, I’m unable to reproduce this myself in a VM and on at least one other (physical) desktop I have access to.
So naturally I’ve looked for differences between these systems, but so far the only correlating one I’m pretty sure of is an Apparmor denial:
apparmor=”DENIED” operation=”open” profile=”snap.wekan.mongodb” name=”/sys/block/” pid=9478 comm=”mongod” requested_mask=”r” denied_mask=”r” fsuid=0 ouid=0
The two systems where Apparmor denies mongodb’s access to /sys/block get stuck at the configure hook, whereas systems that don’t deny access finish the configuration (and installation) successfully.
I have not tweaked any Apparmor configuration on any of these systems prior to this issue cropping up (not that I can remember anyway). I’ve also not touched anything snap-related, as Wekan was one of the first snaps I’ve ever tried and is (or would be) the only one (besides core) currently installed on these systems.
All systems are running Ubuntu 16.04, with my (affected) desktop having both HWE and -proposed enabled, my (affected) server running a 4.4-series kernel (no HWE or -proposed) and the other (unaffected) desktop having HWE but no -proposed. The (unaffected) VM starts with kernel 4.4 and remains unaffected if I upgrade it with HWE.
I’m submitting this from the (HWE+proposed-enabled) desktop, so any logs attached here are from one of the two affected systems. I’ll of course provide other logs too if requested.
DistroRelease: Ubuntu 16.04
Package: snapd 22.214.171.124
ProcVersionSignature: Ubuntu 4.13.0-30.33~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-30-generic x86_64
Date: Mon Jan 22 15:44:20 2018
InstallationDate: Installed on 2016-10-13 (466 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS ”Xenial Xerus” – Release amd64 (20160719)
UpgradeStatus: No upgrade log present (probably fresh install)