Comment 12 for bug 1770044

>> In case it helps, I printed today to a non-existing printer. (Or not connected now)
>> This might be the reason.

That's interesting. The system on which I had the problem also had an "unusual" printer defined.
I have a Brother printer/scanner, so add the Brother-supplied driver (more options - needed for the scanner). I then try to prevent cups from finding the device on the network and adding another printer entry by manually editing cups-browsed.conf to add BrowseDeny entries, but that doesn't always seem to work.
So it's possible that when I re-installed the OS (see #4) I did this in a way which worked differently.