I already mentioned about it in here:
http://talk.maemo.org/showpost.php?p...&postcount=216

It is not easily reproducible because an unitialized variable (e.g. Settings::incomingCallNotification) is being read (valgrind should complain).

QObject->property() will only return an invalid variant if the property does not exist. The property exists (it is not dynamic, since it is declared via Q_PROPERTY), and therefore the isValid() check is useless (always returns true).

Thus, even if the dconf setting does not exist, the current value of Settings::incomingCallNotification is read. This is not initialized in the constructor (which doesn't initialize much), and certainly is not initialized by MDConfGroup (because the setting does not exist in dconf yet).

Therefore, a random value is read.

Sorry I don't have time to make a patch atm, but it should be as trivial as changing the settings.h constructor to initialize the member variables to the proper default values.