On Tue, Dec 19, 2017 at 11:52:22AM -0400, Joey Hess wrote: > Disabling apparmor avoids this bug.
As I guessed. As it's disabled per default, can we close this bug? (Yes, I am aware about the upgrade maybe not disabling it, but this is sid->sid...). And to be honest, people with "nonstandard" parts will always have problems when more and more applications will ship apparmor stuff. Anyone who will use LO to connect to it and specify an own userdir for example (see #882597). That's the root cause why it's reenabled but only switched to complain in 5.4.4-1. Regards, Rene
