This bug was fixed in the package gsettings-qt -
0.1+14.10.20140624-0ubuntu1
---------------
gsettings-qt (0.1+14.10.20140624-0ubuntu1) utopic; urgency=low
[ Lars Uebernickel ]
* Stop using deprecated g_settings_get_range()
* qml: only emit changed when the value has actually changed This
cannot be done for the c++ class, because that would involve a
round-trip to the dconf database. The QML component already caches
all values because of the way QQmlPropertyMap works. (LP: #1330365)
-- Ubuntu daily release <[email protected]> Tue, 24 Jun 2014
10:01:54 +0000
** Changed in: gsettings-qt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsettings-qt in Ubuntu.
https://bugs.launchpad.net/bugs/1330365
Title:
gsettings-qt bi-directional binding can cause X lockup
Status in GSettingsQt:
In Progress
Status in “gsettings-qt” package in Ubuntu:
Fix Released
Bug description:
Bi-directional bindin can cause a lockup of X.
Would be good to check inside gsettings-qml something like:
void setValue
( m_value != value )
{
m_value = value;
emit valueChanged();
}
}
Example code:
http://pastie.org/9293986
To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-qt/+bug/1330365/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
