I believe the appearance of these issues corresponds to the release of the
package policykit-1 version 0.105-17 into stretch/testing on October 27,
2016.

Reply via email to