It seems that the app's windows procedure does not expect a WM_QUERYNEWPALETTE message.
Damn, I faintly remember that I've also had a problem with the WM_QUERYNEWPALETTE ages ago (about two years ago). Commenting it out made it go away.
Sounds like we might want to investigate WM_QUERYNEWPALETTE behaviour...
If someone that knows this code well have an idea... else I will report this bug to bugzilla.
Yep, good idea, since I can confirm suspicions about WM_QUERYNEWPALETTE brokenness. (or at least the WM_QUERYNEWPALETTE is playing a role in such a problem somewhere...)
I've just submitted the bug report. Now you confirm the bug and add some comments.