Earlier, I wrote: > I will soon switch back to dconf-0.36 to see if the problem returns.
Shortly after switching back to dconf-0.36, the problem has indeed
returned. So, in summary, the problem has *never* happened to me with
dconf-0.34, but happens quite frequently with dconf-0.36.
Mark
