> Is this the same bug as in Bug#45679?

It certainly can be, yes.
Fixing one will probably fix the other. But I decided not to guess and file this report as well, as the described case is a bit different