Comment 10 for bug 61954

It required purging and reinstalling the package in order to solve the problem. That would normally suggest to me that further work on the package is indicated. On the other hand, no one else has reported the problem yet. My philosophy is that a problem which happens once can sometimes be dismissed as a quirk ... but if it happens a second time, it is a real problem and something must be done to fix it.

I would agree that the bug be left closed for now, but if someone else reports the same behaviour, I hope that you will re-open it and add some further cleanup of previous files.