I think this is possibly fixed with the upload of update-notifier 3.167 and is a duplicate of bug #1563854.
I think this is possibly fixed with the upload of update-notifier 3.167 and is a duplicate of bug #1563854.