The haptic feedback including the DBus API used to lookup the setting is
not version-specific, the code lives in
src/Ubuntu/Components/1.1/Haptics.qml and is used even with 1.3 via
ucabstractbutton.cpp and uchaptics.cpp. The default is true, meaning if
the setting doesn't work it will indeed always vibrate.

After adding "onErrorChanged: console.log(error)" to the vibra object (at the 
very bottom) in Haptics.qml I got the following running Calculator:
qml: An AppArmor policy prevents this sender [...] 
interface="org.freedesktop.Accounts" member="FindUserById" [...]

So by the looks of it Calculator can't read the setting.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537248

Title:
  Disabling haptics in the system settings only affects Unity8 and a few
  system apps

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1537248/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to