@Tihomir
There was a Xenial update for friendly-recovery done in bug 1766872 that likely fixed your issue.
@Tihomir
There was a Xenial update for friendly-recovery done in bug 1766872 that likely fixed your issue.