[Bug 911165] [NEW] QDeclarativeItemPrivate::isAccessible is not propertly initialized

Albert Astals Cid albert.astals at canonical.com
Tue Jan 3 10:40:14 UTC 2012


Public bug reported:

The a11y_qt_and_qml_backport.diff patch as shipped in Oneiric does not initialize QDeclarativeItemPrivate::isAccessible meaning that when you try to valgrind a QML based application like unity-2d you get lots of
   Conditional jump or move depends on uninitialised value(s)
when the code uses the isAccessible variable.

** Affects: qt4-x11 (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

- The a11y_qt_and_qml_backport.diff patch as shipped in Oneiric does not initialize QDeclarativeItemPrivate::isAccessible meaning that when you try to valgrind a QML based all like unity-2d you get lots of 
-    Conditional jump or move depends on uninitialised value(s)
+ The a11y_qt_and_qml_backport.diff patch as shipped in Oneiric does not initialize QDeclarativeItemPrivate::isAccessible meaning that when you try to valgrind a QML based application like unity-2d you get lots of
+    Conditional jump or move depends on uninitialised value(s)
  when the code use the isAccessible variable.

** Description changed:

  The a11y_qt_and_qml_backport.diff patch as shipped in Oneiric does not initialize QDeclarativeItemPrivate::isAccessible meaning that when you try to valgrind a QML based application like unity-2d you get lots of
     Conditional jump or move depends on uninitialised value(s)
- when the code use the isAccessible variable.
+ when the code uses the isAccessible variable.

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

Title:
  QDeclarativeItemPrivate::isAccessible is not propertly initialized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/911165/+subscriptions



More information about the kubuntu-bugs mailing list