@unknown reflecting on this, I executed
and encountered the error. I did not (as you indicated) execute
on a fresh installation right after login. So, that is maybe the difference. You are likely entirely correct that executing apt get remove right after login on first install will fix the issue. That said, I suspect most folks are going to come across the error only after trying to do an apt get upgrade, so my note is aimed at those folks, who when searching might come across this discussion.
