date:20160805

[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients

2016-08-05 Thread Daniel d'Andrada

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtdeclarative-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1597205

Title:
  Not sending relative mouse events to clients

Status in Canonical System Image:
  Fix Committed
Status in QtMir:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  QtMir is not sending relative mouse movements in mouse events.

  Relevant code from mirsurface.cpp:

  
  mir::EventUPtr makeMirEvent(QMouseEvent *qtEvent, MirPointerAction action)
  {
  auto timestamp = 
uncompressTimestamp(qtmir::Timestamp(qtEvent->timestamp()));
  auto modifiers = getMirModifiersFromQt(qtEvent->modifiers());
  auto buttons = getMirButtonsFromQt(qtEvent->buttons());

  return mir::events::make_event(0 /*DeviceID */, timestamp, 
std::vector{} /* cookie */, modifiers, action,
 buttons, qtEvent->x(), qtEvent->y(), 0, 0, 
0, 0);

  
  The last 2 parameters in the make_event call should be the relative x & y 
motion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597205/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1610349] [NEW] QML compare() does not reliably compare colours

2016-08-05 Thread Andrea Bernabei

Public bug reported:

See upstream bug https://bugreports.qt.io/browse/QTBUG-34878

There is already a fix upstream which has been merged to Qt5.8 ( see 
https://codereview.qt-project.org/#/c/158967/ )
Without that fix, all the unit tests relying on compare() to compare colours 
must be considered unreliable and potentially misleading, as they could be 
producing PASSes instead of FAILs.


Bug description copied from that link:
"QtTest's compare() function considers two colors (the QML basic type) as equal 
when they aren't.
I am aware that Qt.colorEqual exists (and it works correctly), but I think that 
this makes it far too easy to write tests that don't catch an error.
Consider the following test case:

import QtQuick 2.2
import QtTest 1.0

Item {
Rectangle {
id: black
color: "#00"
}

Rectangle {
id: white
color: "#ff"
}

TestCase {
name: "ColorComparison"

function test_this_should_fail() {
compare(black.color, white.color)
}

function test_this_is_ok() {
compare(black.color == white.color, false)
compare(Qt.colorEqual(black.color, white.color), false)
}
}
}"

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtdeclarative-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1610349

Title:
  QML compare() does not reliably compare colours

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  See upstream bug https://bugreports.qt.io/browse/QTBUG-34878

  There is already a fix upstream which has been merged to Qt5.8 ( see 
https://codereview.qt-project.org/#/c/158967/ )
  Without that fix, all the unit tests relying on compare() to compare colours 
must be considered unreliable and potentially misleading, as they could be 
producing PASSes instead of FAILs.

  
  Bug description copied from that link:
  "QtTest's compare() function considers two colors (the QML basic type) as 
equal when they aren't.
  I am aware that Qt.colorEqual exists (and it works correctly), but I think 
that this makes it far too easy to write tests that don't catch an error.
  Consider the following test case:

  import QtQuick 2.2
  import QtTest 1.0

  Item {
  Rectangle {
  id: black
  color: "#00"
  }

  Rectangle {
  id: white
  color: "#ff"
  }

  TestCase {
  name: "ColorComparison"

  function test_this_should_fail() {
  compare(black.color, white.color)
  }

  function test_this_is_ok() {
  compare(black.color == white.color, false)
  compare(Qt.colorEqual(black.color, white.color), false)
  }
  }
  }"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1610349/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1588238] Re: Flickable's widthRatio and heightRatio are wrong when the content is smaller than the view and has topMargin/leftMargin

2016-08-05 Thread Łukasz Zemczak

This bug was fixed in the package qtdeclarative-opensource-src
5.4.1-1ubuntu11~overlay9~1 in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/stable-phone-overlay

---

qtdeclarative-opensource-src (5.4.1-1ubuntu11~overlay9~1) vivid;
urgency=medium

  * debian/patches/Flickable-fix-minXExtent-minYExtent-when-content-is-.patch:
- Fix flickable's widthRatio and heightRatio (LP: #1588238)
  * debian/patches/QQuickWindow-Fill-out-timestamps-in-QHoverEvents-sen.patch:
- Fix relative mouse events (LP: #1597205)
- debian/libqt5quick5.symbols: Update symbols.

 -- Timo Jyrinki   Thu, 02 Jun 2016 10:18:08
+


** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtdeclarative-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1588238

Title:
  Flickable's widthRatio and heightRatio are wrong when the content is
  smaller than the view and has topMargin/leftMargin

Status in Canonical System Image:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  UPSTREAM BUG: https://bugreports.qt.io/browse/QTBUG-53726

  Description (copied from the upstream bug I created)

  According to Flickable's documentation, widthRatio and heightRatio define
  "the percentage of the full view currently visible, scaled to 0.0 - 1.0".
  At the moment, defining leftMargin so that
  leftMargin+contentWidth < flickable.width
  causes widthRatio to be wrongly evaluated to something != 1, whereas it 
should be 1, because Flickable's defaults at -leftMargin
  (see 
https://github.com/qtproject/qtdeclarative/blob/5.6/src/quick/items/qquickflickable.cpp#L1592
 ).
  and when contentX is -leftMargin, the whole content fits inside the view.
  As a consequence of that, in the current implementation you can also scroll 
the item from the testcase left and right, which shouldn't be possible (because 
item+margin are still smaller than the view).

  

  Additional Ubuntu-specific info:
  This is currently blocking the correct implementation of the new scrollbars 
inside TextFields (ping kalikiana or me (faenil) on IRC for more info)

  TESTCASE

  import QtQuick 2.0

  Flickable {
  id: flickable
  width: 200
  height: 200
  contentWidth: item.width
  contentHeight: item.height
  topMargin: 20
  leftMargin: 40
  Component.onCompleted: console.log("xPos", 
flickable.visibleArea.xPosition, "widthRatio", flickable.visibleArea.widthRatio)
  Connections {
  target: flickable.visibleArea
  onXPositionChanged: console.log("xPosChanged", 
flickable.visibleArea.xPosition)
  onWidthRatioChanged: console.log("widthRatioChanged", 
flickable.visibleArea.widthRatio)
  }
  Rectangle {
  id: item
  width: 100
  height: 100
  color: "black"
  }
  }

  ===

  How to reproduce:
  1) qmlscene testcase.qml
  2) watch the console output

  Actual result: widthRatio is != 1
  Expected result: widthRatio == 1

  ===

  Fix: I worked on a fix which is being reviewed by upstream --->
  https://codereview.qt-project.org/#/c/161043/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588238/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients

2016-08-05 Thread Łukasz Zemczak

This bug was fixed in the package qtdeclarative-opensource-src
5.4.1-1ubuntu11~overlay9~1 in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/stable-phone-overlay

---

qtdeclarative-opensource-src (5.4.1-1ubuntu11~overlay9~1) vivid;
urgency=medium

  * debian/patches/Flickable-fix-minXExtent-minYExtent-when-content-is-.patch:
- Fix flickable's widthRatio and heightRatio (LP: #1588238)
  * debian/patches/QQuickWindow-Fill-out-timestamps-in-QHoverEvents-sen.patch:
- Fix relative mouse events (LP: #1597205)
- debian/libqt5quick5.symbols: Update symbols.

 -- Timo Jyrinki   Thu, 02 Jun 2016 10:18:08
+


** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtdeclarative-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1597205

Title:
  Not sending relative mouse events to clients

Status in Canonical System Image:
  In Progress
Status in QtMir:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  QtMir is not sending relative mouse movements in mouse events.

  Relevant code from mirsurface.cpp:

  
  mir::EventUPtr makeMirEvent(QMouseEvent *qtEvent, MirPointerAction action)
  {
  auto timestamp = 
uncompressTimestamp(qtmir::Timestamp(qtEvent->timestamp()));
  auto modifiers = getMirModifiersFromQt(qtEvent->modifiers());
  auto buttons = getMirButtonsFromQt(qtEvent->buttons());

  return mir::events::make_event(0 /*DeviceID */, timestamp, 
std::vector{} /* cookie */, modifiers, action,
 buttons, qtEvent->x(), qtEvent->y(), 0, 0, 
0, 0);

  
  The last 2 parameters in the make_event call should be the relative x & y 
motion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597205/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1606944] Re: Password field briefly displays characters when input using a keyboard

2016-08-05 Thread Christian Dywan

** Package changed: ubuntu-ui-toolkit (Ubuntu) => ubuntuone-credentials
(Ubuntu)

** Changed in: ubuntuone-credentials (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1606944

Title:
  Password field briefly displays characters when input using a keyboard

Status in Canonical System Image:
  New
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed

Bug description:
  When running Unity 8 on my classic desktop I have to enter my password
  in to, for example, the store login.

  If I am entering text using a real keyboard I still see the character
  displayed in clear as I am typing.  I don't think it should do that.

  Use-case:  I am making a screencast and entering a password.  By
  playing back the video The Baddies would be able to see each character
  I entered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1606944/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1609616] Re: Alarm/AlarmModel should be confined per app

2016-08-05 Thread Christian Dywan

** Package changed: ubuntu-ui-toolkit (Ubuntu) => apparmor-easyprof-
ubuntu (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1609616

Title:
  Alarm/AlarmModel should be confined per app

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New

Bug description:
  Currently, when you use the AlarmModel and calendar apparmor policy,
  your app can view, add, edit and delete alarms even those that were
  created by other apps like for example the core clock app.

  I think it would be better if the model only gives your app the permission to 
view, edit and delete alarms created by your app. Then when the alarm is 
triggered, the appropriate app will open and not alwayd the clock app.
  This means that alarms in the AlarmModel can be distinguished by app and bot 
as whole.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1609616/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1608912] Re: Changing volume from speaker/microphone with mouse wheel is not working

2016-08-05 Thread Christian Dywan

** No longer affects: ubuntu-ui-toolkit (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1608912

Title:
  Changing volume from speaker/microphone with mouse wheel is not
  working

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Unity8 can't change volume from speaker or microphone in the opened
  indicator sound (See attached) with the mouse wheel. Note that Unity7
  can do this and increases/decreases 10% every wheel event

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1608912/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1610231] [NEW] tst_sections.13 fails with Qt 5.6

2016-08-05 Thread Christian Dywan

Public bug reported:

tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual 
tests/unit/visual/tst_sections.13.qml
[...]
FAIL!  : components::SectionsApi::initTestCase() Action 0 was triggered with 
selectedIndex: 1.
 Actual (): true
 Expected (): false
 Loc:[./tests/unit/visual/tst_sections.13.qml(149)]

More information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: qt5.6

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1610231

Title:
  tst_sections.13 fails with Qt 5.6

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual 
tests/unit/visual/tst_sections.13.qml
  [...]
  FAIL!  : components::SectionsApi::initTestCase() Action 0 was triggered with 
selectedIndex: 1.
   Actual (): true
   Expected (): false
   Loc:[./tests/unit/visual/tst_sections.13.qml(149)]

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1610230] [NEW] tst_expandablescolumn11 fails with Qt 5.6

2016-08-05 Thread Christian Dywan

Public bug reported:

tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual 
tests/unit/visual/tst_expandablescolumn.11.qml
[...]
QWARN  : components::ExpandablesColumn::test_collapseByClickingOutside() 
./_build/qml/Ubuntu/Components/ListItems/1.2/ExpandablesColumn.qml:127: 
TypeError: Type error
[...]
FAIL!  : components::ExpandablesColumn::test_scrollToTop() Uncaught exception: 
Type error
 Loc:[./tests/unit/visual/tst_expandablescolumn.11.qml(115)]

cf. tst_ubuntulistview.qml

More information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: qt5.6

** Description changed:

  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual 
tests/unit/visual/tst_expandablescolumn.11.qml
  [...]
  QWARN  : components::ExpandablesColumn::test_collapseByClickingOutside() 
./_build/qml/Ubuntu/Components/ListItems/1.2/ExpandablesColumn.qml:127: 
TypeError: Type error
  [...]
  FAIL!  : components::ExpandablesColumn::test_scrollToTop() Uncaught 
exception: Type error
-  Loc:[./tests/unit/visual/tst_expandablescolumn.11.qml(115)]
+  Loc:[./tests/unit/visual/tst_expandablescolumn.11.qml(115)]
+ 
+ cf. tst_ubuntulistview.qml
  
  More information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1610230

Title:
  tst_expandablescolumn11 fails with Qt 5.6

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual 
tests/unit/visual/tst_expandablescolumn.11.qml
  [...]
  QWARN  : components::ExpandablesColumn::test_collapseByClickingOutside() 
./_build/qml/Ubuntu/Components/ListItems/1.2/ExpandablesColumn.qml:127: 
TypeError: Type error
  [...]
  FAIL!  : components::ExpandablesColumn::test_scrollToTop() Uncaught 
exception: Type error
   Loc:[./tests/unit/visual/tst_expandablescolumn.11.qml(115)]

  cf. tst_ubuntulistview.qml

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1604032] Re: Touchpad scrolling should be enabled by default in Unity8

2016-08-05 Thread Launchpad Bug Tracker

This bug was fixed in the package gsettings-ubuntu-touch-schemas -
0.0.7+16.10.20160730-0ubuntu1

---
gsettings-ubuntu-touch-schemas (0.0.7+16.10.20160730-0ubuntu1) yakkety; 
urgency=medium

  * Enable TouchpadTwoFingerScroll and TouchpadTapToClick by default
(LP: #1603183, #1604032)

 -- Lukáš Tinkl   Sat, 30 Jul 2016 21:17:59
+

** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1604032

Title:
  Touchpad scrolling should be enabled by default in Unity8

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Invalid
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  this used to work, 
  on a unity8-desktop-session, launch browser
  on touchpad scroll up/down
  expect webpage to scroll, but currently there is no reaction

  the only way to get a webpage to scroll is to grab the page with a
  mousebutton down and hold it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604032/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1610208] [NEW] Migrate to new QT_SCALE_FACTOR in Qt 5.6

2016-08-05 Thread Christian Dywan

Public bug reported:

Qt 5.6 supersedes QT_DEVICE_PIXEL_RATIO with three variables:
- QT_SCALE_FACTOR, which works the same way.
- QTSCREEN_SCALE_FACTORS, which lists values per monitor.
- QT_AUTO_SCREEN_SCALE_FACTOR, which automatically picks a value for each 
monitor.

Documentation needs to take these new variables into account and we need
to start using the new variables where applicable (the old one still
works, but triggers warnings with Qt 5.6).

Note: tests/unit/units have failures with Qt 5.6.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Critical
 Assignee: Christian Dywan (kalikiana)
 Status: Confirmed


** Tags: qt5.6

** Tags added: qt5.6

** Description changed:

  Qt 5.6 supersedes QT_DEVICE_PIXEL_RATIO with three variables:
  - QT_SCALE_FACTOR, which works the same way.
  - QTSCREEN_SCALE_FACTORS, which lists values per monitor.
  - QT_AUTO_SCREEN_SCALE_FACTOR, which automatically picks a value for each 
monitor.
  
  Documentation needs to take these new variables into account and we need
  to start using the new variables where applicable (the old one still
  works, but triggers warnings with Qt 5.6).
+ 
+ Note: tests/unit/units have failures with Qt 5.6.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1610208

Title:
  Migrate to new QT_SCALE_FACTOR in Qt 5.6

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Qt 5.6 supersedes QT_DEVICE_PIXEL_RATIO with three variables:
  - QT_SCALE_FACTOR, which works the same way.
  - QTSCREEN_SCALE_FACTORS, which lists values per monitor.
  - QT_AUTO_SCREEN_SCALE_FACTOR, which automatically picks a value for each 
monitor.

  Documentation needs to take these new variables into account and we
  need to start using the new variables where applicable (the old one
  still works, but triggers warnings with Qt 5.6).

  Note: tests/unit/units have failures with Qt 5.6.

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

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1606927] Re: Qt 5.6.1 causes some powerpc tests to fail

2016-08-05 Thread Launchpad Bug Tracker

This bug was fixed in the package unity-api -
7.116+16.10.20160730-0ubuntu1

---
unity-api (7.116+16.10.20160730-0ubuntu1) yakkety; urgency=medium

  [ Michał Sawicz ]
  * Don't run tests on powerpc (LP: #1606927)

  [ Stephen Kelly ]
  * Silence some gcc warnings.

 -- Lukáš Tinkl   Sat, 30 Jul 2016 21:18:50
+

** Changed in: unity-api (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtdeclarative-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1606927

Title:
  Qt 5.6.1 causes some powerpc tests to fail

Status in maliit-framework package in Ubuntu:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in unity-api package in Ubuntu:
  Fix Released

Bug description:
  An example: ubuntu-system-settings:

  https://launchpadlibrarian.net/275303704/buildlog_ubuntu-yakkety-
  powerpc.ubuntu-system-
  settings_0.4+16.10.20160727.2-0ubuntu1_BUILDING.txt.gz

  Stacktraces:
  http://pastebin.ubuntu.com/21137254/
  http://pastebin.ubuntu.com/21137968/
  http://pastebin.ubuntu.com/21138111/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libqt5qml5 5.6.1-4ubuntu1~4
  ProcVersionSignature: Ubuntu 3.13.0-79.123-powerpc64-smp 3.13.11-ckt33
  Uname: Linux 3.13.0-79-powerpc64-smp ppc
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: powerpc
  Date: Wed Jul 27 13:27:50 2016
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: qtdeclarative-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1606927/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients

[Ubuntu-sdk-bugs] [Bug 1610349] [NEW] QML compare() does not reliably compare colours

[Ubuntu-sdk-bugs] [Bug 1588238] Re: Flickable's widthRatio and heightRatio are wrong when the content is smaller than the view and has topMargin/leftMargin

[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients

[Ubuntu-sdk-bugs] [Bug 1606944] Re: Password field briefly displays characters when input using a keyboard

[Ubuntu-sdk-bugs] [Bug 1609616] Re: Alarm/AlarmModel should be confined per app

[Ubuntu-sdk-bugs] [Bug 1608912] Re: Changing volume from speaker/microphone with mouse wheel is not working

[Ubuntu-sdk-bugs] [Bug 1610231] [NEW] tst_sections.13 fails with Qt 5.6

[Ubuntu-sdk-bugs] [Bug 1610230] [NEW] tst_expandablescolumn11 fails with Qt 5.6

[Ubuntu-sdk-bugs] [Bug 1604032] Re: Touchpad scrolling should be enabled by default in Unity8

[Ubuntu-sdk-bugs] [Bug 1610208] [NEW] Migrate to new QT_SCALE_FACTOR in Qt 5.6

[Ubuntu-sdk-bugs] [Bug 1606927] Re: Qt 5.6.1 causes some powerpc tests to fail

12 matches

Site Navigation

Mail list logo

Footer information