KCModule's are loaded in the background from systemsettings. The changed code was supposed to enable lazy loading. It didn't work because of two flaws:

1. wrong initialization for _firstshow
2. Those d->kcm->show() call wouldn't trigger a showEvent. That widget KCModule was never hidden anyway. The KCModuleProxy was hidden.

That wasn't good for some reasons. One of it is you get warnings possibly completely out of context. klicking on Keyboard&Mouse could bring up messages from 3 different kcm's which aren't visible at that moment. That's confusing for the user.

Now some kcmodule could load their settings twice. Once during the initialization and once during the initial show. We have to find and fix those double loads.