Same problem here. It started from the edgy beta version of update-manager AFAIK. Two updates later, the problem is still unresolved (at least for me).
Same problem here. It started from the edgy beta version of update-manager AFAIK. Two updates later, the problem is still unresolved (at least for me).