[Touch-packages] [Bug 1642885] Re: The UITK package depends on upstart
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Christian Dywan (kalikiana) => Sergio Cazzolato (sergio-j-cazzolato) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1642885 Title: The UITK package depends on upstart Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The ubuntu-ui-toolkit depends on upstart and not supporting systemd yet. We should use ubuntu-app-launch for this, no need to go down to the upstart vs. systemd detail. c.f. tests/autopilot/ubuntuuitoolkit/tests/__init__.py /usr/lib/python3/dist-packages/autopilot/application/_launcher.py https://code.launchpad.net/~canonical-platform-qa/ubuntu-system-tests/systemd_support/+merge/307239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1642885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642885] Re: The UITK package depends on upstart
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) ** Description changed: The ubuntu-ui-toolkit depends on upstart and not supporting systemd yet. We should use ubuntu-app-launch for this, no need to go down to the upstart vs. systemd detail. + + c.f. + tests/autopilot/ubuntuuitoolkit/tests/__init__.py + /usr/lib/python3/dist-packages/autopilot/application/_launcher.py ** Description changed: The ubuntu-ui-toolkit depends on upstart and not supporting systemd yet. We should use ubuntu-app-launch for this, no need to go down to the upstart vs. systemd detail. c.f. tests/autopilot/ubuntuuitoolkit/tests/__init__.py /usr/lib/python3/dist-packages/autopilot/application/_launcher.py + https://code.launchpad.net/~canonical-platform-qa/ubuntu-system-tests/systemd_support/+merge/307239 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1642885 Title: The UITK package depends on upstart Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The ubuntu-ui-toolkit depends on upstart and not supporting systemd yet. We should use ubuntu-app-launch for this, no need to go down to the upstart vs. systemd detail. c.f. tests/autopilot/ubuntuuitoolkit/tests/__init__.py /usr/lib/python3/dist-packages/autopilot/application/_launcher.py https://code.launchpad.net/~canonical-platform-qa/ubuntu-system-tests/systemd_support/+merge/307239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1642885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633851] Re: Middle-click clipboard no longer works
** No longer affects: ubuntu-ui-toolkit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1633851 Title: Middle-click clipboard no longer works Status in Canonical System Image: New Status in content-hub package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Under X, any selected text would be automatically be added to a seperate clipboard whose contents could be pasted by pressing the middle-click button or the equivalent touchpad tap. I understand it's an X functionality, and I'm asking it to be implemented in Mir. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1633851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Fix Released => In Progress ** Changed in: canonical-devices-system-image Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1586013 Title: UITK Date picker broken on xenial Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6 (right). More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml [...] FAIL! : components::DatePicker13API::test_1_changeMinimumBeforeDate() Uncaught exception: Cannot call method hasOwnProperty of null Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624342] Re: tst_textarea.11.qml unit test fails
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1624342 Title: tst_textarea.11.qml unit test fails Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: Fails with Qt 5.6. FAIL! : components::TextAreaAPI::test_0_color() TextArea.color is same as TextEdit.canUndo Actual (): #5d5d5d Expected (): #00 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textarea.11.qml(141)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628855] Re: UITK Gallery: first click on left panel list items activates the focus frame
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1628855 Title: UITK Gallery: first click on left panel list items activates the focus frame Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: ubuntu-ui-toolkit/staging r2133 Environment: Yakkety Beta libqt5core5a: Installed: 5.6.1+dfsg-3ubuntu5~xenialoverlay1~1 How to reproduce: - build uitk source - run the gallery (./gallery.sh) - Click on a list item in the left panel Expected outcome: the list item is selected, no focus frame is shown Actual outcome: The list item is selected and the focus frame is shown around it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1628855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624342] Re: tst_textarea.11.qml unit test fails
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1624342 Title: tst_textarea.11.qml unit test fails Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Fails with Qt 5.6. FAIL! : components::TextAreaAPI::test_0_color() TextArea.color is same as TextEdit.canUndo Actual (): #5d5d5d Expected (): #00 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textarea.11.qml(141)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631941] Re: new arm64 unit test failures in components::TextInputTouchTests
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1631941 Title: new arm64 unit test failures in components::TextInputTouchTests Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: In unmodified trunk, so that may mean bug #1630906 builder problem is involved but we can't change the kernel ourselves right now. There is a Qt fix from upstream in silo https://launchpad.net/~ci- train-ppa-service/+archive/ubuntu/2055/+packages but even with that UITK fails these two tests although otherwise everything is going much better: FAIL! : components::TextInputTouchTests::test_do_not_activate_on_pressed(TextArea) Input must not be focused on press Actual (): true Expected (): false Loc: [/<>/ubuntu-ui-toolkit-1.3.2135+16.10.20161010/tests/unit/visual/tst_textinput_touch.SEGFAULT.11.qml(141)] FAIL! : components::TextInputTouchTests::test_drag_cursor_handler(TextArea) 'Caret "undefined" cannot be found!' returned FALSE. () Loc: [/<>/ubuntu-ui-toolkit-1.3.2135+16.10.20161010/tests/unit/visual/tst_textinput_touch.SEGFAULT.11.qml(266)] Those happen with both xenial and yakkety. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1631941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630167] Re: SlotsLayout with Column as mainSlot: endless loop when resizing view so that Column has negative width
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: In Progress => Fix Committed
** No longer affects: ubuntu-ui-toolkit (Ubuntu RTM)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1630167
Title:
SlotsLayout with Column as mainSlot: endless loop when resizing view
so that Column has negative width
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
With a simple code such as
import QtQuick 2.4
import Ubuntu.Components 1.3
import QtQuick.Window 2.0
Window {
SlotsLayout {
id: slotsLayout
onHeightChanged: print("SlotsLayout height",height)
width: parent.width
mainSlot: Column {
onHeightChanged: print("COlumn height",height)
onWidthChanged: console.log("Column width", width)
Rectangle {
id: rect
width: parent.width
onWidthChanged: console.log("RECT WIDTH", width)
onHeightChanged: console.log("RECT HEIGHT!", height)
height: 5
}
}
}
}
Or something similar (http://archive.is/N0jnM), when resizing the view
horizontally to only use few pixels, an infinite resizing loop starts and the
view freezes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630167/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628982] Re: Active section has no underline initially
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Zsombor Egri (zsombi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1628982 Title: Active section has no underline initially Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: bq M10 rc-proposed v199 I've noticed this in Silo Installer app but it affects other apps too. Steps to reproduce: 1. Open an app which has PageHeader with Sections 2. Notice the active section has no underline (screenshot attached) 3. Tap on that section, you will see focus frame as reported in other bug 1628855 4. Tap on the second section and again on the first section, now the active section has the underline as it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1628982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630278] Re: Multiple text selection handles visible in Notes app
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1630278 Title: Multiple text selection handles visible in Notes app Status in Ubuntu Notes app: Invalid Status in notes-app package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Hi, If I open Notes on my phone and create or edit a note, then activate a cursor/selector and keep it active while switching out and back to the app again I can now see the old handles (can't get rid of those) and I can create a new one. This way I can bring up as many cursors/selectors as I'd like. The old ones are not usable, but they are present when clearly they should not, as visible in the attached screenshot. I am running rc-proposed on MX4 - and yesterday was the first time I've seen this behaviour but I am not sure if it is a new bug or not. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/reminders-app/+bug/1630278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624340] Re: tst_textfield.11.qml unit test failures
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1624340 Title: tst_textfield.11.qml unit test failures Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Fails with Qt 5.6. FAIL! : components::TextFieldAPI::test_0_cursorRectangle() cursorRectangle 0 by default Actual (): QRectF(0, 4, 1, 16) Expected (): QRectF(0, 0, 0, 0) Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textfield.11.qml(168)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624342] Re: tst_textarea.11.qml unit test fails
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1624342 Title: tst_textarea.11.qml unit test fails Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Fails with Qt 5.6. FAIL! : components::TextAreaAPI::test_0_color() TextArea.color is same as TextEdit.canUndo Actual (): #5d5d5d Expected (): #00 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textarea.11.qml(141)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630872] Re: Clear text (x) does not clear the first suggested but not committed word
- No AP tests fail. - Word suggestions are off by default, but don't affect the test results. - The most recent change related to the clear button is confirmed to not affect this bug: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/revision/2115 - Apparently with AP we don't test the button visibility directly. - We don't force the right IM settings to reproduce it either. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1630872 Title: Clear text (x) does not clear the first suggested but not committed word Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: When the "Word suggestions" option in the "Language & Text" settings then the (x) clear button does not clear the first not committed word from the text input. It seems that the suggested word is not yet in the text innut but only in the input method and the clear button does not clear the input method. After the first word is committed, the second suggestion is cleared if you clear the content. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630872] Re: Clear text (x) does not clear the first suggested but not committed word
** Attachment added: "video20161005_175452486.mp4" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630872/+attachment/4755744/+files/video20161005_175452486.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1630872 Title: Clear text (x) does not clear the first suggested but not committed word Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: When the "Word suggestions" option in the "Language & Text" settings then the (x) clear button does not clear the first not committed word from the text input. It seems that the suggested word is not yet in the text innut but only in the input method and the clear button does not clear the input method. After the first word is committed, the second suggestion is cleared if you clear the content. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1526250] Re: Pressing Escape should close an open PickerPanel
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1526250 Title: Pressing Escape should close an open PickerPanel Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: If a DatePicker opens a PickerPanel, Escape should close it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1526250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1298306] Re: Do not hardcode ordering of day number and day name in DatePicker
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Zsombor Egri (zsombi) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1298306 Title: Do not hardcode ordering of day number and day name in DatePicker Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: In my locale, when I'm seeing the day name and day number in a sentence, I expect to have them in "day_name day_number" format. However in the DatePicker, they seem to be the other way around. I.e. "dissabte 26" (expected, correct) vs "26 dissabte" (actual, incorrect). This comes from hardcoding the ordering in DayModel.qml [1]. Instead, - the day_name, day_number ordering should be taken from the user's locale or, - alternatively, if that ordering is not available, the string should be made translatable so that translators can reorder it according to their locale by translating the SDK zsombi mentioned there is a bug in MonthModel.qml too, but I couldn't quite find it. See the attached image showing the wrong order for the day picker. [1] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/trunk/view/head:/modules/Ubuntu/Components/Pickers/DayModel.qml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1298306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1338138] Re: [sdk] Time Picker component does not respect user locale
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: Zsombor Egri (zsombi) => Christian Dywan (kalikiana)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1338138
Title:
[sdk] Time Picker component does not respect user locale
Status in Ubuntu UX:
Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
In the new clock app we are using the Date Picker component to allow
the user to choose a time. Hence the mode used was "Hours|Minutes".
However the Date Picker seems to always display the time in 24 hour
instead of using the user's locale. So whereever 12-hour time format
is required, the time picker ignores that.
The code below shows the usage in the clock app.
DatePicker {
id: _timePicker
anchors {
left: parent.left
right: parent.right
margins: units.gu(-2)
}
clip: true
mode: "Hours|Minutes"
}
-- Design solution --
https://docs.google.com/a/canonical.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#heading=h.tuxva2dtgvpk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1338138/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575893] Re: Toolbar focus & keyboard navigation
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed ** Description changed: Toolbar needs focus for keyboard navigation that works in the same way as the Sections. - These two bugs need to be fixed first: - - - https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1611327 - - https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1614541 + Bug 1611327 and bug 1614541 need to be fixed first. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1575893 Title: Toolbar focus & keyboard navigation Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: Toolbar needs focus for keyboard navigation that works in the same way as the Sections. Bug 1611327 and bug 1614541 need to be fixed first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1575893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628161] Re: SlotsLayout height is not dynamically updated when main paddings change
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1628161 Title: SlotsLayout height is not dynamically updated when main paddings change Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: You can see this in the attached testcase. When paddings are changed, the SlotsLayout height is not updated dynamically. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1628161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1586013 Title: UITK Date picker broken on xenial Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6 (right). More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml [...] FAIL! : components::DatePicker13API::test_1_changeMinimumBeforeDate() Uncaught exception: Cannot call method hasOwnProperty of null Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1626088] Re: Text handlers are upside down (over a highlighted text)
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1626088 Title: Text handlers are upside down (over a highlighted text) Status in Ubuntu UX: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: I think it was in OTA12 when someone put the text handlers over the text. As an attachment to this bug report You can see a photo how we »handle« the text with these tiny "blue dots" as I called them in another bug. Whats the problem: In order to have any control over the handlers we have to lock the screen rotation and turn the phone 180 degrees upside down. If not, whatever we want to select with the handlers is covered under our finger. Oh... You can also put the hand from over the screen as in the photo. It ain't funny neither on E4.5 nor M10. Solution: However small the handlers are, we should be able to put the finger on one of them and see what we are highlighting or where we are placing the cursor. It is at the moment impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1626088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628982] Re: Active section has no underline initially
** Tags added: regression -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1628982 Title: Active section has no underline initially Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: bq M10 rc-proposed v199 I've noticed this in Silo Installer app but it affects other apps too. Steps to reproduce: 1. Open an app which has PageHeader with Sections 2. Notice the active section has no underline (screenshot attached) 3. Tap on that section, you will see focus frame as reported in other bug 1628855 4. Tap on the second section and again on the first section, now the active section has the underline as it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1628982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628855] Re: UITK Gallery: first click on left panel list items activates the focus frame
** Tags added: regression -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1628855 Title: UITK Gallery: first click on left panel list items activates the focus frame Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: ubuntu-ui-toolkit/staging r2133 Environment: Yakkety Beta libqt5core5a: Installed: 5.6.1+dfsg-3ubuntu5~xenialoverlay1~1 How to reproduce: - build uitk source - run the gallery (./gallery.sh) - Click on a list item in the left panel Expected outcome: the list item is selected, no focus frame is shown Actual outcome: The list item is selected and the focus frame is shown around it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1628855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622577] Re: tst_pagestack_deprecated_toolbar unit test warnings with qt56
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1622577 Title: tst_pagestack_deprecated_toolbar unit test warnings with qt56 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: ubuntu@xenial1:~/dev/ubuntu-ui-toolkit/staging/tests/unit/components$ qmltestrunner -import ../../../qml/ -input tst_pagestack_deprecated_toolbar.qml qml: Page.tools is a deprecated property. Please use Page.head instead. qml: Page.tools is a deprecated property. Please use Page.head instead. qml: WARNING! Do not put Page/Tabs/PageStack inside another Page because that causes confusion which is the active page that sets the title and actions. qml: WARNING! Do not put Page/Tabs/PageStack inside another Page because that causes confusion which is the active page that sets the title and actions. * Start testing of qmltestrunner * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) PASS : qmltestrunner::PageStackAPI::initTestCase() PASS : qmltestrunner::PageStackAPI::test_active_bug1260116() QDEBUG : qmltestrunner::PageStackAPI::test_active_bug1260116() qml: Page.tools is a deprecated property. Please use Page.head instead. PASS : qmltestrunner::PageStackAPI::test_currentPage() PASS : qmltestrunner::PageStackAPI::test_depth() PASS : qmltestrunner::PageStackAPI::test_pop_to_tabs_bug1316736() PASS : qmltestrunner::PageStackAPI::test_tabs_inside_stack_bug1187850() PASS : qmltestrunner::PageStackAPI::test_title_bug1143345_bug1317902() PASS : qmltestrunner::PageStackAPI::test_tools_bug1126197() QDEBUG : qmltestrunner::PageStackAPI::test_tools_bug1126197() qml: Page.tools is a deprecated property. Please use Page.head instead. PASS : qmltestrunner::PageStackAPI::cleanupTestCase() QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null Totals: 9 passed, 0 failed, 0 skipped, 0 blacklisted * Finished testing of qmltestrunner * To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1622577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627978] [NEW] Different sized/ themed mouse pointers
Public bug reported: Somehow headers have larger mouse pointers with a theme different to other components. This seems like a subtle bug, but it's rather confusing. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1627978 Title: Different sized/ themed mouse pointers Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Somehow headers have larger mouse pointers with a theme different to other components. This seems like a subtle bug, but it's rather confusing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1627978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514860] Re: OptionSelector does not work with keyboard
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1514860 Title: OptionSelector does not work with keyboard Status in Canonical System Image: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: OptionSelector does not fully work with only keyboard. There is no way to select a option on OptionSelector using only the keyboard. Pressing the arrows does not navigate on the options. And it does not have any visual feedback that it contains focus. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585996] Re: UITK gallery: can't open subpages on Qt 5.6 because of TypeError
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1585996 Title: UITK gallery: can't open subpages on Qt 5.6 because of TypeError Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: On Qt 5.6 I can't seem to be able to open subpages in UITK Gallery (installed from Store). In logs I have: qml: sourcePage must be added to the view to add new page. 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/1585996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595461] Re: API file uses namespace inconsistently
** Changed in: ubuntu-sdk-api Assignee: (unassigned) => Christian Dywan (kalikiana) ** Changed in: ubuntu-sdk-api Status: New => In Progress ** Changed in: ubuntu-sdk-api Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1595461 Title: API file uses namespace inconsistently Status in Ubuntu SDK API: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: With the recent move of c++ types from Ubuntu.Components plugin into UbuntuToolkit and embedding them into a namespace caused API dump to use the namespace inconsistently. In some places has a "." in other places a "::". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-sdk-api/+bug/1595461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1626445] Re: lttng shouldn't be enabled out of the box/ incompatible with snappy confinement
** Package changed: ubuntu-ui-toolkit (Ubuntu) => ubuntu-app-launch (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1626445 Title: lttng shouldn't be enabled out of the box/ incompatible with snappy confinement Status in ubuntu-app-launch package in Ubuntu: New Bug description: As I understand it, lttng shouldn't be used out of the box - I'm seeing apparmor complaining about it, though. The other aspect of it is the fact that it's using a folder apparmor won't allow under snap confinement. I realize this is a hybrid bug, but I don't know exactly what to expect for either of these, I'm really filing it based on the symptoms for now. $ snap install dekko --edge --devmode $ snappy-debug.security scanlog & $ /snap/bin/dekko Log: apparmor="ALLOWED" operation="open" profile="snap.dekko.dekko" name="/dev/shm/lttng-ust-wait-6-1000" pid=3230 comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Dekko doesn't link to lttng: $ ldd /snap/dekko/current/usr/bin/dekko | grep lttng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1626445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1626445] Re: lttng shouldn't be enabled out of the box/ incompatible with snappy confinement
** Attachment added: "Abbreviated /proc/*/maps for dekko, containing references to lttng" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1626445/+attachment/4746090/+files/maps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1626445 Title: lttng shouldn't be enabled out of the box/ incompatible with snappy confinement Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: As I understand it, lttng shouldn't be used out of the box - I'm seeing apparmor complaining about it, though. The other aspect of it is the fact that it's using a folder apparmor won't allow under snap confinement. I realize this is a hybrid bug, but I don't know exactly what to expect for either of these, I'm really filing it based on the symptoms for now. $ snap install dekko --edge --devmode $ snappy-debug.security scanlog & $ /snap/bin/dekko Log: apparmor="ALLOWED" operation="open" profile="snap.dekko.dekko" name="/dev/shm/lttng-ust-wait-6-1000" pid=3230 comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Dekko doesn't link to lttng: $ ldd /snap/dekko/current/usr/bin/dekko | grep lttng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1626445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1626445] [NEW] lttng shouldn't be enabled out of the box/ incompatible with snappy confinement
Public bug reported: As I understand it, lttng shouldn't be used out of the box - I'm seeing apparmor complaining about it, though. The other aspect of it is the fact that it's using a folder apparmor won't allow under snap confinement. I realize this is a hybrid bug, but I don't know exactly what to expect for either of these, I'm really filing it based on the symptoms for now. $ snap install dekko --edge --devmode $ snappy-debug.security scanlog & $ /snap/bin/dekko Log: apparmor="ALLOWED" operation="open" profile="snap.dekko.dekko" name="/dev/shm/lttng-ust-wait-6-1000" pid=3230 comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Dekko doesn't link to lttng: $ ldd /snap/dekko/current/usr/bin/dekko | grep lttng ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1626445 Title: lttng shouldn't be enabled out of the box/ incompatible with snappy confinement Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: As I understand it, lttng shouldn't be used out of the box - I'm seeing apparmor complaining about it, though. The other aspect of it is the fact that it's using a folder apparmor won't allow under snap confinement. I realize this is a hybrid bug, but I don't know exactly what to expect for either of these, I'm really filing it based on the symptoms for now. $ snap install dekko --edge --devmode $ snappy-debug.security scanlog & $ /snap/bin/dekko Log: apparmor="ALLOWED" operation="open" profile="snap.dekko.dekko" name="/dev/shm/lttng-ust-wait-6-1000" pid=3230 comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Dekko doesn't link to lttng: $ ldd /snap/dekko/current/usr/bin/dekko | grep lttng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1626445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1586013 Title: UITK Date picker broken on xenial Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6 (right). More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml [...] FAIL! : components::DatePicker13API::test_1_changeMinimumBeforeDate() Uncaught exception: Cannot call method hasOwnProperty of null Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610230] Re: tst_expandablescolumn11 fails with Qt 5.6
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625507] Re: Build fails on QT_ASCII_CAST_WARN in QString.replace
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1625507
Title:
Build fails on QT_ASCII_CAST_WARN in QString.replace
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
Something changed, I don't know if it's in UITK, gcc or Qt, but I can
no longer build UITK without running into this warning:
./src/UbuntuToolkit/ucaction.cpp: In member function ‘QString
UCAction::text()’:
./src/UbuntuToolkit/ucaction.cpp:226:38 error: ‘QString::QString(const
char*)’ is deprecated [-Werror=deprecated-declarations]
displayText.replace("&&", "");
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:41:0,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:37,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
from ../../include/UbuntuToolkit/UbuntuToolkitDepends:3:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:654:31 note: declared here
inline QT_ASCII_CAST_WARN QString(const char *ch)
^
./src/UbuntuToolkit/ucaction.cpp:226:38 error: ‘QString::QString(const
char*)’ is deprecated [-Werror=deprecated-declarations]
displayText.replace("&&", "");
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:41:0,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:37,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
from ../../include/UbuntuToolkit/UbuntuToolkitDepends:3:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:654:31 note: declared here
inline QT_ASCII_CAST_WARN QString(const char *ch)
^
cc1plus: all warnings being treated as errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1625507/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514860] Re: OptionSelector does not work with keyboard
** No longer affects: ubuntu-ui-toolkit (Ubuntu RTM) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1514860 Title: OptionSelector does not work with keyboard Status in Canonical System Image: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: OptionSelector does not fully work with only keyboard. There is no way to select a option on OptionSelector using only the keyboard. Pressing the arrows does not navigate on the options. And it does not have any visual feedback that it contains focus. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625507] [NEW] Build fails on QT_ASCII_CAST_WARN in QString.replace
Public bug reported:
Something changed, I don't know if it's in UITK, gcc or Qt, but I can no
longer build UITK without running into this warning:
./src/UbuntuToolkit/ucaction.cpp: In member function ‘QString UCAction::text()’:
./src/UbuntuToolkit/ucaction.cpp:226:38 error: ‘QString::QString(const char*)’
is deprecated [-Werror=deprecated-declarations]
displayText.replace("&&", "");
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:41:0,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:37,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
from ../../include/UbuntuToolkit/UbuntuToolkitDepends:3:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:654:31 note: declared here
inline QT_ASCII_CAST_WARN QString(const char *ch)
^
./src/UbuntuToolkit/ucaction.cpp:226:38 error: ‘QString::QString(const char*)’
is deprecated [-Werror=deprecated-declarations]
displayText.replace("&&", "");
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:41:0,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:37,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
from ../../include/UbuntuToolkit/UbuntuToolkitDepends:3:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:654:31 note: declared here
inline QT_ASCII_CAST_WARN QString(const char *ch)
^
cc1plus: all warnings being treated as errors
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Critical
Assignee: Christian Dywan (kalikiana)
Status: In Progress
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-
toolkit/literalStringReplace
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1625507
Title:
Build fails on QT_ASCII_CAST_WARN in QString.replace
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress
Bug description:
Something changed, I don't know if it's in UITK, gcc or Qt, but I can
no longer build UITK without running into this warning:
./src/UbuntuToolkit/ucaction.cpp: In member function ‘QString
UCAction::text()’:
./src/UbuntuToolkit/ucaction.cpp:226:38 error: ‘QString::QString(const
char*)’ is deprecated [-Werror=deprecated-declarations]
displayText.replace("&&", "");
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:41:0,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:37,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
from ../../include/UbuntuToolkit/UbuntuToolkitDepends:3:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:654:31 note: declared here
inline QT_ASCII_CAST_WARN QString(const char *ch)
^
./src/UbuntuToolkit/ucaction.cpp:226:38 error: ‘QString::QString(const
char*)’ is deprecated [-Werror=deprecated-declarations]
displayText.replace("&&", "");
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:41:0,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:37,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
from ../../include/UbuntuToolkit/UbuntuToolkitDepends:3:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:654:31 note: declared here
inline QT_ASCII_CAST_WARN QString(const char *ch)
^
cc1plus: all warnings being treated as errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1625507/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1586013 Title: UITK Date picker broken on xenial Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6 (right). More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml [...] FAIL! : components::DatePicker13API::test_1_changeMinimumBeforeDate() Uncaught exception: Cannot call method hasOwnProperty of null Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570478] Re: Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1570478 Title: Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: Update: Qt 5.6.1 and UITK 20160716: 13 failures which MUST be fixed: dpr2 dpr3 performance --- original report --- Considerably less than on amd64 (bug #1560004), but still some now seen with the new UITK 20160412 and the latest Qt builds: 1 failures which MUST be fixed: tst_performance tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/performance/performance [...] #7 0x77c32034 in UCTheme::PaletteConfig::restorePalette() (this=0xeb8160) at ./src/Ubuntu/UbuntuToolkit/uctheme.cpp:278 #8 0x77c2ebf3 in UCTheme::~UCTheme() (this=0xeb8160, __in_chrg=) at ./src/Ubuntu/UbuntuToolkit/uctheme_p.h:125 https://launchpadlibrarian.net/253810125/buildlog_ubuntu-xenial-armhf .ubuntu-ui- toolkit_1.3.1938+16.04.20160412build1~xenial1~qt560~1_BUILDING.txt.gz 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/1570478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590005] Re: Focus can go be moved inside ListItem in a horizontal ListView
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1590005
Title:
Focus can go be moved inside ListItem in a horizontal ListView
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
Run this code:
import QtQuick 2.4
import Ubuntu.Components 1.3
Item {
width: units.gu(50)
height: units.gu(50)
ListView {
anchors.fill: parent
model: 10
orientation: ListView.Horizontal
delegate: ListItem {
width: units.gu(5)
height: units.gu(5)
Button {
activeFocusOnTab: false
anchors {
fill: parent
margins: units.gu(1)
}
text: "Button #" + index
}
}
}
}
Use TAB to select the first ListItem in the list. Pressing the LEFT
arrow after that will put the focus on the Button in the first
ListItem (you can see the focus outline changing).
The same happens when using keyboard navigation to go to the last
ListItem and then pressing the RIGHT cursor key.
I could not reproduce the issue with a vertical ListView.
This gives problems for the new Toolbar with scrolling icons inside
it, because there I am wrapping an AbstractButton inside a ListItem in
order to be able to get cursor key navigation until this bug is fixed:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
toolkit/+bug/1573616
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1590005/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1611327] Re: Disabled ListItem inside ListView takes focus but does not show focus ring
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1611327
Title:
Disabled ListItem inside ListView takes focus but does not show focus
ring
Status in Ubuntu UX:
Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
Items outside of a ListView are skipped when using keyboard navigation
to change the focus. However, a ListItem inside a ListView takes the
focus even when it is disabled, but it does not show the focus frame
when focused.
For example, execute this QML program:
import QtQuick 2.4
import Ubuntu.Components 1.3
Item {
width: units.gu(50)
height: units.gu(50)
ListView {
anchors.fill: parent
delegate: ListItem {
enabled: index != 2
Label {
anchors.centerIn: parent
text: parent.enabled ? "enabled" : "disabled"
}
}
model: 5
}
}
Press TAB to focus on the ListView. Then press the down-cursor-key
twice to move the focus down inside the ListView. The focus will be on
the disabled item, but not focus frame is visible This is confusing
for the user since the focus seems to disappear, and the Item where
the focus seems to be (although invisible) cannot be triggered because
it is disabled.
Note: When fixing this bug, also test the solution for Horizontal
ListViews (and RightToLeft and BottomToTop directions), since I
encountered this bug in the scrolling toolbar (in progress) that has a
Horizontal, RightToLeft ListView.
==UX Fix===
Bypass focus for a disabled item and show focus immediately for the
next available enabled item.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1611327/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1586013 Title: UITK Date picker broken on xenial Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6 (right). More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml [...] FAIL! : components::DatePicker13API::test_1_changeMinimumBeforeDate() Uncaught exception: Cannot call method hasOwnProperty of null Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556785] Re: Blinking cursor is higher than the text (especially on the lock screen password entry)
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1556785 Title: Blinking cursor is higher than the text (especially on the lock screen password entry) Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Unity8's blinking cursor is higher than the text. You can see this on desktop, both on the Unity8 login screen (password entry), and in System Settings "Search". In both cases the blue cursor appears to be the right size, but is several pixels higher than the text. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1556785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556785] Re: Blinking cursor is higher than the text (especially on the lock screen password entry)
It seems to me like this is merely the space left for accents - even if the text is "AEOU" the cursor (and selection) will be high enough to accomodate for "ÁÉÓÚ". If you use other characters, say "私は猫がすきです", the spacing will differ. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1556785 Title: Blinking cursor is higher than the text (especially on the lock screen password entry) Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Unity8's blinking cursor is higher than the text. You can see this on desktop, both on the Unity8 login screen (password entry), and in System Settings "Search". In both cases the blue cursor appears to be the right size, but is several pixels higher than the text. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1556785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Zsombor Egri (zsombi) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1586013 Title: UITK Date picker broken on xenial Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6 (right). More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml [...] FAIL! : components::DatePicker13API::test_1_changeMinimumBeforeDate() Uncaught exception: Cannot call method hasOwnProperty of null Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552773] Re: _optionselector.py looks for Label delegates instead of UCLabel
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Christian Dywan (kalikiana) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1552773 Title: _optionselector.py looks for Label delegates instead of UCLabel Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: The autopilot helper for optionselector seeks Label delegates, rather than UCLabel delegates. -- def get_selected_text(self): """gets the text of the currently selected item""" option_selector_delegate = self.select_single( 'OptionSelectorDelegate', focus='True') current_label = option_selector_delegate.select_single( 'Label', visible='True') return current_label.text def get_current_label(self): """gets the text of the currently selected item""" option_selector_delegate = self.select_single( 'OptionSelectorDelegate', focus='True') current_label = option_selector_delegate.select_single( 'Label', visible='True') return current_label -- Those select_single calls should use UCLabel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1552773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461571] Re: Text field clear button does not work with first predicted word
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1461571 Title: Text field clear button does not work with first predicted word Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed #219 When entering text into a text field using OSK with predictive text enabled, it is not possible to clear the first word using the clear button. Steps: 1) Load Ubuntu UI Toolkit Gallery 2) Select Text Field -> Standard 3) Type in a few characters using the OSK, so that the word in text field remains underlined and suggestions are displayed by OSK. 4) Press clear button in the text field. Expected result: The text in the text field should be cleared. Actual result: The clear button does not work and the text remains. Note that if there are multiple words entered then the clear button will work as expected. This problem only happens if there is only 1 word that is being deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1461571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1587580] Re: No way to escape an ampersand in UCAction
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1587580
Title:
No way to escape an ampersand in UCAction
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress
Bug description:
Let's say we have an Ubuntu.Action as follow:
import Ubuntu.Components 1.3 as Ubuntu
Ubuntu.Action {
text: "Apps & Scopes"
}
UCAction translates the ampersand as a mnemonic, using QKeySequence.
A way to escape a mnemonic in Qt is to add another ampersand. The resulting
string is "Apps && Scopes".
The UITK component seems not to take in account this situation, since:
- How the string should be shown in e.g. an ActionBar:
"Apps & Scopes"
- How the string is displayed instead in an ActionBar:
"Apps && Scopes"
QKeySequence returns no mnemonic as expected, but UCAction shows two
ampersands.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1587580/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514841] Re: TextArea.text with autoSize=true is cut at the bottom
** Summary changed: - [Ubuntu phone] Text in text entry is cut at the bottom (TextArea with autoSize=true) + TextArea.text with autoSize=true is cut at the bottom -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1514841 Title: TextArea.text with autoSize=true is cut at the bottom Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: When I get a text message and try to answer from the notification text entry, the text I write is cut at the bottom. Also the scrollbar is visible. Please see attached screenshot. The text reads: „Hej zgadza się”. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1514841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580974] Re: Button label should ellipsize in the middle
** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1580974 Title: Button label should ellipsize in the middle Status in Ubuntu UX: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: As per the Buttons spec "In the unlikely event that a button’s label is too long for the width available, it should be ellipsized in the middle" Currently the Label in ButtonForeground ellipsizes in the end. Also quoting Matthew on the reasoning: (1 Two buttons with long but similar labels are more likely to differ at their ends than their middles (e.g. “Change This Event Only” vs. “Change This And Future Events”). (2 End ellipsis is already used to mean “you’ll need to do something else after tapping this”. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1580974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580974] Re: Button label should ellipsize in the middle
I only realize this now as I didn't investigate that much in the context of the original discussion: we never elide in the middle ATM - before changing this I think we need to be certain that other cases shouldn't be changed, or that this should be changed in the spec, since it would seem rather strange to have only a single case of middle ellipsis. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1580974 Title: Button label should ellipsize in the middle Status in Ubuntu UX: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: As per the Buttons spec "In the unlikely event that a button’s label is too long for the width available, it should be ellipsized in the middle" Currently the Label in ButtonForeground ellipsizes in the end. Also quoting Matthew on the reasoning: (1 Two buttons with long but similar labels are more likely to differ at their ends than their middles (e.g. “Change This Event Only” vs. “Change This And Future Events”). (2 End ellipsis is already used to mean “you’ll need to do something else after tapping this”. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1580974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614045] Re: tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1614045 Title: tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: The cases for ComboButton in tst_focus.13.qml listed in test_trigger_via_keyboard_data use "button" as the item, which means they're not actually testing a ComboButton. Also the comboButton has no override mechanism in the test so it wouldn't be testable as-is. This needs to be corrected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1614045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620991] Re: Anchoring warnings in Buttons page in UITK Gallery
=== modified file 'src/imports/Components/1.3/ComboButton.qml'
--- src/imports/Components/1.3/ComboButton.qml 2016-09-13 15:01:14 +
+++ src/imports/Components/1.3/ComboButton.qml 2016-09-13 15:57:46 +
@@ -395,6 +395,7 @@
}
}
Scrollbar {
+parent: comboHolder.parent
flickableItem: comboHolder
}
This appears to work. However no test seems to catch this problem - we
need to find a way to test that this is actually fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1620991
Title:
Anchoring warnings in Buttons page in UITK Gallery
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
ubuntu-ui-toolkit/staging, r2090
1) Build uitk
2) run gallery with ./gallery.sh
3) Open Buttons page
Expected outcome:
no warnings
Actual outcome:
A few "QML Scrollbar: Cannot anchor to an item that isn't a parent or
sibling."
Explanation:
That happens because Scrollbar anchors to the flickable item, but the
ComboButton code has a hack that changes the parent of the Flickable to
actually be Flickable's child. As a consequence Flickable is not a sibling of
the scrollbar anymore, thus producing the anchor-related warning.
See http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
toolkit/staging/annotate/2090/src/Ubuntu/Components/1.3/ComboButton.qml#L354
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1620991/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614045] Re: tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1614045 Title: tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The cases for ComboButton in tst_focus.13.qml listed in test_trigger_via_keyboard_data use "button" as the item, which means they're not actually testing a ComboButton. Also the comboButton has no override mechanism in the test so it wouldn't be testable as-is. This needs to be corrected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1614045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598920] Re: MainView intercepts MouseArea's cursorShape property
Doesn't appear to be a problem anymore - I see the cross shaped mouse
pointer running the example snippet with qmlscene or ubuntu-ui-toolkit-
launcher, with staging/ Xenial/ Qt 5.6.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: Dubstar_04 (dubstar-04) => Christian Dywan (kalikiana)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1598920
Title:
MainView intercepts MouseArea's cursorShape property
Status in Canonical System Image:
Confirmed
Status in qtubuntu package in Ubuntu:
Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Status in unity8 package in Ubuntu:
Invalid
Bug description:
The MouseArea CursorShape doesnt have any effect.
Docs Here: http://doc.qt.io/qt-5/qml-qtquick-mousearea.html
Expected Behavour:
Mouse image shows selected Qt cursor
Experienced Behavour:
The regular arrow is displayed.
Example Code:
import QtQuick 2.4
import Ubuntu.Components 1.3
MainView {
objectName: "mainView"
applicationName: "mouseTest"
width: units.gu(100)
height: units.gu(75)
Rectangle{
anchors.fill: parent
color: UbuntuColors.coolGrey
MouseArea{
anchors.fill: parent
cursorShape: Qt.CrossCursor
hoverEnabled: true
onClicked: console.log("In MouseArea")
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598920/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616858] Re: ActionBar overflow issues with Qt 5.6
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1616858 Title: ActionBar overflow issues with Qt 5.6 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: With Qt 5.6 I'm seeing problems with the ActionBar. 1. tst_actionbar.13.qml passes but there's lots of warnings: QWARN : components::ActionBarApi::test_number_of_actions_in_overflow() ./_build/qml/Ubuntu/Components/Themes/Ambiance/1.3/OverflowPanel.qml:66: ReferenceError: modelData is not defined The unit test should be failing. And obviously there's a bug here. 2. Running tst_actionbar.13.qml in the launcher the overflow button is absent. 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/1616858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1621509] Re: ListView with extension from UbuntuToolkit updates its model after the component is completed
** Description changed:
This is the cause for the Sections index resetting after initialization,
- see bug https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
- toolkit/+bug/1610231
+ see bug 1610231.
Create the file ModelTest.qml:
+
import QtQuick 2.4
Item {
- id: root
- width: 800
- height: 600
+ id: root
+ width: 800
+ height: 600
- ListView {
- model: root.model
- onModelChanged: print("LV model changed to "+model[0]+" "+model[1]+"
"+model[2]+" "+model[3])
- Component.onCompleted: print("ListView completed.")
- }
- Component.onCompleted: print("root item completed.")
+ ListView {
+ model: root.model
+ onModelChanged: print("LV model changed to "+model[0]+" "+model[1]+"
"+model[2]+" "+model[3])
+ Component.onCompleted: print("ListView completed.")
+ }
+ Component.onCompleted: print("root item completed.")
- property list objectList
- onObjectListChanged: print("root.objectList changed to "+objectList[0]+"
"+objectList[1]+" "+objectList[2])
- property var model: objectList
+ property list objectList
+ onObjectListChanged: print("root.objectList changed to "+objectList[0]+"
"+objectList[1]+" "+objectList[2])
+ property var model: objectList
}
+ And run this program modelInst.qml:
- and run this program modelInst.qml:
import QtQuick 2.4
import Ubuntu.Components 1.3
ModelTest {
- QtObject {
- objectName: "one"
- id: objectOne
- }
- QtObject {
- objectName: "two"
- id: objectTwo
- }
- QtObject{
- objectName: "three"
- id: objectThree
- }
+ QtObject {
+ objectName: "one"
+ id: objectOne
+ }
+ QtObject {
+ objectName: "two"
+ id: objectTwo
+ }
+ QtObject{
+ objectName: "three"
+ id: objectThree
+ }
-objectList: [objectOne, objectTwo, objectThree]
+ objectList: [objectOne, objectTwo, objectThree]
}
+ The output is as follows:
- The output is as follows:
- ubuntu@xenial1:~/dev/ubuntu-ui-toolkit/m/qt56fixes2sections$ qmlscene
modelInst.qml
+ $ qmlscene modelInst.qml
qml: root.objectList changed to undefined undefined undefined
qml: root.objectList changed to QObject(0x118abf0, "one") undefined undefined
qml: root.objectList changed to QObject(0x118abf0, "one") QObject(0x118a110,
"two") undefined
qml: root.objectList changed to QObject(0x118abf0, "one") QObject(0x118a110,
"two") QObject(0x1182f80, "three")
qml: LV model changed to QObject(0x118abf0, "one") QObject(0x118a110, "two")
QObject(0x1182f80, "three") undefined
qml: LV model changed to QObject(0x118abf0, "one") QObject(0x118a110, "two")
QObject(0x1182f80, "three") undefined
qml: root item completed.
qml: ListView completed.
qml: LV model changed to QObject(0x118abf0, "one") QObject(0x118a110, "two")
QObject(0x1182f80, "three") undefined
qml: LV model changed to QObject(0x118abf0, "one") QObject(0x118a110, "two")
QObject(0x1182f80, "three") undefined
- so the model ic changed AFTER the ListView and root item are completed.
+ So the model is changed AFTER the ListView and root item are completed.
- When the Ubuntu.Components import is removed, the output is correct, like
this:
- ubuntu@xenial1:~/dev/ubuntu-ui-toolkit/m/qt56fixes2sections$ qmlscene
modelInst.qml
+ When the Ubuntu.Components import is removed the output is correct:
+
+ $ qmlscene modelInst.qml
qml: root.objectList changed to undefined undefined undefined
qml: root.objectList changed to QObject(0x171c8d0, "one") undefined undefined
qml: root.objectList changed to QObject(0x171c8d0, "one") QObject(0x171d290,
"two") undefined
qml: root.objectList changed to QObject(0x171c8d0, "one") QObject(0x171d290,
"two") QObject(0x171d420, "three")
qml: LV model changed to QObject(0x171c8d0, "one") QObject(0x171d290, "two")
QObject(0x171d420, "three") undefined
qml: LV model changed to QObject(0x171c8d0, "one") QObject(0x171d290, "two")
QObject(0x171d420, "three") undefined
qml: root item completed.
qml: ListView completed.
-
- Also, if there is no ListView inside ModelTest.qml, then nothing is updated
after the items are completed. So I suspect the issue is in our ListView
extension.
+ Also, if there is no ListView inside ModelTest.qml, then nothing is
+ updated after the items are completed. So I suspect the issue is in our
+ ListView extension.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1621509
Title:
ListView with extension from UbuntuToolkit updates its model after the
component is completed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
This is the cause for the Sections index resetting after
initialization, see bug 1610231.
Create the file
[Touch-packages] [Bug 1620553] Re: [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable
The new plugin indeed seems to be synchronous - in the UI Toolkit we
merely use HapticsEffect.play(), so nothing to do on that side.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
[Krillin] Taps are delayed by 1-2seconds, although gestures are not.
Keyboard is thus unusable
Status in platform-api package in Ubuntu:
Confirmed
Bug description:
Krillin, rc-proposed/bq_aquaris.en r422
UPDATE: see comment #5, it turns out it's the haptics plugin doing
SYNC dbus calls and blocking the UI thread when the dbus service does
not reply or the replies come with a big delay
Description:
All at once taps have become incredibly delayed, by 1 or 2 secs.
Gestures still work ok, no delay there.
Swiping the greeter -> no delay. Tapping numbers to input code on the greeter
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to
only be a problem of unity8 clients, but also unity8 itself.
I have no idea why horizontal/vertical swipes would be unaffected, though.
The virtual keyboard is also completely unusable because of the huge
delay that each tap has.
Also noticed that the vibration is gone, taps don't trigger vibration
anymore.
Webview also seemed to be unaffected by the delays (although I'm not
entirely sure, the bug is now gone)
I also restarted unity8 and unity8-dash with Mir input logging enabled. That
showed that the touch events were being delivered as expected, no delay.
restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log
Restarting lightdm (that forces the restart of unity-system-
compositor) fixed the issue.
Additional info: I had Mir touchspots visualization enabled, which are
known to cause more stuttering, but I think they're unlikely to be the
cause of this bug, I had them enabled for 2 weeks and haven't noticed
any problem like this before.
This is the log from a tap on an icon in the shell:
[2016-09-06 10:52:51.876400] input-receiver: Received
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0,
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963,
minor=0, size=19.963}, modifiers=1)
[2016-09-06 10:52:51.953821] input-receiver: Received
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0,
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137,
major=19.963, minor=0, size=19.963}, modifiers=1)
[2016-09-06 10:52:51.954343] input-receiver: Received
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0,
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963,
minor=0, size=19.963}, modifiers=1)
SEE VIDEO ATTACHMENT BELOW
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/platform-api/+bug/1620553/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620553] Re: [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable
** Changed in: platform-api (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
[Krillin] Taps are delayed by 1-2seconds, although gestures are not.
Keyboard is thus unusable
Status in platform-api package in Ubuntu:
Confirmed
Bug description:
Krillin, rc-proposed/bq_aquaris.en r422
UPDATE: see comment #5, it turns out it's the haptics plugin doing
SYNC dbus calls and blocking the UI thread when the dbus service does
not reply or the replies come with a big delay
Description:
All at once taps have become incredibly delayed, by 1 or 2 secs.
Gestures still work ok, no delay there.
Swiping the greeter -> no delay. Tapping numbers to input code on the greeter
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to
only be a problem of unity8 clients, but also unity8 itself.
I have no idea why horizontal/vertical swipes would be unaffected, though.
The virtual keyboard is also completely unusable because of the huge
delay that each tap has.
Also noticed that the vibration is gone, taps don't trigger vibration
anymore.
Webview also seemed to be unaffected by the delays (although I'm not
entirely sure, the bug is now gone)
I also restarted unity8 and unity8-dash with Mir input logging enabled. That
showed that the touch events were being delivered as expected, no delay.
restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log
Restarting lightdm (that forces the restart of unity-system-
compositor) fixed the issue.
Additional info: I had Mir touchspots visualization enabled, which are
known to cause more stuttering, but I think they're unlikely to be the
cause of this bug, I had them enabled for 2 weeks and haven't noticed
any problem like this before.
This is the log from a tap on an icon in the shell:
[2016-09-06 10:52:51.876400] input-receiver: Received
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0,
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963,
minor=0, size=19.963}, modifiers=1)
[2016-09-06 10:52:51.953821] input-receiver: Received
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0,
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137,
major=19.963, minor=0, size=19.963}, modifiers=1)
[2016-09-06 10:52:51.954343] input-receiver: Received
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0,
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963,
minor=0, size=19.963}, modifiers=1)
SEE VIDEO ATTACHMENT BELOW
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/platform-api/+bug/1620553/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598920] Re: MainView intercepts MouseArea's cursorShape property
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: (unassigned) => Dubstar_04 (dubstar-04)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1598920
Title:
MainView intercepts MouseArea's cursorShape property
Status in Canonical System Image:
Confirmed
Status in qtubuntu package in Ubuntu:
Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
Invalid
Bug description:
The MouseArea CursorShape doesnt have any effect.
Docs Here: http://doc.qt.io/qt-5/qml-qtquick-mousearea.html
Expected Behavour:
Mouse image shows selected Qt cursor
Experienced Behavour:
The regular arrow is displayed.
Example Code:
import QtQuick 2.4
import Ubuntu.Components 1.3
MainView {
objectName: "mainView"
applicationName: "mouseTest"
width: units.gu(100)
height: units.gu(75)
Rectangle{
anchors.fill: parent
color: UbuntuColors.coolGrey
MouseArea{
anchors.fill: parent
cursorShape: Qt.CrossCursor
hoverEnabled: true
onClicked: console.log("In MouseArea")
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598920/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585996] Re: UITK gallery: can't open subpages on Qt 5.6 because of TypeError
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Christian Dywan (kalikiana) => (unassigned) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Zsombor Egri (zsombi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1585996 Title: UITK gallery: can't open subpages on Qt 5.6 because of TypeError Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: On Qt 5.6 I can't seem to be able to open subpages in UITK Gallery (installed from Store). In logs I have: qml: sourcePage must be added to the view to add new page. 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/1585996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618581] Re: The margin to swipe from top in QQuickFlickable is not enough
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: (unassigned) => Zoltan Balogh (bzoltan)
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1618581
Title:
The margin to swipe from top in QQuickFlickable is not enough
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress
Bug description:
On krillin device many of the UITK autopilot tests fail with this
traceback:
File
"/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_flickable.py",
line 164, in swipe_child_into_view
self._swipe_non_visible_child_into_view(child, containers)
File "/usr/lib/python3/dist-packages/autopilot/logging.py", line 46, in inner
return f(instance, *args, **kwargs)
File
"/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_flickable.py",
line 174, in _swipe_non_visible_child_into_view
self.swipe_to_show_more_above(containers)
File
"/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_flickable.py",
line 190, in swipe_to_show_more_above
self._swipe_to_show_more('above', containers)
File
"/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_flickable.py",
line 252, in _swipe_to_show_more
self._slow_drag(start_x, stop_x, start_y, stop_y, rate)
File
"/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_flickable.py",
line 137, in _slow_drag
raise _common.ToolkitException('Could not swipe in the flickable.')
ubuntuuitoolkit._custom_proxy_objects._common.ToolkitException: Could not
swipe in the flickable.
In the _swipe_to_show_more() when the direction is 'above' the starting Y
should be in the flickable. The self.margin_to_swipe_from_top is set to
units.gu(1) what seems to be too little.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1618581/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617745] Re: popupUtils.open() won't work inside Window with "null" caller
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1617745
Title:
popupUtils.open() won't work inside Window with "null" caller
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
I think I found a regression with popupUtils.open() in rc-proposed
(r512 on mako):
I have some code which is invoking a dialog in this way:
PopupUtils.open(Qt.resolvedUrl("DeleteConfirmation.qml"), null, {
... params... })
This now doesn't work, but it works on OTA-12.
This can cause serious regression in third party applications, if
dialogs stop appearing.
Furthermore, if I replace "null" with a valid item, things work again
but I get a warning on the console:
qml: 'caller' is DEPRECATED. It has no effect.
Which seems wrong, given that in the current stable documentation
there is absolutely no mention of the caller property being
deprecated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617745/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616868] Re: Scrollbar thumb shows as hovered after touch release
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1616868 Title: Scrollbar thumb shows as hovered after touch release Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: ubuntu-ui-toolkit r2079 The fix to bug #1608897 created another issue. Since MouseArea does not get the exited() signal on touch release (to be investigated if that's intended), dragging the thumb with touchscreen and releasing while the finger is still inside the area of the thumb will cause the thumb to show as hovered even after release. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1616868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616926] Re: Scrollbar thumb shows as hovered after mouse is released outside the thumb
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1616926 Title: Scrollbar thumb shows as hovered after mouse is released outside the thumb Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: ubuntu-ui-toolkit r2079 The fix to bug #1608897 created another issue. The code that checks if the thumb is being hovered currently only checks the y position of the input event, an optimization that worked well with the previous assumption that releasing mouse would always reset the hover state (but that was causing bug #1608897). There were, in fact, 2 cases before: - input device moves away (no pressed buttons) -> onExited is fired -> hover is reset - input device moves away while press-hold is in progress --> onRelease will reset hover Now that the behaviour changed and release does not reset the hover state, we obviously need to check both x and y position To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1616926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617818] Re: [ActionBar] Actions are shown in reverse order
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Tim Peeters (tpeeters) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1617818 Title: [ActionBar] Actions are shown in reverse order Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Please try the attached test case: the delete action is the last one, but it appears as the first one. If you add one fourth item to the action list, then the items get sorted correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618007] Re: Invalid property assignment in ActivityIndicatorStyle.qml
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Fix Committed ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Florian Boucault (fboucault) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1618007 Title: Invalid property assignment in ActivityIndicatorStyle.qml Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: I get file:///usr/lib/x86_64-linux- gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24 Invalid property assignment: "implicitHeight" is a read-only property To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1618007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617745] Re: popupUtils.open() won't work inside Window with "null" caller
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1617745
Title:
popupUtils.open() won't work inside Window with "null" caller
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress
Bug description:
I think I found a regression with popupUtils.open() in rc-proposed
(r512 on mako):
I have some code which is invoking a dialog in this way:
PopupUtils.open(Qt.resolvedUrl("DeleteConfirmation.qml"), null, {
... params... })
This now doesn't work, but it works on OTA-12.
This can cause serious regression in third party applications, if
dialogs stop appearing.
Furthermore, if I replace "null" with a valid item, things work again
but I get a warning on the console:
qml: 'caller' is DEPRECATED. It has no effect.
Which seems wrong, given that in the current stable documentation
there is absolutely no mention of the caller property being
deprecated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617745/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617745] Re: Regression: popupUtils.open() won't work with "null" caller
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: (unassigned) => Christian Dywan (kalikiana)
** Summary changed:
- Regression: popupUtils.open() won't work with "null" caller
+ popupUtils.open() won't work inside Window with "null" caller
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1617745
Title:
popupUtils.open() won't work inside Window with "null" caller
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
I think I found a regression with popupUtils.open() in rc-proposed
(r512 on mako):
I have some code which is invoking a dialog in this way:
PopupUtils.open(Qt.resolvedUrl("DeleteConfirmation.qml"), null, {
... params... })
This now doesn't work, but it works on OTA-12.
This can cause serious regression in third party applications, if
dialogs stop appearing.
Furthermore, if I replace "null" with a valid item, things work again
but I get a warning on the console:
qml: 'caller' is DEPRECATED. It has no effect.
Which seems wrong, given that in the current stable documentation
there is absolutely no mention of the caller property being
deprecated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617745/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617745] Re: Regression: popupUtils.open() won't work with "null" caller
Dialog.caller is deprecated - if you use PopupUtils.open with a Dialog
you will see that warning, as documented in the docs for the Dialog
component, and it won't do anything. The same isn't true for Popover.
A test case to demonstrate what "doesn't work" would be needed, it's not
obvious from the description.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1617745
Title:
Regression: popupUtils.open() won't work with "null" caller
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
I think I found a regression with popupUtils.open() in rc-proposed
(r512 on mako):
I have some code which is invoking a dialog in this way:
PopupUtils.open(Qt.resolvedUrl("DeleteConfirmation.qml"), null, {
... params... })
This now doesn't work, but it works on OTA-12.
This can cause serious regression in third party applications, if
dialogs stop appearing.
Furthermore, if I replace "null" with a valid item, things work again
but I get a warning on the console:
qml: 'caller' is DEPRECATED. It has no effect.
Which seems wrong, given that in the current stable documentation
there is absolutely no mention of the caller property being
deprecated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617745/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616889] [NEW] ActionBar with overflow doesn't shrink
Public bug reported: The ActionBar with an overflow, as can be seen in tst_actionbar.13.qml, doesn't shrink below the space needed to show numberOfSlots buttons. That seems counterproductive when the window/ column/ device is too small, but I still want to see more buttons when possible (convergence). ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Medium Assignee: Tim Peeters (tpeeters) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1616889 Title: ActionBar with overflow doesn't shrink Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The ActionBar with an overflow, as can be seen in tst_actionbar.13.qml, doesn't shrink below the space needed to show numberOfSlots buttons. That seems counterproductive when the window/ column/ device is too small, but I still want to see more buttons when possible (convergence). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1616889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616858] [NEW] ActionBar overflow issues with Qt 5.6
Public bug reported: With Qt 5.6 I'm seeing problems with the ActionBar. 1. tst_actionbar.13.qml passes but there's lots of warnings: QWARN : components::ActionBarApi::test_number_of_actions_in_overflow() ./_build/qml/Ubuntu/Components/Themes/Ambiance/1.3/OverflowPanel.qml:66: ReferenceError: modelData is not defined The unit test should be failing. And obviously there's a bug here. 2. Running tst_actionbar.13.qml in the launcher the overflow button is absent. More information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Assignee: Tim Peeters (tpeeters) Status: New ** Tags: qt5.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1616858 Title: ActionBar overflow issues with Qt 5.6 Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: With Qt 5.6 I'm seeing problems with the ActionBar. 1. tst_actionbar.13.qml passes but there's lots of warnings: QWARN : components::ActionBarApi::test_number_of_actions_in_overflow() ./_build/qml/Ubuntu/Components/Themes/Ambiance/1.3/OverflowPanel.qml:66: ReferenceError: modelData is not defined The unit test should be failing. And obviously there's a bug here. 2. Running tst_actionbar.13.qml in the launcher the overflow button is absent. 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/1616858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615591] [NEW] Promote MainWindow to Ubuntu.Components and add unit tests
Public bug reported: Once we determine the MainWindow API ready, provided discussion around the features we want it to have has taken place, more tests should be added so all the API is covered and finally it should move from Labs to Components. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1615591 Title: Promote MainWindow to Ubuntu.Components and add unit tests Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Once we determine the MainWindow API ready, provided discussion around the features we want it to have has taken place, more tests should be added so all the API is covered and finally it should move from Labs to Components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1615591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613972] Re: Change focus colour to blue
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Christian Dywan (kalikiana) => Zsombor Egri (zsombi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1613972 Title: Change focus colour to blue Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The current focus colour (orange) need to change to blue so that it matches with the select state. The palette value for this needs to be change to affect the colour of focus everywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1613972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614045] [NEW] tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton
Public bug reported: The cases for ComboButton in tst_focus.13.qml listed in test_trigger_via_keyboard_data use "button" as the item, which means they're not actually testing a ComboButton. Also the comboButton has no override mechanism in the test so it wouldn't be testable as-is. This needs to be corrected. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Assignee: Christian Dywan (kalikiana) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1614045 Title: tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The cases for ComboButton in tst_focus.13.qml listed in test_trigger_via_keyboard_data use "button" as the item, which means they're not actually testing a ComboButton. Also the comboButton has no override mechanism in the test so it wouldn't be testable as-is. This needs to be corrected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1614045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613248] Re: Text selection handles are too small
*** This bug is a duplicate of bug 1540108 *** https://bugs.launchpad.net/bugs/1540108 ** This bug has been marked a duplicate of bug 1540108 Blue dots for text marking/placing a cursor are too small -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1613248 Title: Text selection handles are too small Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: In a text box (eg. a message in the messaging app), I find it impossible to move the edges of a selection because the handles are too small. When I do manage to grab a handle, I cannot see where I am placing it because the handle's hotspot isn't far enough away from the text so my finger covers the area I need to see. If I move my finger down, so does the selection. In practice, this means that I can never use the handles, and end up having to delete and retype anything I want to edit. This also applies to just moving the text caret, which is again difficult because I cannot see where I am going. Sorry I took this long to report this. I had assumed that this bug was obvious enough that a fix would arrive without reporting it. Maybe this is hardware specific? I'm using a bq Aquaris 4.5 on OTA-12. This may be a regression of bug 1407723, which describes exactly the same problem but is marked Fix Released. Or perhaps the fix there wasn't sufficient for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1613248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613972] Re: Change focus colour to blue
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1613972 Title: Change focus colour to blue Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The current focus colour (orange) need to change to blue so that it matches with the select state. The palette value for this needs to be change to affect the colour of focus everywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1613972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1433590
Title:
apparmor dbus denial for org.freedesktop.Accounts and make Other
vibrations work
Status in Canonical System Image:
In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
Fix Released
Status in ubuntu-system-settings package in Ubuntu:
Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Status in usensord package in Ubuntu:
Fix Committed
Bug description:
This affects vivid and (somewhat recently?) 14.09.
At some point, apps started to request access to
org.freedesktop.Accounts for something, but I'm not sure what. It has
been conjectured in this bug that it is due to vibration settings.
Filing against ubuntu-system-settings for now, but please feel free to
move to the correct package.
This happens with webapps:
Apr 7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/Accounts"
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send"
name="org.freedesktop.Accounts" pid=2632
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26"
peer_pid=1596 peer_profile="unconfined"
Apr 7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/Accounts"
interface="org.freedesktop.Accounts" member="FindUserById" mask="send"
name="org.freedesktop.Accounts" pid=2632
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26"
peer_pid=1596 peer_profile="unconfined"
and QML apps:
Apr 7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/Accounts"
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send"
name="org.freedesktop.Accounts" pid=3377
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596
peer_profile="unconfined"
Apr 7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/Accounts"
interface="org.freedesktop.Accounts" member="FindUserById" mask="send"
name="org.freedesktop.Accounts" pid=3377
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596
peer_profile="unconfined"
The following rules allow the requested access:
dbus (send)
bus=system
path="/org/freedesktop/Accounts"
interface="org.freedesktop.DBus.{Introspectable,Properties}"
member=Introspect
peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
bus=system
path="/org/freedesktop/Accounts"
interface="org.freedesktop.Accounts"
member=FindUserById
peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
bus=system
path="/org/freedesktop/Accounts/User[0-9]*"
interface="org.freedesktop.DBus.Properties"
member=Get
peer=(name=org.freedesktop.Accounts,label=unconfined),
However, the above is too lenient and constitutes a privacy leak for
apps. FindUserById could be used by a malicious app to enumerate
usernames on multiuser systems and because we can't mediate method
data with apparmor, the Get() method can be used to obtain any
information provided by this interface.
The following can be used to see what can be leaked to a malicious app:
gdbus introspect --system -d org.freedesktop.Accounts -o
/org/freedesktop/Accounts/User`id -u phablet`
This can be solved in a couple of ways:
1. add whatever information the app is trying to access to a new helper
service that only exposes things that the app needs. This could be a single
standalone service, perhaps something from ubuntu-system-settings, that could
expose any number of things-- the current locale, if the locale changed, if the
grid units changed, the vibration settings, etc. Since this service wouldn't
have any sensitive information, you could use standard dbus
properties/Get()/etc
2. add a new dbus API to an existing service such that apparmor rules can
then be used to allow by method (eg, GetVibration() or something)
I won't dictate the implementation except to mention that '1' seems
like something generally useful and I believe that it was something
the ubuntu-system-settings devs were already looking at for detecting
locale changes without rebooting.
Original description
starting an app in vivid (image 135 on arale currently)
produces a bunch of dbus denials in syslog ... (there is also a
/dev/tty one but i think this is just because soemthing tries to write
an error to console ... so transient)
http://paste.ubuntu.com/10620834/
To manage
[Touch-packages] [Bug 1585996] Re: UITK gallery: can't open subpages on Qt 5.6 because of TypeError
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1585996 Title: UITK gallery: can't open subpages on Qt 5.6 because of TypeError Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: On Qt 5.6 I can't seem to be able to open subpages in UITK Gallery (installed from Store). In logs I have: qml: sourcePage must be added to the view to add new page. 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/1585996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610208] Re: Migrate to new QT_SCALE_FACTOR in Qt 5.6
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610208] Re: Migrate to new QT_SCALE_FACTOR in Qt 5.6
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: In Progress 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610165] Re: qmltestrunner::DashContent::test_mainNavigation() does not always pass
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1610165 Title: qmltestrunner::DashContent::test_mainNavigation() does not always pass Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: It would be useful to make the test bulletproof. Here is a link to the run with unity8 8.14+16.10.20160803-0ubuntu1: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/u/unity8/20160804_211146@/log.gz -- FAIL! : qmltestrunner::DashContent::test_mainNavigation() Compared values are not the same Actual (): true Expected (): false Loc: [/tmp/autopkgtest.rL2rsf/build.OoP/unity8-8.14+16.10.20160803/tests/qmltests/Dash/tst_DashContent.qml(360)] -- A retry worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1610165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595910] Re: review input field: send button issues with predictive OSK
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1595910 Title: review input field: send button issues with predictive OSK Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Triaged Bug description: Steps to reproduce: * Make sure predictive OSK is enabled * got an app in the store and start writing a review * Just write one word, no space after it (so that it is underlined for text correction things) => actual: The send button is disabled even though the text field holds a word => expected: The send button should be enabled Most likely the Send button is enabled/disabled based on inputField.text, while it should be inputField.displayText instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1595910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595910] Re: review input field: send button issues with predictive OSK
You need to be using inputMethodComposing: TextArea.displayText has different semantics - it's the text with no formatting, but not aware of the input method. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1595910 Title: review input field: send button issues with predictive OSK Status in ubuntu-ui-toolkit package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: Steps to reproduce: * Make sure predictive OSK is enabled * got an app in the store and start writing a review * Just write one word, no space after it (so that it is underlined for text correction things) => actual: The send button is disabled even though the text field holds a word => expected: The send button should be enabled Most likely the Send button is enabled/disabled based on inputField.text, while it should be inputField.displayText instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1595910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578319] Re: QMLStringAppTestCase rejected by Unity8
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1578319 Title: QMLStringAppTestCase rejected by Unity8 Status in ubuntu-app-launch package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: I'm trying to run the ubuntu-ui-toolkit autopilot tests on today's image. First off, they could cause unity8 to crash, which is bug 1578258 which can be resolved with https://code.launchpad.net/~gerboland/qtmir/ual-catch-exception/+merge/293805 That causes unity8 to report it rejects some of the test apps the UITK AP test tries to launch: qtmir.applications: ApplicationController::createApp - UAL failed to create app for appId "ubuntu-ui-toolkit-gallery" : Invalid app ID: ubuntu-ui-toolkit-gallery UITK AP is launching like this: /usr/bin/ubuntu-ui-toolkit-launcher -testability -I /usr/lib/modules /usr/lib/arm-linux-gnueabihf/qt5/examples//ubuntu-ui-toolkit/examples /ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml --desktop_file_hint=/usr/lib/arm-linux-gnueabihf/qt5/examples/ubuntu- ui-toolkit/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit- gallery.desktop which is not using upstart-app-launch - which would explain the fail. desktop_file_hint is not a supported means of launching an app (and can go away at any time), so UITK should change to use UAL in its AP tests. This indeed used to work until recently, but a recent refactoring broke the desktop_file_hint behaviour. Since it's not a supported behaviour, it should not be relied on, so it would be better to fix UITK than restore the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1578319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578319] Re: QMLStringAppTestCase rejected by Unity8
I renamed the title. desktop_file_hint is not the problem, the location of the .desktop files is. The hint is in fact still needed. ** Summary changed: - UITK AP tests that use QMLStringAppTestCase fail - rejected by unity8 as is using desktop_file_hint + QMLStringAppTestCase rejected by Unity8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1578319 Title: QMLStringAppTestCase rejected by Unity8 Status in ubuntu-app-launch package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: I'm trying to run the ubuntu-ui-toolkit autopilot tests on today's image. First off, they could cause unity8 to crash, which is bug 1578258 which can be resolved with https://code.launchpad.net/~gerboland/qtmir/ual-catch-exception/+merge/293805 That causes unity8 to report it rejects some of the test apps the UITK AP test tries to launch: qtmir.applications: ApplicationController::createApp - UAL failed to create app for appId "ubuntu-ui-toolkit-gallery" : Invalid app ID: ubuntu-ui-toolkit-gallery UITK AP is launching like this: /usr/bin/ubuntu-ui-toolkit-launcher -testability -I /usr/lib/modules /usr/lib/arm-linux-gnueabihf/qt5/examples//ubuntu-ui-toolkit/examples /ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml --desktop_file_hint=/usr/lib/arm-linux-gnueabihf/qt5/examples/ubuntu- ui-toolkit/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit- gallery.desktop which is not using upstart-app-launch - which would explain the fail. desktop_file_hint is not a supported means of launching an app (and can go away at any time), so UITK should change to use UAL in its AP tests. This indeed used to work until recently, but a recent refactoring broke the desktop_file_hint behaviour. Since it's not a supported behaviour, it should not be relied on, so it would be better to fix UITK than restore the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1578319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578319] Re: UITK AP tests that use QMLStringAppTestCase fail - rejected by unity8 as is using desktop_file_hint
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1578319 Title: UITK AP tests that use QMLStringAppTestCase fail - rejected by unity8 as is using desktop_file_hint Status in ubuntu-app-launch package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: I'm trying to run the ubuntu-ui-toolkit autopilot tests on today's image. First off, they could cause unity8 to crash, which is bug 1578258 which can be resolved with https://code.launchpad.net/~gerboland/qtmir/ual-catch-exception/+merge/293805 That causes unity8 to report it rejects some of the test apps the UITK AP test tries to launch: qtmir.applications: ApplicationController::createApp - UAL failed to create app for appId "ubuntu-ui-toolkit-gallery" : Invalid app ID: ubuntu-ui-toolkit-gallery UITK AP is launching like this: /usr/bin/ubuntu-ui-toolkit-launcher -testability -I /usr/lib/modules /usr/lib/arm-linux-gnueabihf/qt5/examples//ubuntu-ui-toolkit/examples /ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml --desktop_file_hint=/usr/lib/arm-linux-gnueabihf/qt5/examples/ubuntu- ui-toolkit/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit- gallery.desktop which is not using upstart-app-launch - which would explain the fail. desktop_file_hint is not a supported means of launching an app (and can go away at any time), so UITK should change to use UAL in its AP tests. This indeed used to work until recently, but a recent refactoring broke the desktop_file_hint behaviour. Since it's not a supported behaviour, it should not be relied on, so it would be better to fix UITK than restore the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1578319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1611733] Re: Autopilot does not work on xenial / Qt 5.5/ Mir
** Summary changed: - Autopilot does not work on xenial / Qt 5.5 + Autopilot does not work on xenial / Qt 5.5/ Mir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu. https://bugs.launchpad.net/bugs/1611733 Title: Autopilot does not work on xenial / Qt 5.5/ Mir Status in autopilot-qt package in Ubuntu: New Bug description: There is a problem with Autopilot and Qt 5.5 and newer on the phone (works better on desktop, reportedly) that would need fixed if Autopilot is wanted to be continued to be used after the phone base switches from vivid to xenial. The introspection would probably need at least some amount of changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-qt/+bug/1611733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570478] Re: Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Christian Dywan (kalikiana) => Zsombor Egri (zsombi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1570478 Title: Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6 Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Update: Qt 5.6.1 and UITK 20160716: 13 failures which MUST be fixed: dpr2 dpr3 performance --- original report --- Considerably less than on amd64 (bug #1560004), but still some now seen with the new UITK 20160412 and the latest Qt builds: 1 failures which MUST be fixed: tst_performance tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/performance/performance [...] #7 0x77c32034 in UCTheme::PaletteConfig::restorePalette() (this=0xeb8160) at ./src/Ubuntu/UbuntuToolkit/uctheme.cpp:278 #8 0x77c2ebf3 in UCTheme::~UCTheme() (this=0xeb8160, __in_chrg=) at ./src/Ubuntu/UbuntuToolkit/uctheme_p.h:125 https://launchpadlibrarian.net/253810125/buildlog_ubuntu-xenial-armhf .ubuntu-ui- toolkit_1.3.1938+16.04.20160412build1~xenial1~qt560~1_BUILDING.txt.gz 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/1570478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578319] Re: Some ubuntu-ui-toolkit AP tests failing to launch - rejected by unity8 as is using desktop_file_hint
Is there still an issue here? We've since landed code so I'm pretty sure the tests can pass. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1578319 Title: Some ubuntu-ui-toolkit AP tests failing to launch - rejected by unity8 as is using desktop_file_hint Status in ubuntu-app-launch package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: I'm trying to run the ubuntu-ui-toolkit autopilot tests on today's image. First off, they could cause unity8 to crash, which is bug 1578258 which can be resolved with https://code.launchpad.net/~gerboland/qtmir/ual-catch-exception/+merge/293805 That causes unity8 to report it rejects some of the test apps the UITK AP test tries to launch: qtmir.applications: ApplicationController::createApp - UAL failed to create app for appId "ubuntu-ui-toolkit-gallery" : Invalid app ID: ubuntu-ui-toolkit-gallery UITK AP is launching like this: /usr/bin/ubuntu-ui-toolkit-launcher -testability -I /usr/lib/modules /usr/lib/arm-linux-gnueabihf/qt5/examples//ubuntu-ui-toolkit/examples /ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml --desktop_file_hint=/usr/lib/arm-linux-gnueabihf/qt5/examples/ubuntu- ui-toolkit/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit- gallery.desktop which is not using upstart-app-launch - which would explain the fail. desktop_file_hint is not a supported means of launching an app (and can go away at any time), so UITK should change to use UAL in its AP tests. This indeed used to work until recently, but a recent refactoring broke the desktop_file_hint behaviour. Since it's not a supported behaviour, it should not be relied on, so it would be better to fix UITK than restore the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1578319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1587429] Re: Introduce Ubuntu.Components.Labs namespace
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Zsombor Egri (zsombi) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1587429 Title: Introduce Ubuntu.Components.Labs namespace Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: As has been discussed before we want to introduce new components under the Ubuntu.Components.Labs namespace to be able to preview in- development code, make it easy to try out but without any sort of guarantee on stability - everything in there can and will change or disappear at any point in time. In practise candidates for Ubuntu.Components proper should be introduce under Labs and moved once they're ready. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1587429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584356] Re: Difficulty with text selection in BQ M10 Tablet
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1584356 Title: Difficulty with text selection in BQ M10 Tablet Status in Canonical System Image: Confirmed Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: First bug report on M10 so forgive if I am doing anything wrong. I am just having no luck on getting complex text selected - stuff like mathematical expressions or passwords where there is a mix of alphabetical symbols, numerals, and punctuation in plain text with no spaces. Among other reasons this is important to me is that I use massive long passwords and sometimes have to copy them from one place to another, and math/sql/similar expressions are a mess to handle too. What selects is portions of the text, but the selection will not expand to the whole thing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593841] Re: CrossFadeImage: support horizontalAlignment and verticalAlignment
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Loïc Molinari (loic.molinari) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1593841 Title: CrossFadeImage: support horizontalAlignment and verticalAlignment Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: CrossFadeImage supports fillMode, which is nice. But I'd also like to control horizontalAlignment and verticalAlignment on the inner Image items. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1593841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596947] Re: button borders are streched in landscape orientation
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Loïc Molinari (loic.molinari) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1596947 Title: button borders are streched in landscape orientation Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: current build number: 369 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Button border are thick and streched in landscape orientation. It is also visible on tablet in portrait mode where borders are a bit blurry. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1596947/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598491] Re: AdaptivePageLayout primaryPageSource: is slow to load
This isn't being slow - by default the primaryPageSource is being loaded
asynchronously, that is unless you set asynchronous: false, and so by
definition the component is going to be complete before it's loaded.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1598491
Title:
AdaptivePageLayout primaryPageSource: is slow to load
Status in ubuntu-ui-toolkit package in Ubuntu:
Invalid
Bug description:
If using APL and setting the primaryPageSource:
Qt.resolvedUrl("MyPage.qml) the APL is so slow to load that the
primaryPage value doesnt exist until way after the
component.oncompleted signal is emitted.
I came across this issue when using the contenthub. if i select a file
in Telegram for example and my app recieves the transfer it tries to
add a page to the APL: addPageToCurrentColumn(pageLayout.primaryPage,
Qt.resolvedUrl("MyPage2.qml"))
Error:
qml: No SourcePage specified. Page will not be added.
Note: setting primaryPage: MyPage{} works without issue and resolves.
Example:
import QtQuick 2.4
import Ubuntu.Components 1.3
MainView {
objectName: "mainView"
applicationName: "aplTest.Testers"
width: units.gu(100)
height: units.gu(100)
AdaptivePageLayout {
id: apl
anchors.fill: parent
primaryPageSource: Qt.resolvedUrl("UI_FileOne.qml") //<-- qml: No
sourcePage specified. Page will not be added.
//primaryPage: UI_FileOne{} //<-- This works
layouts: [
PageColumnsLayout {
when: true;
// Just a single column layout
PageColumn {
fillWidth: true
}
}
]
Component.onCompleted: {
apl.addPageToCurrentColumn(apl.primaryPage,
Qt.resolvedUrl("UI_FileTwo.qml"));
}
}//AdaptivePageLayout
}//Mainview
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1598491/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599203] Re: CrossFadeImage: modifying sourceSize causes black image
Can you provide an example QML snippet demonstrating the problem? ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1599203 Title: CrossFadeImage: modifying sourceSize causes black image Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: 1) Have a CrossFadeImage loaded 2) Set a new source 3) Set a new sourceSize for the new source You'll see the CrossFadeImage go black while it reloads the image for the new sourceSize. This rather breaks the point of CrossFadeImage. Each source may have its own unique sourceSize. They tend to go hand- in-hand. But modifying sourceSize currently affects both image1 and image2 internally. Maybe either (A) have a way to set source and sourceSize at the same time or (B) have sourceSize changes only affect the next-loaded source? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1599203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603452] Re: [SDK] Change leading action background to red and icon to white
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1603452
Title:
[SDK] Change leading action background to red and icon to white
Status in Ubuntu UI Toolkit:
New
Status in Ubuntu UX:
In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
We'd like to change the leading action background from light grey back
to red. And switch the icon from red to white. However, I have spoken
to Andrea and the problem is regarding when a leading action is
disabled. Outlined as follows:
the default action delegate is just an Item { Icon {} } so it has no
background, see: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-
ui-
toolkit/staging/view/2033/src/Ubuntu/Components/Themes/Ambiance/1.3/ListItemStyle.qml#L120
Moreover, the whole ListItemActions panel uses only one colour for the
background http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
toolkit/staging/view/2033/src/Ubuntu/Components/Themes/Ambiance/1.3/ListItemStyle.qml#L51
Therefore if there are several actions in the leading action slot, all
will be disabled. Can we change the API so that there is flexibility
when choosing one action to be disabled rather than all of them?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1603452/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1611326] Re: Disabled ListItem inside ListView takes focus but does not show focus ring
*** This bug is a duplicate of bug 1611327 ***
https://bugs.launchpad.net/bugs/1611327
** This bug has been marked a duplicate of bug 1611327
Disabled ListItem inside ListView takes focus but does not show focus ring
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1611326
Title:
Disabled ListItem inside ListView takes focus but does not show focus
ring
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
Items outside of a ListView are skipped when using keyboard navigation
to change the focus. However, a ListItem inside a ListView takes the
focus even when it is disabled, but it does not show the focus frame
when focused.
For example, execute this QML program:
import QtQuick 2.4
import Ubuntu.Components 1.3
Item {
width: units.gu(50)
height: units.gu(50)
ListView {
anchors.fill: parent
delegate: ListItem {
enabled: index != 2
Label {
anchors.centerIn: parent
text: parent.enabled ? "enabled" : "disabled"
}
}
model: 5
}
}
Press TAB to focus on the ListView. Then press the down-cursor-key
twice to move the focus down inside the ListView. The focus will be on
the disabled item, but not focus frame is visible This is confusing
for the user since the focus seems to disappear, and the Item where
the focus seems to be (although invisible) cannot be triggered because
it is disabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1611326/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610943] Re: UITK FTBFS on yakkety, GCC6 change
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1610943
Title:
UITK FTBFS on yakkety, GCC6 change
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
ucbottomedge.cpp: In member function ‘void
UCBottomEdgePrivate::detectDirection(qreal)’:
ucbottomedge.cpp:263:33: error: call of overloaded ‘abs(qreal&)’ is ambiguous
bool deltaPassed = abs(delta) >= qApp->styleHints()->startDragDistance();
^
In file included from /usr/include/c++/6/cstdlib:75:0,
from /usr/include/c++/6/bits/stl_algo.h:59,
from /usr/include/c++/6/algorithm:62,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:37,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:41,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:40,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:37,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
from ../../../include/UbuntuToolkit/UbuntuToolkitDepends:3:
/usr/include/stdlib.h:774:12: note: candidate: int abs(int)
extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
from /usr/include/c++/6/algorithm:62,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:37,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:41,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:40,
from
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:37,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
from ../../../include/UbuntuToolkit/UbuntuToolkitDepends:3:
/usr/include/c++/6/cstdlib:180:3: note: candidate: long long int
std::abs(long long int)
abs(long long __x) { return __builtin_llabs (__x); }
^~~
/usr/include/c++/6/cstdlib:172:3: note: candidate: long int std::abs(long int)
abs(long __i) { return __builtin_labs(__i); }
^~~
...etc
From https://gcc.gnu.org/gcc-6/porting_to.html:
"Code which assumes that abs, malloc etc. are macros may no longer compile"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1610943/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1560004] Re: tst_listitem.* failures in test_0_defaults with Qt 5.6 on amd64
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1560004 Title: tst_listitem.* failures in test_0_defaults with Qt 5.6 on amd64 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: Update 2016-07-20: Updated information from latest Qt 5.6.1 builds and 20160615 UITK. UITK fails some tests with Qt 5.6 on amd64, preventing a build (unless overridden): https://launchpadlibrarian.net/253811553/buildlog_ubuntu-xenial-amd64 .ubuntu-ui- toolkit_1.3.1938+16.04.20160412build1~xenial1~qt560~1_BUILDING.txt.gz FAIL! : components::ListItemAPI::test_0_defaults() Transparent by default Actual (): # Expected (): #00 Loc: [/home/cris/bau/uut.staging/tests/unit/visual/tst_listitem.12.qml(248)] amd64 on Qt 5.6.1 30 failures which MUST be fixed: dpr2 dpr3 performance subtheming tst_datepicker12.bug1567840.SEGFAULT.qml tst_datepicker13.bug1567840.SEGFAULT.qml tst_expandablescolumn.qml tst_listitem.qml tst_listitem13.qml tst_pagehead_sections_bug1511839.qml tst_scrollbar.qml tst_scrollbar_header.qml tst_sections.qml tst_ubuntulistview.qml 60 fatal warnings which MUST be fixed: tst_actionbar.qml tst_expandable.qml tst_pagestack_deprecated_toolbar.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/1560004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
