[Touch-packages] [Bug 1469471] Re: Checkbox shown in the ListView Multiselect mode does not obey selected property
** 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/1469471 Title: Checkbox shown in the ListView Multiselect mode does not obey selected property Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The ListItem in Ubuntu.Components 1.2 and higher supports multiselect mode which is controlled by the selectMode property. The selected property controls whether a listitem is selected or not. However it seems that the checkbox shown during multiselect mode doesn't seem to obey the selected property. Steps to reproduce the bug: 1. Run the sample code 2. Long press to active multiselect mode 3. Press on any checkbox visible while in multiselect mode 4. Now press on that listitem. Notice the following, - Clicking on the listitem toggles the selected property. But the checkbox does not seem to respect that. - The selectedIndices array correctly shows that the listitem is selected/unselected on pressing it, but the checkbox just ignores that. I have attached sample code which reproduces the bug in a simple manner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1469471/+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 1372061] Re: SMS notification: time format not translatable
Nick, you can get updates on function calls when local or any parameter used changes. See i18n.tr() and other functions also get updated when locale changes. You could have thing like i18n.trDate(date, format) which returns an object, which in turn can also have properties/functions so those can get updated whenever date, format or locale changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1372061 Title: SMS notification: time format not translatable Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu Translations: Triaged Status in telephony-service package in Ubuntu: Invalid Status in ubuntu-settings-components package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in ubuntu-settings-components package in Ubuntu RTM: Triaged Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: Triaged Bug description: See the attached screenshot. The time for the notification seems to be hardcoded to hh:mm - mm, d. This works well for the US, but it's not a format that is used in all other countries. In Spain, for example, the date would rather be d mm. The time format needs to be marked for translation. Not sure from which project the notifications come from, for some reason I seem to remember they were moved to u-s-s, but if it's the wrong project/package, please reassign. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1372061/+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 1369874] Re: [Unity Dependency] Cleanup workarounds made to accept any QObject as Action or ActionContext.
** Project changed: ubuntu-ui-toolkit = ubuntu-ui-toolkit (Ubuntu) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Won't Fix = In Progress ** 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/1369874 Title: [Unity Dependency] Cleanup workarounds made to accept any QObject as Action or ActionContext. Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: We must introduce workarounds in toolkit to accept any QObject as Action or ActionContext to avoid crashes on those apps who mix Unity Actions with Toolkit Actions on registration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1369874/+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 1463430] Re: Clock app crashes when renabling an alarm
It has been approved and waiting for landing into trunk. We prepared the MR against trunk in case we are asked to do a super critical landing, so it got obsolete from staging landing :/ Sorry for the pickup, it'll be included in the next toolkit landing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1463430 Title: Clock app crashes when renabling an alarm Status in the base for Ubuntu mobile products: In Progress Status in QT Ubuntu: Invalid Status in Clock application for Ubuntu devices: Confirmed Status in qtbase-opensource-src package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: It seems clock app crashes when reenabling an alarm that just went off. Steps to reproduce the bug: 1. Set an alarm to ring in +1 or +2 minutes 2. Let it ring. 3. Dismiss it 4. Switch back to clock app and then renable that alarm What happens (sometimes) Clock app crashes Out of 10-11 tries, I was able to reproduce the crash only once on my N4 running ubuntu-touch/rc-proposed/ubuntu-developer image #1. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 1 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu-developer last update: 2015-06-03 16:58:46 version version: 1 version ubuntu: 20150602 version device: 20150210 version custom: 20150508-685-1-11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1463430/+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 1463430] Re: Clock app crashes when renabling an alarm
** 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 qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1463430 Title: Clock app crashes when renabling an alarm Status in the base for Ubuntu mobile products: In Progress Status in QT Ubuntu: Invalid Status in Clock application for Ubuntu devices: Confirmed Status in qtbase-opensource-src package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: It seems clock app crashes when reenabling an alarm that just went off. Steps to reproduce the bug: 1. Set an alarm to ring in +1 or +2 minutes 2. Let it ring. 3. Dismiss it 4. Switch back to clock app and then renable that alarm What happens (sometimes) Clock app crashes Out of 10-11 tries, I was able to reproduce the crash only once on my N4 running ubuntu-touch/rc-proposed/ubuntu-developer image #1. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 1 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu-developer last update: 2015-06-03 16:58:46 version version: 1 version ubuntu: 20150602 version device: 20150210 version custom: 20150508-685-1-11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1463430/+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 1456501] Re: Messaging ask to select a SIM card while there only is one
After few reboots I managed to get messages sent, but since then I cannot make any calls, Phone app keeps telling me No network, however the SIM settings said it si registered successfully to Orange. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1456501 Title: Messaging ask to select a SIM card while there only is one Status in messaging-app package in Ubuntu: New Bug description: The phone was low on battery and switched off at some point, while playing music. Later, while charging, i powered on the phone and tried to send a textmessage. But i got a pop-up, saying: -- No SIM card selected You need to select a SIM card close -- I have only one SIM card installed and it was registered to the provider (t-mobile) And with only one SIM, there is no option to select a SIM. So i had to restart the phone in order to be able to send the textmessage. After the restart, the phone worked normaly again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1456501/+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 1465806] Re: Alarms not shown in indicator datetime after upgrade to ota4
I thunk this and the Clock crasher bug are two different bugs! The alarm not kicking is not the Clock or backend's problem, please break the duplication! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1465806 Title: Alarms not shown in indicator datetime after upgrade to ota4 Status in the base for Ubuntu mobile products: New Status in evolution-data-server package in Ubuntu: Confirmed Bug description: STEPS: 1. Flash image 22 from stable 2. Set a one time alarm and a recurring alarm 3. Update to 23 EXPECTED: Alarms should be up and running as expected ACTUAL: Alarms are not shown in the datetime indicator but show up as active in and available in the clock. Because the indicator is in control of the alarm trigger the alarm never goes off. TEMPORARY WORK AROUND: Disable and enable all your alarms and then they work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1465806/+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 1465582] Re: TrailingAction widths needs to be clamped
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Zsombor Egri (zsombi) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = High ** 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/1465582 Title: TrailingAction widths needs to be clamped Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: In Podbird we have listitems that are sometimes big (height wise) and it has been noticed that when the listitem is big, the trailing edge actions width are too big that it hides the entire listitem when swiping left. Attached are screenshots that illustrate the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1465582/+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 1372592] Re: [SDK] Popover thindivider visible between contents and pointer on phone
@Jouni, if you find a bug is no fixed, you either mark it as new or create a new bug, not simply erasing a Fix Released bug to someone. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Fix Released = 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/1372592 Title: [SDK] Popover thindivider visible between contents and pointer on phone Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: There should not be a thin line separating the pointer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1372592/+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 1428762] Re: [SDK] Add Menu to the SDK to support convergence
** No longer affects: ubuntu-ui-toolkit -- 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/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UX bugs: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1428762/+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 1344883] Re: PageHeadSections/Picker: selectedIndex changes incorrectly when inserting/removing model entries
Your sample code doesn't remove items from the model, but inserts. The behaviour you experience is due to both components using ListView (PathView or GridView behaves the same). When you alter the model, the currentIndex won't necessarily point to the same item was pointing anymore. Removing an element from the ListView will cause currentIndex to change as well. This bug is more related to ListView than to Picker itself. Try the same with a ListView, and I'm sure you'll experience the same. -- 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/1344883 Title: PageHeadSections/Picker: selectedIndex changes incorrectly when inserting/removing model entries Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: I've attached a minimal program to demonstrate the problem. The Model contains 20 items, and the selectedIndex is at 18. Clicking the button below will remove the item at index 10. Expected behaviour: Picker keeps number 18 selected. Actual behaviour: Picker jumps to number 9, the index before the one just deleted. Observe that when changing the button code to remove index 3 instead of 10, the picker works correctly, and remains at item 18. The behaviour only breaks on some index removals. inserts appear to behave correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1344883/+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 1462690] Re: Header missing in pages pushed for the first time when using a custom application theme
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Zsombor Egri (zsombi) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = High ** 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/1462690 Title: Header missing in pages pushed for the first time when using a custom application theme Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Ubuntu.Components 1.2 provides developers with the ability to create custom application themes derived from Ambiance and SuruDark as explained in the tutorial blog post [1]. However testing it, I noticed a bug where any page pushed for the first time since the application start is not pushed properly. Steps to reproduce: 1. Branch sample application project bzr branch lp:~nik90/+junk/themebug 2. Run app 3. Press Tap me button to push a page What happens The mainPage contents are still shown despite pushing a page into the pagestack. The Page header is also missing title, buttons etc. What should happen The child page is pushed and its contents are shown. What I also noticed is that pressing the Tap me button again pushes the page correctly. However now the user needs to pop the page twice to go back to the main page. This was tested on a Nexus 4 running the image channel ubuntu-touch /rc-proposed/ubuntu #1 (likely to become OTA-4) [1] https://developer.ubuntu.com/en/blog/2015/03/17/creating-theme- your-application/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1462690/+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 1462738] [NEW] ListItem crashes when leading/trailing actions are swiped in
Public bug reported: Run UI Toolkit tGallery on staging, navigate to New ListItems, swipe in Leading or Trailing actions labeled ListItem. Shoot over or release while the actions are not fully revealed. At the end of the animation there will be a segfault on property binding restoration. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Critical Assignee: Zsombor Egri (zsombi) 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/1462738 Title: ListItem crashes when leading/trailing actions are swiped in Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Run UI Toolkit tGallery on staging, navigate to New ListItems, swipe in Leading or Trailing actions labeled ListItem. Shoot over or release while the actions are not fully revealed. At the end of the animation there will be a segfault on property binding restoration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1462738/+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 1461044] Re: Importing Ubuntu components brings warning
*** This bug is a duplicate of bug 1457528 *** https://bugs.launchpad.net/bugs/1457528 ** This bug has been marked a duplicate of bug 1457528 Theme.createStyleComponent deprecation useless warnings are displayed -- 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/1461044 Title: Importing Ubuntu components brings warning Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Default project template brings some warnings due to the Ubuntu components import. This doesn't make the new developers feeling in easy territory. import Ubuntu.Components 1.1 (or 1.2) brings numerous: Errors while reading typeinfo files: Failed to parse path/plugins.qmltype. Error: … Those errors are mostly missing or misparsed Package/Name major.minor. This as well prevent the Design mode to show some wireframing-type display. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1461044/+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 1461042] Re: Qthelp documentation (pressing in F1) has no style in qtcreator
** Also affects: qtcreator-plugin-ubuntu (Ubuntu) Importance: Undecided Status: New ** 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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1461042 Title: Qthelp documentation (pressing in F1) has no style in qtcreator Status in qtcreator-plugin-ubuntu package in Ubuntu: New Bug description: Some annotation tags are missing to bring back the style in qtcreator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1461042/+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 1457528] Re: Theme.createStyleComponent deprecation useless warnings are displayed
** 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/1457528
Title:
Theme.createStyleComponent deprecation useless warnings are displayed
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
Take that example
import QtQuick 2.0
import Ubuntu.Components 0.1
Item {
Button {
text: click
}
}
run it on wily, you get those warnings
QML Button: Theme.createStyleComponent() is deprecated. Use
ThemeSettings instead.
the warning is not helpful, it warns about a standard component issue
(so something in the responsability of the uitk team, not the code
writer), lists the issue on something you are not using (what is
Theme.createStyleComponent() that's not used in the code example?),
it's just confusing...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1457528/+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 1460897] Re: Captions API sample code is not working on vivid
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided = Medium
** 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/1460897
Title:
Captions API sample code is not working on vivid
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
The original sample code at:
https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Captions/
is not working.
The correct one:
import QtQuick 2.4
import Ubuntu.Components 1.2
import QtQuick.Layouts 1.1 // THIS SHOULD BE ADDED
/*!
\brief MainView with a Label and Button elements.
*/
MainView {
// objectName for functional testing purposes (autopilot-qt5)
objectName: mainView
// Note! applicationName needs to match the name field of the click
manifest
applicationName: captions.liu-xiao-guo
/*
This property enables the application to change orientation
when the device is rotated. The default is false.
*/
//automaticOrientation: true
// Removes the old toolbar and enables new features of the new header.
//useDeprecatedToolbar: false
width: units.gu(60)
height: units.gu(85)
Page {
title: i18n.tr(captions)
ListItem {
RowLayout {
anchors.fill: parent// THIS SHOULD BE ADDED
Captions {
title.text: Caption
subtitle.text: Subtitle text
// attached properties of an Item type property
// can be changed only with assignment
Component.onCompleted: subtitle.Layout.alignment =
Qt.AlignRight
}
Captions {
captionStyle: Ubuntu.SummaryCaptionStyle
title.text: Text
subtitle.text: Text
}
}
}
}
}
The module:
import QtQuick.Layouts 1.1 // THIS SHOULD BE ADDED
and also
anchors.fill: parent// THIS SHOULD BE ADDED
Otherwise, nothing will be displayed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1460897/+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 1461061] Re: Normalizing import version across ubuntu components
This was a valid problem in the UI Toolkit in the previous versions - we had the main component set 1.2, the ListItems 1.1, etc. From 15.10 onwards all its sub-modules, including themes will be aligned to 1.3 version, and the plan is that with the next LTS (16.04) we will open 2.0, which will not necessarily mean every LTS will bring major release update. However. Bumping version with every release in modules which do not bring new APIs are a bit of an overkill. For instance if Content Hub brings a new API let's say in 1.4, and UI Toolkit doesn't bring anything for 1.4, that would mean that we would need to duplicate theme files for 1.4 just because we need to rise the version of the toolkit, which is a bit of an unnecessary work - remember, themes are loaded runtime and not resolved through the QML type system, so qmldir tricks do not apply there. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- 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/1461061 Title: Normalizing import version across ubuntu components Status in content-hub package in Ubuntu: New Status in location-service package in Ubuntu: New Status in media-hub package in Ubuntu: New Status in u1db package in Ubuntu: New Status in ubuntu-download-manager package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: Some components are still 1.0, other 1.3. It can be hard for the developer to understand exactly which version to import, what version is compatible or part of the same framework that the other one. The goal is to get a common agreements with all components we ship as part of the ubuntu sdk coming from canonical (from media-hub, content- hub to ubuntu components) to use the same API version for making easier developer's life experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1461061/+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 1460897] Re: Captions API sample code is not working on vivid
The example codes in documentation are not always applications. The
example from ListItem is a such one, you have to use it in a ListView.
The missing import is valid though.
** 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/1460897
Title:
Captions API sample code is not working on vivid
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
The original sample code at:
https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Captions/
is not working.
The correct one:
import QtQuick 2.4
import Ubuntu.Components 1.2
import QtQuick.Layouts 1.1 // THIS SHOULD BE ADDED
/*!
\brief MainView with a Label and Button elements.
*/
MainView {
// objectName for functional testing purposes (autopilot-qt5)
objectName: mainView
// Note! applicationName needs to match the name field of the click
manifest
applicationName: captions.liu-xiao-guo
/*
This property enables the application to change orientation
when the device is rotated. The default is false.
*/
//automaticOrientation: true
// Removes the old toolbar and enables new features of the new header.
//useDeprecatedToolbar: false
width: units.gu(60)
height: units.gu(85)
Page {
title: i18n.tr(captions)
ListItem {
RowLayout {
anchors.fill: parent// THIS SHOULD BE ADDED
Captions {
title.text: Caption
subtitle.text: Subtitle text
// attached properties of an Item type property
// can be changed only with assignment
Component.onCompleted: subtitle.Layout.alignment =
Qt.AlignRight
}
Captions {
captionStyle: Ubuntu.SummaryCaptionStyle
title.text: Text
subtitle.text: Text
}
}
}
}
}
The module:
import QtQuick.Layouts 1.1 // THIS SHOULD BE ADDED
and also
anchors.fill: parent// THIS SHOULD BE ADDED
Otherwise, nothing will be displayed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1460897/+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 1457361] Re: Clipboard clear method crashes and Pushing data straight to clipboard is not working
** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed ** 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/1457361 Title: Clipboard clear method crashes and Pushing data straight to clipboard is not working Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: - I tried to call the Clipboard.clear() method, and it crashes my application for 100% sure. - I tried the 2. Pushing data straight to clipboard method on page: https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Clipboard/ it does not work at all. The method 1/3 work fine. I have my test code: https://gitcafe.com/ubuntu/clipboard/tree/master You can check it out by running: git clone https://gitcafe.com/ubuntu/clipboard.git The test phone image is: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 195 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-05-12 14:52:33 version version: 195 version ubuntu: 20150512 version device: 20150210 version custom: 20150508 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1457361/+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 1427714] Re: Clock app requires timers support from the platform
As we do not have any backend support/schedule for it, I cannot express any estimates. Perhaps this will fall into 16.04 timeframe, depends on how much time we have and whether we get support from platform. By platform I mean the new backend which omits the QtOrganizer/EDS middlemen. With QtOrganizer this would be a bit hard to implement so the timers are not mixed with alarms. -- 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/1427714 Title: Clock app requires timers support from the platform Status in indicator-datetime package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Similar to alarms, the clock app requires the platform to wake up and notify the user when a timer is complete. The clock app cannot do this by itself since it would be suspended as per the app life cycle policies. Clock App Timer design is tracked at bug 1427566. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1427714/+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 1458694] Re: [vivid-overlay] unity8 fails to start on the emulator
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New = Triaged
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: High = Critical
** 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/1458694
Title:
[vivid-overlay] unity8 fails to start on the emulator
Status in mir package in Ubuntu:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 140
device name: generic_x86
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2015-05-25 12:02:10
version version: 140
version ubuntu: 20150525
version device: 20150210
version custom: 20150525
When starting unity8 (this started at image 136, probably when mir
0.13 landed):
phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
()
[1432595001.896139] mirplatform: Found graphics driver: dummy
[1432595001.898447] mirplatform: Found graphics driver: android
qtmir.mir: MirServer created
[1432595003.675225] Server: Starting
[1432595003.679331] Loader: Loading modules from:
/usr/lib/i386-linux-gnu/mir/server-platform
[1432595003.679501] Loader: Loading module:
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
[1432595003.680673] Loader: Loading module:
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
[1432595003.681107] WARNING Loader: Failed to load module:
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
[1432595003.684868] Loader: Loading module:
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
[1432595003.685014] mirplatform: Found graphics driver: dummy
[1432595003.685211] mirplatform: Found graphics driver: android
[1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
qtmir.mir: PromptSessionListener::PromptSessionListener - this=
PromptSessionListener(0x9679764)
qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
qtmir.mir: MirShell::MirShell
[1432595003.883766] DisplayServer: Mir version 0.13.0
QtCompositor::setAllWindowsExposed true
qtmir.clipboard: D-Bus registration successful.
Mode argument was not provided or was set to an illegal value. Using default
value of --mode= full-greeter
Cannot create window: no screens available
With version 135 it starts fine, but not fully functional, giving this
error:
QOpenGLShader::compile(Fragment): 0:2(12): warning: extension
`GL_OES_standard_derivatives' unsupported in fragment shader
0:2(1): error: #extension directive is not allowed in the middle of a shader
*** Problematic Fragment shader source code ***
#extension GL_OES_standard_derivatives : enable // Enable dFdy() on OpenGL
ES 2.
#define lowp
#define mediump
#define highp
// Copyright © 2015 Canonical Ltd.
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU Lesser General Public License as published by
// the Free Software Foundation; version 3.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU Lesser General Public License for more details.
//
// You should have received a copy of the GNU Lesser General Public License
// along with this program. If not, see http://www.gnu.org/licenses/.
//
// Author: Loïc Molinari loic.molin...@canonical.com
// Static flow control (branching on a uniform value) is fast on most GPUs
(including ultra-low
// power ones) because it allows to use the same shader execution path for an
entire draw call. We
// rely on that technique here (also known as uber-shader solution) to
avoid the complexity of
// dealing with a multiple shaders solution.
// FIXME(loicm) Validate GPU behavior with regards to static flow control.
uniform sampler2D shapeTexture;
uniform sampler2D sourceTexture;
uniform lowp vec2 dfdtFactors;
uniform lowp vec2 opacityFactors;
uniform lowp float sourceOpacity;
uniform lowp float distanceAA;
uniform bool textured;
uniform mediump int aspect;
varying mediump vec2 shapeCoord;
varying mediump vec4 sourceCoord;
varying lowp vec4 backgroundColor;
const mediump int FLAT = 0x08; // 1 3
const mediump int INSET = 0x10; // 1 4
void main(void)
{
lowp vec4 shapeData = texture2D(shapeTexture, shapeCoord);
lowp vec4 color = backgroundColor;
// FIXME(loicm) Would be better to use a bitfield but bitwise ops have
only been integrated in
//
[Touch-packages] [Bug 1457528] Re: Theme.createStyleComponent deprecation useless warnings are displayed
** 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/1457528
Title:
Theme.createStyleComponent deprecation useless warnings are displayed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
Take that example
import QtQuick 2.0
import Ubuntu.Components 0.1
Item {
Button {
text: click
}
}
run it on wily, you get those warnings
QML Button: Theme.createStyleComponent() is deprecated. Use
ThemeSettings instead.
the warning is not helpful, it warns about a standard component issue
(so something in the responsability of the uitk team, not the code
writer), lists the issue on something you are not using (what is
Theme.createStyleComponent() that's not used in the code example?),
it's just confusing...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1457528/+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 1457528] Re: Theme.createStyleComponent deprecation useless warnings are displayed
I've checked the test with staging, and I get warnings for 0.1, 1.0, 1.1
and 1.2 imports. So seems staging has some fix which makes the warning
to be printed everywhere but 1.3.
About the logs, staging (and I think overlay PPA will get it soon) has
more info on where the problem relies. I am getting the following log:
test.qml:5:5: QML Button: Theme.createStyleComponent() is deprecated.
Use ThemeSettings instead.
Theme is a context property. Context properties and Singletons are
impossible to know from which QML file are invoked. So we cannot really
display any meaningful information on where the component is used. We
cannot know whether the functionality is called from a toolkit component
or from an application or custom component based on toolkit. As seen
above, the staging which is also planned to be released, has more
information on Theme.createStyleComponent(), but that is the only one
can give valuable information. Theme.palette or Theme.name will not know
the caller context, and will not be able to specify from what document
it is addressed.
** 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/1457528
Title:
Theme.createStyleComponent deprecation useless warnings are displayed
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
Take that example
import QtQuick 2.0
import Ubuntu.Components 0.1
Item {
Button {
text: click
}
}
run it on wily, you get those warnings
QML Button: Theme.createStyleComponent() is deprecated. Use
ThemeSettings instead.
the warning is not helpful, it warns about a standard component issue
(so something in the responsability of the uitk team, not the code
writer), lists the issue on something you are not using (what is
Theme.createStyleComponent() that's not used in the code example?),
it's just confusing...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1457528/+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 1457528] Re: Theme.createStyleComponent deprecation useless warnings are displayed
If the warning disappears with 1.1 import then we're in trouble. It
should be displayed with 1.1 as well. It should be displayed till Theme
is used instead of theme. So if 1.3 import uses Theme, it will show a
warning.
--
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/1457528
Title:
Theme.createStyleComponent deprecation useless warnings are displayed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
Take that example
import QtQuick 2.0
import Ubuntu.Components 0.1
Item {
Button {
text: click
}
}
run it on wily, you get those warnings
QML Button: Theme.createStyleComponent() is deprecated. Use
ThemeSettings instead.
the warning is not helpful, it warns about a standard component issue
(so something in the responsability of the uitk team, not the code
writer), lists the issue on something you are not using (what is
Theme.createStyleComponent() that's not used in the code example?),
it's just confusing...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1457528/+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 1314672] Re: Caption listitems left margin is different from normal items
The Caption aligns the text horizontally centered by design. The component has never been revisited by design and with the new ListItem it became deprecated in v1.2. Please use the new ListItem with a Label or if no divider is needed, a simple Item can do the job as well. Also beware that the new ListItem has no layout on purpose, and it was a design decision not to have any layout for it. ** No longer affects: ubuntu-ui-toolkit ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = Won't Fix -- 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/1314672 Title: Caption listitems left margin is different from normal items Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: Ubuntu 14.04 r2 In the Brightness System Settings panel, the caption Brightens and dims the display to suit the surroundings starts nearly at the left edge of the screen. The left edge of a caption should be lined up exactly with the left edge of a label. This might be a toolkit problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1314672/+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 1279789] Re: ListItem inside Dialog is black-on-grey
Since then design got changed, and SuruDark theme Dialog is also having white background to circumvent contrast issues on labels. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = Won't Fix -- 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/1279789 Title: ListItem inside Dialog is black-on-grey Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: If you include a ListItem (in this screenshot, a ListItem.SingleValue) inside a Dialog, the text is black on a grey background - this is almost unreadable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1279789/+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 1256024] Re: ListItem icon: Rectangle {} stopped working since it got deprecated
System settings imports 0.1, 1.0 and 1.1 toolkit, and this is not good.
We asked developers to switch to import the latest UI toolkit in their
apps to get the fixes rolling on, especially that 0.1 version was a
development version. QML versioning also played us out badly, and we
had to split the sources for the different versions, which mean that
some components will not work with different toolkit versions. We do not
have maintenance capabilities to support previous versions or deprecated
components, especially the ListItems module. It has been decided that
the toolkit will not provide any standard layouts for list items as
design changes may bring us to more deprecation.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed = Won't Fix
--
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/1256024
Title:
ListItem icon: Rectangle {} stopped working since it got deprecated
Status in ubuntu-ui-toolkit package in Ubuntu:
Won't Fix
Bug description:
The system settings code is using a custom component (basically a Rectangle
with a Label) as an icon,
http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/view/head:/plugins/language/KeyboardLayouts.qml#L48
That code stopped working in trusty with the recent changes
(http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
toolkit/trunk/revision/858), the icon is not displayed in the UI
Those warning are displayed on the command line:
file:///usr/lib/i386-linux-gnu/qt5/qml/Ubuntu/Components/ListItems/Standard.qml:252:
Error: Cannot assign QObject* to QUrl
WARNING: ListItems.Standard.icon is DEPRECATED. Use iconName and iconSource
instead.
We are looking at porting our code (bug #1256017), I'm still opening
that, as a toolkit bug, since ideally users of the old property should
keep working during the transition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1256024/+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 1355830] Re: ListItems height breaks when put in a Loader
Please do not use ListItems module, and migrate your app to use UITK 1.2 and the new ListItem. ListItems module is deprecated and we won't provide bugfixes to the module. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = Won't Fix -- 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/1355830 Title: ListItems height breaks when put in a Loader Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: See the attached .qml file. As soon as you put a ListItem in a Loader, its expansion breaks miserably. This prevents dynamic creation of UIs based on expandable items. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1181+14.10.20140806-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 12 15:37:08 2014 SourcePackage: ubuntu-ui-toolkit SystemImageInfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1355830/+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 1216352] Re: onAccepted not triggered if TextField in ListItem
Please try this with the new ListItem (UITK v1.2) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Triaged = Won't Fix -- 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/1216352 Title: onAccepted not triggered if TextField in ListItem Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: If a TextField is placed within a List Item (Standard, for example), the Accepted signal does not trigger. onAccepted works fine if textField is not in a List element. Workaround for now is to use Keys.onReturnPressed and implement your own field validation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1216352/+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 1313134] Re: listitem: itemRemoved should be triggered before the listItem hiding animation.
If your application i sin Vivid, please upgrade to use the new ListItem. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = Won't Fix -- 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/1313134 Title: listitem: itemRemoved should be triggered before the listItem hiding animation. Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: Currently after swiping on the listItem.Empty, the listItem first hides and after the hiding animation completes, itemRemoved is called. However, preferrably, itemRemoved should be triggered before the hiding animation. Also, in itemRemoved, a way to cancel removal(hiding animation) should be provided. @Jan Kundrát who suggested reporting this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1313134/+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 1348604] Re: Provide a property to change the font color of listitems
The new ListItem provides more flexibility, please use that.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed = Fix Released
--
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/1348604
Title:
Provide a property to change the font color of listitems
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Bug description:
The clock app and many other system application that received designs
at Malta require the listitem font color to be midAubergine. The
default color is however black. Please provide a property to change
the font color so that this can be done easily.
Currently the way we do it in the clock app is to use ListItem.Base
and define Labels{} where we explicitly set the font color. This can
all be avoided by a simple expose of the fontcolor property.
Example Design Spec:
https://docs.google.com/presentation/d/1Kkl7xT8BYo9mT8i3IXh6rPrDlNg6cBxTajahlRYIGlI/edit#slide=id.p
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1348604/+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 1358241] Re: Listitems should allow color properties for themeability
The new ListItem (Ubuntu.Components 1.2) allows you to do that. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = Fix Released -- 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/1358241 Title: Listitems should allow color properties for themeability Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: It is not currently possible to theme ListItems bg and fg colors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1358241/+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 1421653] Re: Changing ItemSelector model sets currentIndex to 0
Modxel change resets the index, like any model change in a mode-based component (see PathView, ListView, etc). No way to stay in the original index as what if that is out of the model count? ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Won't Fix -- 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/1421653 Title: Changing ItemSelector model sets currentIndex to 0 Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: Repro: 1. Have expanded ItemSelector 2. Set currentIndex to something other than 0 by tapping the second or third item in an ItemSelector What happens: currentIndex is sat to 0, i.e. the selected item is changed What should have happened: currentIndex should have remained Example: http://pastebin.ubuntu.com/10205382/ Might be invalid/unfixable, and that's ok, but it might deserve a note in the docs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421653/+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 1432634] Re: [Calendar] date picker design is out of date
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium ** 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/1432634 Title: [Calendar] date picker design is out of date Status in Calendar application for Ubuntu devices: Fix Committed Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The design for the date picker is out of date. See the Clock app for the new design To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1432634/+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 1374028] Re: [address-book] contact detail view content too close to SURU divider
** Changed in: ubuntu-ui-toolkit Assignee: (unassigned) = Tim Peeters (tpeeters) ** No longer affects: ubuntu-ui-toolkit ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Tim Peeters (tpeeters) ** 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 address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1374028 Title: [address-book] contact detail view content too close to SURU divider Status in Address Book App: New Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Address Book app 2. Tap on a list item (contact) 3. Tap again on the person icon which appears to the right 4. Actual result: contact detail view opens and it seems that the content is shifted up, thumbnail is too close to SURU divider. Scroll down, and content shifts into correct position. The thumbnail has now a different spacing from the SURU divider. 5. Expected result: The contacts detail view page shouldn't scroll if the content fits into view. When opening the detail page, the correct spacing is after the scroll down. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1374028/+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 1276118] Re: List Item onItemRemoved signal should provide the option to override its action with a custom one.
Please switch to the new ListItem.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed = Won't Fix
--
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/1276118
Title:
List Item onItemRemoved signal should provide the option to override
its action with a custom one.
Status in ubuntu-ui-toolkit package in Ubuntu:
Won't Fix
Bug description:
The title is a bit ambigious, let me try to explain in more detail
here. I have been using U1db documents in a listview to retrieve and
display stored listitems. U1db allows you to delete documents by
putDoc(value, docId). So I connected this with the listitem's swipe to
delete method.
delegate: ListItem.Standard {
removable: true
onItemRemoved: {
db.putDoc(, docId)
}
}
The problem here is that when the user swipes delete a delegate, the
listview deletes the delegate which in turn also deletes the u1db
document. This changes the u1db model which is noticed by the listview
and tried to delegate again which is no longer available resulting in
an error.
QQmlVMEMetaObject: Internal error - attempted to evaluate a function in an
invalid context
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/ListItems/Empty.qml:459:9:
QML ScriptAction: Unknown File:
The solution here would be to provide a way to override the default
action of the onItemRemoved signal. This way the deleting action is
only performed once.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1276118/+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 1329129] Re: ListItem text color is black and very harsh
We hav edeprecated this module in 1.2 and we are no longer provide fixes on the deprecated components. Please switch to use the new ListItem, and the Captions to lay out labels in the ListItem. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Triaged = Won't Fix -- 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/1329129 Title: ListItem text color is black and very harsh Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: The text color of ListItems is black, whether used in a SuruGradient app or the default Ambiance theme. This is a very harsh color compared to the dark gray used by default in the Label component in the Ambiance theme. It would be nice if the ListItem components used a dark gray color, probably the same as the default Label color, to provide a nicer appearance and not be so harsh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1329129/+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 1450213] Re: [SDK] cursor handle should not be visible if field is empty
** Summary changed:
- {SDK] cursor handle should not be visible if field is empty
+ [SDK] cursor handle should not be visible if field is empty
--
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/1450213
Title:
[SDK] cursor handle should not be visible if field is empty
Status in the base for Ubuntu mobile products:
New
Status in Ubuntu UX bugs:
Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
On arale
ui-tookit version 1.2.1485+15.04.20150429-0ubuntu1
The big blue cursor handle should not be visible if the text field is
empty, as dragging does nothing. It should only be displayed if the
field has text (or spaces) in it where dragging would make sense.
Steps to reproduce:
1) reboot phone
2) launch messaging-app
3) swipe up from bottom to create new messaage
Expected results:
- cursor should be blinking in field
- no text handle should be visible
Actual results:
- cursor is blinking in field
- big blue cursor handle is visible
NOTE, you can repeat this same thing by pressing the Search icon in
the dash. The blue cursor appears even when nothing in paste buffer.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450213/+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 1450222] Re: [SDK] cursor handle is cut off by keyboard and not functional
The only way to solve this is to put the handler above the input field when OSK covers it. You cannot put the handler above the OSK, and OSK will always cover it. However the handlers are ugly anyway, wether is above or below the text input :) -- 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/1450222 Title: [SDK] cursor handle is cut off by keyboard and not functional Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: latest arale build ui-toolkit version 1.2.1485+15.04.20150429-0ubuntu1 If there is a text field at the bottom of a page, directly above the keyboard you cannot drag the cursor handle to re-position because it's cut off by the keyboard window. Sometimes you can can drag it but it's very difficult as it's truncated. The fix should be to place the cursor handles above the text field, not below, if there is not space to draw the handle below. Steps to reproduce: 1) reboot 2) open messaging-app 3) drag up to create a new message 4) start typing in the send field at bottom 5) try to drag the handles to reposition the caret Expected results: handle easy to drag Actual results: handle very difficult to drag as it's cut off by To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450222/+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 1289329] Re: Pushed list item remains highlighted even when releasing will do nothing
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Fix Committed = Fix Released -- 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/1289329 Title: Pushed list item remains highlighted even when releasing will do nothing Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: Ubuntu Trusty r188 1. Go to System Settings Language Text. 2. Quickly tap the Spell checking list item. 3. Slowly push down on the Spell checking list item, then release after a few seconds. What happens: 2. The item highlights and then returns to its previous appearance, and the switch toggles. 3. The item highlights and then returns to its previous appearance, but the switch does not toggle. What should happen: either 3a. the item loses its highlight after the maximum tap duration, or 3b. there is no maximum tap duration, and the switch still toggles when you release (bug 1365471). It is misleading to highlight a control as if it will change state, and then not do it. (Not to be confused with bug 1362305, about items that don't do anything regardless of how long you tap them.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1289329/+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 1197058] Re: [SDK ListItems] should allow controls on the left
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Fix Committed = Fix Released
--
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/1197058
Title:
[SDK ListItems] should allow controls on the left
Status in Ubuntu UX bugs:
Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Bug description:
Looking to this system settings design:
https://wiki.ubuntu.com/Sound?action=AttachFiledo=gettarget=phone-settings-sound.png
The list have list entries with that format
| [check]Label |
I've used a custom item for those doing that:
'ListItem.Base {
property string textEntry: ;
property bool checkStatus: false;
Row {
anchors.top: parent.top
anchors.bottom: parent.bottom
spacing: units.gu(2)
CheckBox {
anchors.verticalCenter: parent.verticalCenter
checked: checkStatus
}
Label {
anchors.verticalCenter: parent.verticalCenter
text: textEntry
}
}
}
But:
- that's not standard
- clicking on the label doesn't tweak the checkbox as it does for other
controls (I can hack that easily if needed though)
- the UI might not be consistent with what is used in other place
This bug might also be a place to discuss if those items are fine to
use or non coherent with our use of the toolkit in other places...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1197058/+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 1452676] Re: [SDK] Right-click menu instead of leading/ trailing actions
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Zsombor Egri (zsombi) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Triaged ** Tags added: convergence -- 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/1452676 Title: [SDK] Right-click menu instead of leading/ trailing actions Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: On desktops/ laptops the leading and trailing actions of list items should be available as context menus. In practise we probably want to enable the menu if a mouse is being used and only enable the actions if s touchscreen is available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1452676/+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 1451225] Re: Cannot set background colour for overflow of leading/trailing actions
The bug here is the colouring of the panel colors using Palette value rather than setting the bg colour of the panel. Unfortunately we did not receive any colouring guides from UX for dark themes, only for Ambiance. -- 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/1451225 Title: Cannot set background colour for overflow of leading/trailing actions Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: In music we use dark colours for the listitem background and therefore the background of the actions. With the 'new' listitems you can set the colour of the action by putting it inside a Rectangle. However I have been unable to set the colour if you 'pull' too far, it appears as white in this case. I have created a mini app here [0], if you open the application and drag a listitem to the left you will notice that the action appears, with a background colour set, but then if the user pulls too far it turns to white. (I assume it is the same with the leading actions if you didn't want them to have a red background) Is there anyway we can set this colour? 0 - http://pastebin.ubuntu.com/10979455/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1451225/+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 1451225] Re: Cannot set background colour for overflow of leading/trailing actions
The solution is for you to provide your own theme, where you override the ListItemStyle and set the colour of the trailing panel accordingly. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Zsombor Egri (zsombi) ** 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/1451225 Title: Cannot set background colour for overflow of leading/trailing actions Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: In music we use dark colours for the listitem background and therefore the background of the actions. With the 'new' listitems you can set the colour of the action by putting it inside a Rectangle. However I have been unable to set the colour if you 'pull' too far, it appears as white in this case. I have created a mini app here [0], if you open the application and drag a listitem to the left you will notice that the action appears, with a background colour set, but then if the user pulls too far it turns to white. (I assume it is the same with the leading actions if you didn't want them to have a red background) Is there anyway we can set this colour? 0 - http://pastebin.ubuntu.com/10979455/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1451225/+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
We discussed yesterday with Jamie and Christian, and the best would be
to get this implemented in the usensord service. So the idea is that
service would expose a property the settings application can change.
Toolkit will not read any setting, but will call the Haptics as it did
before. On the other hand, sensors service must check who was the caller
of the vibration, to differentiate whether the call came from OSK or the
app itself. It will then decide to vibrate or not, based on the setting.
So changes would need to be done on
1. usensord - expose the property system settings app can change, identify the
caller and do or do not vibrate depending on the setting
2. system settings app should read/write this property
3. toolkit calls the haptics (vibrate) as it did before, without checking the
enabled flag
Now, how does this sound?
--
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
Status in the base for Ubuntu mobile products:
Confirmed
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:
Confirmed
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,
[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts
Ok, then I've added usensord as affected, no idea who can pick up the
task on that front...
** Also affects: usensord (Ubuntu)
Importance: Undecided
Status: New
** Changed in: usensord (Ubuntu)
Importance: Undecided = High
--
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
Status in the base for Ubuntu mobile products:
Confirmed
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:
Confirmed
Status in usensord package in Ubuntu:
New
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)
[Touch-packages] [Bug 1372061] Re: SMS notification: time format not translatable
** 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 telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1372061 Title: SMS notification: time format not translatable Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu Translations: Triaged Status in telephony-service package in Ubuntu: Invalid Status in ubuntu-settings-components package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in ubuntu-settings-components package in Ubuntu RTM: Triaged Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: Triaged Bug description: See the attached screenshot. The time for the notification seems to be hardcoded to hh:mm - mm, d. This works well for the US, but it's not a format that is used in all other countries. In Spain, for example, the date would rather be d mm. The time format needs to be marked for translation. Not sure from which project the notifications come from, for some reason I seem to remember they were moved to u-s-s, but if it's the wrong project/package, please reassign. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1372061/+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 1372061] Re: SMS notification: time format not translatable
The branch proposed for the toolkit does not cover the BP https://blueprints.launchpad.net/ubuntu-ui-toolkit/+spec/time-formatter. Beside that, I agree with Tim and Christian, that there is no need to provide a component dedicated to translate date and time only, especially that we have the internationalisation engine which can be extended with a function or two to support this. ** 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 telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1372061 Title: SMS notification: time format not translatable Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu Translations: Triaged Status in telephony-service package in Ubuntu: Invalid Status in ubuntu-settings-components package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in ubuntu-settings-components package in Ubuntu RTM: Triaged Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: Triaged Bug description: See the attached screenshot. The time for the notification seems to be hardcoded to hh:mm - mm, d. This works well for the US, but it's not a format that is used in all other countries. In Spain, for example, the date would rather be d mm. The time format needs to be marked for translation. Not sure from which project the notifications come from, for some reason I seem to remember they were moved to u-s-s, but if it's the wrong project/package, please reassign. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1372061/+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
Ok, guys, is anybody working on any service that toolkit can use?
--
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
Status in the base for Ubuntu mobile products:
Confirmed
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:
Confirmed
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 notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1433590/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts
Pat, seams we are not going to have this for wk21. See below.
[15:31:55] seb128 zsombi, hey, yes, we started working on that
[15:45:49] zsombi seb128: any estimate on the availability?
[15:45:58] seb128 zsombi, not yet, weeks at least
[15:46:22] zsombi seb128: ouh, so it may fall out of wk21 milestone
[15:46:45] seb128 zsombi, yeah for sure, I doubt that service is going to be
easy or available before june
--
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
Status in the base for Ubuntu mobile products:
Confirmed
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:
Confirmed
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
[Touch-packages] [Bug 1447113] Re: Preview UITK version 1.3 conflicts released version 1.2
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/separate-uitk-versions -- 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/1447113 Title: Preview UITK version 1.3 conflicts released version 1.2 Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: My app uses Ubuntu.Components 1.1 and one of my Page sub-classes has it's own 'theme' property. When I upgraded my device (mako) to the latest daily release it brought in the new header styles, which introduced a new 'theme' property on Page. Because this new property is marked at FINAL, and my sub-class was trying to redfine it, my app would crash on startup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1447113/+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 1447113] Re: Page.theme property introduced in 1.2 conflicts with app properties
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/fix-import-versions ** Summary changed: - Page.theme property introduced in 1.2 conflicts with app properties + Preview UITK version 1.3 conflicts released version 1.2 -- 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/1447113 Title: Preview UITK version 1.3 conflicts released version 1.2 Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: My app uses Ubuntu.Components 1.1 and one of my Page sub-classes has it's own 'theme' property. When I upgraded my device (mako) to the latest daily release it brought in the new header styles, which introduced a new 'theme' property on Page. Because this new property is marked at FINAL, and my sub-class was trying to redfine it, my app would crash on startup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1447113/+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 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Alex, I know, and I guess you can be a better person to update that, I am not in UI/UX team contrary to you :) -- 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/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+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 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Alex, I know that, but as I donut have a better link to it, and it belongs to design, I guess its not my fault ;) -- 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/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+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 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Alex, I know, and I guess you can be a better person to update that, I am not in UI/UX team contrary to you :) -- 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/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+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 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Damn launchpad said error or posting, and then I see it posted both of my comments :D -- 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/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+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 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Alex, I know, and I guess you can be a better person to update that, I am not in UI/UX team contrary to you :) -- 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/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+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 1447566] Re: Need to expose API to notify about user closing the app
StateSaver discards the saved states on SIGTERM. This has been agreed long ago when we stabilised the StateSaver requirements: - states are saved every time the app goes background (inactive) - SIGINT keeps the states saved - SIGTERM, quit() clears the state data, as well as when the app comes foreground So donate assume states being saved when SIGTERM comes. This was like this since 1.0, so we cannot break that. We can however expose an interface to apps so they can save whatever they want. Any other signals we should listen on? -- 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/1447566 Title: Need to expose API to notify about user closing the app Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Apps currently have no way to clean up when a user closes them (swipes an app away in the right-edge switcher). It'd be useful to expose a signal that the app can subscribe to to handle SIGTERM that's sent to it by upstart. The app should not exit until the signal handler returns. Initially we'll rely on upstart to SIGKILL the app after a timeout, but later we'll need to implement a way for the app to suppress that if e.g. it needs to ask the user what to do with unsaved data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1447566/+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 1447113] Re: Page.theme property introduced in 1.2 conflicts with app properties
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/separate-uitk12 -- 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/1447113 Title: Page.theme property introduced in 1.2 conflicts with app properties Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: My app uses Ubuntu.Components 1.1 and one of my Page sub-classes has it's own 'theme' property. When I upgraded my device (mako) to the latest daily release it brought in the new header styles, which introduced a new 'theme' property on Page. Because this new property is marked at FINAL, and my sub-class was trying to redfine it, my app would crash on startup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1447113/+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 1447113] Re: Page.theme property introduced in 1.2 conflicts with app properties
** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = High ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Zsombor Egri (zsombi) ** 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/1447113 Title: Page.theme property introduced in 1.2 conflicts with app properties Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: My app uses Ubuntu.Components 1.1 and one of my Page sub-classes has it's own 'theme' property. When I upgraded my device (mako) to the latest daily release it brought in the new header styles, which introduced a new 'theme' property on Page. Because this new property is marked at FINAL, and my sub-class was trying to redfine it, my app would crash on startup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1447113/+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 1276797] Re: Add keyboard navigation support to the widgets that need it
** Description changed: - TBD + This concerns TAB/Shift+TAB navigation between components. + + We need UX on how/when to highlight the focus component. -- 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/1276797 Title: [sdk] Add keyboard navigation support to the widgets that need it Status in Ubuntu UX bugs: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: This concerns TAB/Shift+TAB navigation between components. We need UX on how/when to highlight the focus component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1276797/+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 1427662] Re: [FFe] Release UITK 1.2
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Triaged = Fix Released -- 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/1427662 Title: [FFe] Release UITK 1.2 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: Dear release team, I would like to request a feature freeze exception for the Ubuntu UI Toolkit package and release it to 15.04. While it is a bugfix only release, it is still a huge change and it is the next layer above Qt and below the Ubuntu Touch applications. The test before the release I will conduct according to the UITK Test Plan https://wiki.ubuntu.com/Process/Merges/TestPlan/ui-toolkit what consists of running all tests for the available core applications. The test results will be put in the regular place like all other test results: http://people.canonical.com/~bzoltan/ The changes of these release are listed here: [ Albert Astals Cid ] * Fix infinite icon size grow when asked for a non square icon Fixes: LP: #1422835 * IconProvider: Make sure icons fit in the given size [ Christian Dywan ] * Skip select_text_longtap_when_active under opengles2. Fixes: LP: #1401140 * Support for multiple devices with push_to_phone.sh. * Take OrientationHelper y coordinate from real parent height. Fixes: LP: #1413194 * Update popover position upon pointer movement. Fixes: LP: #1199502, LP: #1415532 [ Sebastien Bacher ] * document that MainView's applicationName is used to set the gettext domain. Fixes: LP: #1421661. [ Tiago Salem Herrmann ] * Drop cache once properties are successfully restored. [ Timo Jyrinki ] * Add dist-upgrade option to the UITK Test Plan script. Output the selected parameters in the beginning. [ Tim Peeters ] * Add MainView 1.2 which removes the deprecated toolbar support. * Enable PageStack header animations for MainView 1.2. * Fix the size and anchors of a Page that is loaded inside a Loader. This is useful when a Page is Loaded by a Tab. Fixes: LP: #1424635 * Fix UITK gallery content page width. Fixes: LP: #1424635, LP: #1425470 [ Zsombor Egri ] * Alarm services regression fix. Fixes: LP: #1401883 * Implement ListItem dragging support in ListView. Fixes: LP: #119535 * Introducing select/multiselect mode in ListItem. * Moving the tst_focus.qml under exceptions till we fix DatePicker binding loops. * RTL (Right To Left) support in ListItem. * RTM branch diff merge. Fixes: LP: #1358610. * Second stage of simplification - divider group property is an item, simplifying the anchoring of the contentItem. PropertyChange does not backup the property binding, uses QQmlPropertyPrivate::write() with parameter to keep bindings. ListItemAnimator uses behavior to animate snapping. Styling got styledItem context property to obey general styling rules. clicked() and pressAndHold() emission fix when content is swiped. * Transferring the ListItem attached properties to ListItemStyle API. Most of the style API became redundant, and removed. Few API from ListItem were also removed as not needed. ListItemAnimator, UCListItemAttached and UCActionPanel classes removed. Panel swiping overshoot made elastic. Snapping animation transformed into SmoothedAnimation, uses velocity of 60GU/second. Turning warnings to be reported in the error property. SHOW_SERVICEPROPERTIES_WARNINGS environment variable set will display them in the console. Fixes: LP: #1423203. * Updating documentation and imports for 1.2 Vivid (Qt 5.4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1427662/+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 1442550] Re: Documentation missing return values
** 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/1442550 Title: Documentation missing return values Status in Content sharing/picking infrastructure and service: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Many of the methods in the documentation are missing return values. This makes them really hard to read: https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.AbstractButton/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Action/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.ActionItem/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Alarm/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Button/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.CheckBox/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Clipboard/ (one correct, 2 missing) https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.PageStack/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Panel/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.PickerPanel/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Slider/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.TextArea/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.TextField/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.ToolbarButton/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.ListItems.Empty/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.ListItems.ExpandablesColumn/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Pickers.Picker/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Pickers.PickerDelegate/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Popups.Popover/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Popups.PopupBase/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Test.TestExtras/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Test.UbuntuTestCase/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Content.ContentPeer/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Content.ContentTransfer/ Here's an example of a correct one: https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.AlarmModel/ To manage notifications about this bug go to: https://bugs.launchpad.net/content-hub/+bug/1442550/+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 1429899] Re: StateSaver should not restore when app launched from content-hub
** Branch unlinked: lp:~zsombi/ubuntu-ui-toolkit/disable-statesaver- from-urihandler -- 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/1429899 Title: StateSaver should not restore when app launched from content-hub Status in content-hub package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Testing the messaging-app state saving ability that we've been adding from this MR: https://code.launchpad.net/~tiagosh/messaging-app/state-saver2/+merge/250996 deb can be found here: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/1669/artifact/work/output/*zip*/output.zip The problem is, when the app is launched from the content-hub, the StateSaver still tries to restore it's previously saved state, but it should not and this causes problems. It should clear the state, the same way it does when launched via url-dispatcher. According to Ken, there are content-hub signals that StateSaver will need to listen to in order to know when the app is being launched by content-hub. To reproucde: 1) install the messaging-app deb from above 2) open messaging-app, swipe from bottom to create a new message 3) type some names in the recipient field, and type some message in the send field 4) do kill -2 pidOfMessagingApp to kill the messaging-app and save it's state 5) open camera-app and go to the photo roll 6) press Share from toolbar and select messaging-app from the list Expected results: - messaging-app should be displayed with a new page showing the photo as an attachment, and nothing else Actual results: - messaging-app shows the restored state from when it was last run (the values entered in Step 3 above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1429899/+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 1443424] Re: Header blocks key press events from reaching it's Page
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Triaged ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = High ** Tags added: convergence -- 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/1443424 Title: Header blocks key press events from reaching it's Page Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: The Header component added to a Page in a PageStack will prevent key press events from reaching the underlying Page when it is the component that has keyboard focus. 08:35 zsombi_ mhall119: key events should also go to non-focused items... 08:36 zsombi_ mhall119: they don't seem to... 08:36 mhall119 zsombi_: what I'm trying to do is catch an F5 key press on a page to refresh it's content, but if I clicked on the header instead of the content of the Page, it won't work 08:37 zsombi_ mhall119: right, as keys seem to go only to the focused item, in which case it'll be the header... 08:37 mhall119 zsombi_: currently my code looks like http://paste.ubuntu.com/10815509/ 08:39 zsombi_ mhall119: we should have sthing in the header, like Keys.forwardTo: [] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1443424/+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 1442576] Re: Touch input is misaligned when using QT_DEVICE_PIXEL_RATIO=2
You should try to set the GRID_UNIT_PX to 16 (or any multiply of 8 for instance) rather than setting the QT_DEVICE_PIXEL_RATIO env var. Support on that is on the works, but GRID_UNIT_PX will drive the UI scaling of the UI components. -- 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/1442576 Title: Touch input is misaligned when using QT_DEVICE_PIXEL_RATIO=2 Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I have a high-dpi monitor with touch-screen, and when running ubuntu- ui-toolkit-gallery the interface is too small to read. I can fix this by setting the QT_DEVICE_PIXEL_RATIO environment variable to 2. However, the touch screen input still acts as if the scaling is set to 1 - so a press on one button actually triggers a press on another button. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.2.1458+15.04.20150327-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 18:48:39 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-07 (3 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Beta amd64 (20150326) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1442576/+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 1442576] Re: Touch input is misaligned when using QT_DEVICE_PIXEL_RATIO=2
** 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/1442576 Title: Touch input is misaligned when using QT_DEVICE_PIXEL_RATIO=2 Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: I have a high-dpi monitor with touch-screen, and when running ubuntu- ui-toolkit-gallery the interface is too small to read. I can fix this by setting the QT_DEVICE_PIXEL_RATIO environment variable to 2. However, the touch screen input still acts as if the scaling is set to 1 - so a press on one button actually triggers a press on another button. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.2.1458+15.04.20150327-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 18:48:39 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-07 (3 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Beta amd64 (20150326) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1442576/+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 1441499] Re: Unneeded build dependencies in UITK
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = In Progress ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium -- 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/1441499 Title: Unneeded build dependencies in UITK Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: There are some unneeded build dependencies in UI Toolkit: qt5-default: not recommened to be used anymore, can be replaced with a debian/rules change qtbase5-dev-tools: already depended from qtbase5-dev libqt5organizer5: already depended from qtpim5-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1441499/+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 1440289] Re: Touch, background is black and not changeable
This aint seem to be a toolkit bug. ** 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/1440289 Title: Touch, background is black and not changeable Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: On my BQ Aquaris the Background changed to Black. I was closing the Camera App atm. Since these the BG stays Black. When i change it in the Options it has no Effect, also a complete Phone Reset didnt Work. The BG stays black. What Logfiles you need? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1440289/+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 1439680] Re: DatePicker scrolls too quickly, making precision difficult
Thanks for the report, this is a known issue and we need to expose a property in Pickers + tweak the tumbler scroll speed to a proper speed. We are working on a redesigned DatePicker component, so this may fall under a lower priority, however we will add the property driving the Pickers so we can tweak the speed. The new component will use Pickers (tumblers) in Time picking, but not in Date picking. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium ** 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/1439680 Title: DatePicker scrolls too quickly, making precision difficult Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Using the DatePicker is more difficult than it needs to be. OS: 14.09-RTM Ubuntu-Touch on bq aquaris Example: When adding a new event in the Calendar app, I am presented with 2 DatePicker widgets (one for date and one for time). Expected behaviour: I expect to be able to scroll to my desired date and time quickly and efficiently. I expect it to be particularly easy to select values at the 0,15,30,45 minute times. Current behaviour: A small movement on the DatePicker dial causes the dial to spin quickly. It is far too easy to overshoot the desired value (often by a long way), Making a precise selection is fiddly and takes longer than desirable. Common time increments such as 0,15,30 and 45 are no easier to select than 1,16,31 or 46, and the latter are often picked accidently. I don't know if this sensitivity to gesture is due to the high dpi screen, or whether it is resolution independent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1439680/+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 1439393] Re: Alarms aren't ordered by time
Nekhelesh, you are right, the alarms are stored in a map, but the key is a pair built up using date and organiser id, so that may mess up the order. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium ** 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/1439393 Title: Alarms aren't ordered by time Status in Clock application for Ubuntu devices: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: When multiple alarms are added they aren't ordered by the time the alarm is set for, which I'd have expected to be the case. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1439393/+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 1434537] Re: Silo test script fails on rtm-14.09/mako
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = High ** 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/1434537 Title: Silo test script fails on rtm-14.09/mako Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The test script fails on rtm-14.09/mako at least since it finds terminal app's manifest and tries to download terminal app's autopilot tests which fails: --- Checking out lp:ubuntu-terminal-app to /tmp/tmp8WqYm0/work Traceback (most recent call last): File /usr/bin/phablet-click-test-setup, line 266, in module main() File /usr/bin/phablet-click-test-setup, line 255, in main fetch_click_tests(adb, test_dir, args.user, args.click) File /usr/bin/phablet-click-test-setup, line 240, in fetch_click_tests test_dir) File /usr/bin/phablet-click-test-setup, line 208, in get_bzr_tests 'work'], cwd=tmp_dir) File /usr/lib/python2.7/subprocess.py, line 540, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['bzr', 'checkout', '--lightweight', u'lp:ubuntu-terminal-app', '-r', u'161', 'work']' returned non-zero exit status 3 Removing directory /tmp/tmp8WqYm0 Removing directory /tmp/tmp2CN6hA Removing directory /tmp/tmp4FjFXl Removing directory /tmp/tmpjm2dcU Removing directory /tmp/tmpw3ZWgX Removing directory /tmp/tmp3SVDly Failed operation: phablet-click-test-setup has failed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1434537/+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 1441508] Re: Brightness control broke
Sorry, this is not a toolkit bug. ** 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/1441508 Title: Brightness control broke Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: Hi! I have a Ubuntu Aquaris E4.5. To listen to Cutespotify I run the commands: sudo service powered start/ stop To reduce brightness I changed brightness control to manual (the slide was all the way down), since then, my screen is black and i see nothing, but it response normally. Unfortunatly I can't navigate to the brightness control. You know a workaround? Thank you Aquaris Ubuntu armf 14.10 r20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1441508/+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 1415023] Re: sim unlock/lock confirmation button dismisses keyboard but doesn't confirm till pressed again
It seems the button is getting the pressed signal, which removes the OSK. That one triggers the dialog to be grabbed to the centre of the screen, and therefore the release event happens outside the button. -- 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/1415023 Title: sim unlock/lock confirmation button dismisses keyboard but doesn't confirm till pressed again Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: STEPS: Setup: 1 phone + one locked sim 1. Open system settings 2. Goto Security 3. Goto Sim Pin 4. Tap on unlock 5. Type in the pin 6. Tap the green confirm button EXPECTED: I expect the dialog to be dismissed and the keyboard and sim be unlocked ACTUAL: The keyboard is dismissed but the dialog box remains. A recent change has effected this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1415023/+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 1233630] Re: gallery example app: controls hide behind OSK and become inaccessible
*** This bug is a duplicate of bug 1200371 *** https://bugs.launchpad.net/bugs/1200371 OSK disappears when text input looses focus, so the only thing is to get the OSK to push the focus component upwards when opened. ** This bug has been marked a duplicate of bug 1200371 [SDK] auto-scroll input fields when OSK visibility changes -- 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/1233630 Title: gallery example app: controls hide behind OSK and become inaccessible Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: TextField page in ubuntu-ui-toolkit-gallery example doesn't resize itself when OSK pops up, this make it impossible to access text fields below the top texfield control. Also OSK doesn't disappear when control loose the focus and there is no other way to close the OSK manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1233630/+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 1200371] Re: [SDK] auto-scroll input fields when OSK visibility changes
Similar situation is valid also when a component focused using TAB/Shift+TAB key falls outside of the visible area. As all focusable components are derived from StyledItem, I feel we can implant the scrolling functionality into that component. -- 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/1200371 Title: [SDK] auto-scroll input fields when OSK visibility changes Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Currently when you select in an input field, it causes the osk to be displayed. If the field is located beneath the osk it is obscured. Currently many of the apps have to write special code to handle the osk visiblilty and handle scrolling of the field. This should be done automatically by the sdk if the app opt's in somehow. Here is a pointer to code in lp:phone-app that makes the input filed for sending text messages scroll based on osk visibility. Same is repeated in webbrowser-app: http://bazaar.launchpad.net/~phablet-team/phone-app/trunk/view/head:/src/qml/Widgets/KeyboardRectangle.qml http://bazaar.launchpad.net/~phablet-team/phone-app/trunk/view/head:/src/qml/DetailViewCommunication/CommunicationView.qml#L235 You basically anchor the KeyboardRectangle item to the bottom of your view, and then the contents you want to scroll you anchor to the top of the KeyboardRectangle. This KeyboardRectangle is a normal item that has the size of the virtual keyboard. When the keyboard is visible it has the height of the keyboard, when the keyboard is hidden, it has a height of 0 UX Solution The solution identified by Florian above is 100% correct To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1200371/+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 1438976] Re: Lock Security - Passcode and Passphrase input field: selectall/cut/copy entry should not be available
ATM we don't have any possibilities to drive this from outside. We need an API which can tell what clipboard operations are allowed and which don't. -- 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/1438976 Title: Lock Security - Passcode and Passphrase input field: selectall/cut/copy entry should not be available Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: r155, vivid-proposed channel Steps: 1) Enter Security Privacy - Phone locking - Lock security 2) Select 4-digit passcode or Passphrase 3) In the Choose/Confirm passcode/passfhrase fileds, input several charactors, and hold down on field Result: selectall/cut/copy are seen Expected: These edit operations should not be available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1438976/+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 1367689] Re: Ubuntu.Components.Pickers.Picker does not scroll when using the mouse scroll wheel on the desktop
Cannot reproduce with UITK gallery with the today's release. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = 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/1367689 Title: Ubuntu.Components.Pickers.Picker does not scroll when using the mouse scroll wheel on the desktop Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Add a Picker to a QML app 2. Start the app on the desktop 3. Position the mouse pointer over the picker and use the mouse scroll wheel. Nothing happens. What should happen instead: The mouse wheel movement should change the current element shown by the Picker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1367689/+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 1368273] Re: ListItem/Empty.qml: Binding loop detected for property visible
Please us the new ListItem (UITK 1.2) as ListItems.Empty is deprecated.
You can simply replace the ListItem.Empty with ListItem, and remove the
import to Ubuntu.Components.ListItems
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Incomplete = Fix Released
--
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/1368273
Title:
ListItem/Empty.qml: Binding loop detected for property visible
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Bug description:
Looks like having a layout inside a listitem does not work.
This is causing binding loop messages in indicators.
Code to reprocude:
import QtQuick 2.0
import QtQuick.Layouts 1.1
import Ubuntu.Components.ListItems 1.0 as ListItem
ListItem.Empty {
__height: layout.implicitHeight + units.gu(1)
RowLayout {
id: layout
anchors {
left: parent.left
right: parent.right
verticalCenter: parent.verticalCenter
}
Rectangle {
Layout.fillWidth: true
Layout.preferredHeight: units.gu(10)
color: red
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1368273/+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 1298307] Re: PickerPanel with custom Picker component
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = Won't Fix ** No longer affects: ubuntu-ui-toolkit -- 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/1298307 Title: PickerPanel with custom Picker component Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: There should be a way to use PickerPanel with custom picker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1298307/+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 1439149] Re: Magnification to position the cursor correctly in a texfield
*** This bug is a duplicate of bug 1428775 *** https://bugs.launchpad.net/bugs/1428775 We have a task to prototype Jolla-type of magnification, so I'll make this as duplicate of that task. ** This bug has been marked a duplicate of bug 1428775 [SDK] On Long Press in the Text Area, Screen should be magnified to allow precise positioning -- 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/1439149 Title: Magnification to position the cursor correctly in a texfield Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: On Ubuntu touch it is quite hard to position the cursor right in the middle of a word. Android uses a magnification to be able to better select the right position. A function like this would also be good to have on Ubuntu Touch. Here is an image how it looks on another mobile OS: http://webdesignledger.com/wp-content/uploads/2012/04/37-iphone-zoom- text-psd.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1439149/+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 1439102] Re: Dialogs are rotated incorrectly if root item is not a MainView
Christian, this seems to be related to the same OrientationHelper bug I guess. Please mark it as duplicate if it does. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Christian Dywan (kalikiana) ** 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/1439102 Title: Dialogs are rotated incorrectly if root item is not a MainView Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Please test the attached program. When in portrait mode, the dialog will appear with the correct orientation, but when the device is rotated to landscape, the dialog rotates 180 degrees from its original position. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1439102/+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 1433296] Re: Does not build out-of-source
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Benjamin Zeller (zeller-benjamin) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Triaged ** 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/1433296 Title: Does not build out-of-source Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Steps: apt install devscripts equivs bzr branch lp:ubuntu-ui-toolkit mk-build-deps -s sudo -i ubuntu-ui-toolkit mkdir -p uitk-build cd uitk-build qmake ../ubuntu-ui-toolkit make Expected: * builds fine Current: * errors out: Generating localization for localizedApp msgfmt: error while opening po/en_US.po for reading: No such file or directory Makefile:307: recipe for target 'mo' failed make[3]: *** [mo] Error 1 make[3]: Leaving directory '/home/michal/dev/canonical/unity8/uitk-build/tests/unit/tst_i18n' Makefile:255: recipe for target 'sub-tst_i18n-make_first' failed make[2]: *** [sub-tst_i18n-make_first] Error 2 make[2]: Leaving directory '/home/michal/dev/canonical/unity8/uitk-build/tests/unit' Makefile:45: recipe for target 'sub-unit-make_first' failed make[1]: *** [sub-unit-make_first] Error 2 make[1]: Leaving directory '/home/michal/dev/canonical/unity8/uitk-build/tests' Makefile:70: recipe for target 'sub-tests-make_first' failed make: *** [sub-tests-make_first] Error 2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.2.1433+15.04.20150306-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 17 21:17:42 2015 SourcePackage: ubuntu-ui-toolkit SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1433296/+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 1433305] Re: Does not respect PREFIX
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Benjamin Zeller (zeller-benjamin) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Triaged ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium -- 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/1433305 Title: Does not respect PREFIX Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Steps: apt install devscripts equivs bzr branch lp:ubuntu-ui-toolkit mkdir uitk-install mk-build-deps -s sudo -i ubuntu-ui-toolkit cd ubuntu-ui-toolkit qmake PREFIX=`readlink -f ../uitk-install` make install Expected: * builds and installs fine Current: * errors out: make[3]: Entering directory '/home/michal/dev/canonical/unity8/uitk-amd64/modules/Ubuntu/Components' ALARM_BACKEND=memory /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump -notrelocatable Ubuntu.Components 0.1 ../../ 2/dev/null //usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes Makefile.ComponentModule:295: recipe for target 'install_plugins_qmltypes' failed make[3]: *** [install_plugins_qmltypes] Error 2 make[3]: Leaving directory '/home/michal/dev/canonical/unity8/uitk-amd64/modules/Ubuntu/Components' Makefile:81: recipe for target 'sub-ComponentModule-pro-install_subtargets' failed When cross-building: make[3]: Entering directory '/home/michal/dev/canonical/unity8/ubuntu-ui-toolkit/modules/Ubuntu/Components/ListItems' mkdir: cannot create directory ‘/usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components’: Permission denied Makefile:267: recipe for target 'install_qml_files_f4eaca92-c1f0-47bd-bdd3-eda299079fc0' failed make[3]: *** [install_qml_files_f4eaca92-c1f0-47bd-bdd3-eda299079fc0] Error 1 make[3]: Leaving directory '/home/michal/dev/canonical/unity8/ubuntu-ui-toolkit/modules/Ubuntu/Components/ListItems' Makefile:62: recipe for target 'sub-ListItems-install_subtargets' failed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.2.1433+15.04.20150306-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 17 21:17:42 2015 SourcePackage: ubuntu-ui-toolkit SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1433305/+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 1439195] Re: Touchscreen blocked when finger on one of the unvisible hardware keys
This is not a toolkit bug. It's either a HAL bug or a touch related one. ** 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/1439195 Title: Touchscreen blocked when finger on one of the unvisible hardware keys Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: When I hold my BQ Aquarius Phone at the bottom edge and I try to give some input on the touchscreen, it doesn't react. This only happens when my finger is on one of the 3 hardware buttons which would be present on an android device. When it's between the assumed keys, it works without problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1439195/+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 1426042] Re: mako UITK failures started after 2015-02-12 (not because of UITK)
Timo, this seem to be ended? CI at least seems to be back to normal now... -- 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/1426042 Title: mako UITK failures started after 2015-02-12 (not because of UITK) Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: In summary: - Several UITK tests started randomly failing starting with 2015-02-13 Friday image: http://ci.ubuntu.com/smokeng/vivid/touch/mako/97:20150213:20150210/12295/ubuntuuitoolkit/ - The landings for that and the next image were: http://people.canonical.com/~ogra/touch-image-stats/20150213.changes + http://people.canonical.com/~ogra/touch-image-stats/20150213.1.changes - nothing suspicious - It's not UITK landing causing the problem - It does not seem to affect krillin, only mako - Tests failing seem (?) pretty random - Latest results currently at http://ci.ubuntu.com/smokeng/vivid/touch/mako/112:20150226:20150210/12378/ubuntuuitoolkit/ - and see Result History for more. Landings to https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/staging happened on w8 possibly because of CI misconfiguration, even though AP:s were also failing then. And it seems it's still happening, for example: https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/pushToMultiplePhones/+merge/250782 - the AP:s fail, then finally there is a empty CI Approved. This was reported to CI team on Tuesday 24th and they said to investigate it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1426042/+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 1389721] Re: API versioning broken in some cases
Actually we have revisions and we use the same declaration for
components in UI Toolkit as well. And the revisioning of ViewItems
attached properties are also broken, see
https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/listitem-
expansion/+merge/254375, where I had to do an ugly workaround to get the
revisioned API accepted in Expansion.qml test code.
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1389721
Title:
API versioning broken in some cases
Status in qtdeclarative-opensource-src package in Ubuntu:
New
Bug description:
With Oxide 1.2 being the version that's shipping in the RTM image, I
want to start correctly versioning new API's so that we can upgrade
Oxide OTA safely without breaking existing applications. I'm testing
the attached patch for Oxide to add a revision to API's that were
added in 1.3, but running the test suite results in the following
failure:
Output:
--
file:///home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11:11:
.allowedExtraUrlSchemes is not available due to component versioning.
context.allowedExtraUrlSchemes: [ test, bar ]
^
* Start testing of qml-core-test *
Config: Using QtTest library 5.3.0, Qt 5.3.0
QWARN : qml-core-test::tst_CustomURLSchemes::compile()
/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml
produced 1 error(s):
/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11,11:
.allowedExtraUrlSchemes is not available due to component versioning.
Working directory: /home/chr1s/src/oxide/oxide/objdir/qt/tests/qmltests
View: QQuickView, import paths:
'/home/chr1s/src/oxide/oxide/objdir/out/bin'
'/home/chr1s/src/oxide/oxide/objdir/out/imports'
'/usr/lib/x86_64-linux-gnu/qt5/qml'
Plugin paths:
'.'
FAIL! : qml-core-test::tst_CustomURLSchemes::compile()
.allowedExtraUrlSchemes is not available due to component versioning.
Loc:
[/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml(11)]
After scratching my head for a while, I can't see what I'm doing wrong
here.
If I run the following simple QML app, I can access the property
correctly:
- test.qml:
import QtQuick 2.0
import com.canonical.Oxide 1.3
WebView {
focus: true
width: 960
height: 540
url: https://www.google.com;
context: WebContext {
allowedExtraUrlSchemes: []
}
}
However, if I run this simple app instead, then it fails with the same
message I see in the unit tests:
- test.qml:
import QtQuick 2.0
import com.canonical.Oxide 1.3
TestWebView {
focus: true
width: 960
height: 540
url: https://www.google.com;
context.allowedExtraUrlSchemes: []
}
- TestWebView.qml
import QtQuick 2.0
import com.canonical.Oxide 1.3
WebView {
context: WebContext {}
}
This last example works fine without a revision number on this API.
I consider this to be a blocker for being able to update Oxide OTA, as
we're not able to version new API's with this bug
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1389721/+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 1389721] Re: API versioning broken in some cases
+Timo, the bug is in Chris' comment #2. I'll add to the description.
** Description changed:
With Oxide 1.2 being the version that's shipping in the RTM image, I
want to start correctly versioning new API's so that we can upgrade
Oxide OTA safely without breaking existing applications. I'm testing the
attached patch for Oxide to add a revision to API's that were added in
1.3, but running the test suite results in the following failure:
Output:
--
file:///home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11:11:
.allowedExtraUrlSchemes is not available due to component versioning.
context.allowedExtraUrlSchemes: [ test, bar ]
^
* Start testing of qml-core-test *
Config: Using QtTest library 5.3.0, Qt 5.3.0
QWARN : qml-core-test::tst_CustomURLSchemes::compile()
/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml
produced 1 error(s):
/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11,11:
.allowedExtraUrlSchemes is not available due to component versioning.
Working directory: /home/chr1s/src/oxide/oxide/objdir/qt/tests/qmltests
View: QQuickView, import paths:
'/home/chr1s/src/oxide/oxide/objdir/out/bin'
'/home/chr1s/src/oxide/oxide/objdir/out/imports'
'/usr/lib/x86_64-linux-gnu/qt5/qml'
Plugin paths:
'.'
FAIL! : qml-core-test::tst_CustomURLSchemes::compile()
.allowedExtraUrlSchemes is not available due to component versioning.
Loc:
[/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml(11)]
After scratching my head for a while, I can't see what I'm doing wrong
here.
If I run the following simple QML app, I can access the property
correctly:
- test.qml:
import QtQuick 2.0
import com.canonical.Oxide 1.3
WebView {
focus: true
width: 960
height: 540
url: https://www.google.com;
context: WebContext {
allowedExtraUrlSchemes: []
}
}
However, if I run this simple app instead, then it fails with the same
message I see in the unit tests:
- test.qml:
import QtQuick 2.0
import com.canonical.Oxide 1.3
TestWebView {
focus: true
width: 960
height: 540
url: https://www.google.com;
context.allowedExtraUrlSchemes: []
}
- TestWebView.qml
import QtQuick 2.0
import com.canonical.Oxide 1.3
WebView {
context: WebContext {}
}
This last example works fine without a revision number on this API.
I consider this to be a blocker for being able to update Oxide OTA, as
we're not able to version new API's with this bug
+
+ Upstream bug https://bugreports.qt.io/browse/QTBUG-40043 is related to
+ this one.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1389721
Title:
API versioning broken in some cases
Status in qtdeclarative-opensource-src package in Ubuntu:
New
Bug description:
With Oxide 1.2 being the version that's shipping in the RTM image, I
want to start correctly versioning new API's so that we can upgrade
Oxide OTA safely without breaking existing applications. I'm testing
the attached patch for Oxide to add a revision to API's that were
added in 1.3, but running the test suite results in the following
failure:
Output:
--
file:///home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11:11:
.allowedExtraUrlSchemes is not available due to component versioning.
context.allowedExtraUrlSchemes: [ test, bar ]
^
* Start testing of qml-core-test *
Config: Using QtTest library 5.3.0, Qt 5.3.0
QWARN : qml-core-test::tst_CustomURLSchemes::compile()
/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml
produced 1 error(s):
/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11,11:
.allowedExtraUrlSchemes is not available due to component versioning.
Working directory: /home/chr1s/src/oxide/oxide/objdir/qt/tests/qmltests
View: QQuickView, import paths:
'/home/chr1s/src/oxide/oxide/objdir/out/bin'
'/home/chr1s/src/oxide/oxide/objdir/out/imports'
'/usr/lib/x86_64-linux-gnu/qt5/qml'
Plugin paths:
'.'
FAIL! : qml-core-test::tst_CustomURLSchemes::compile()
.allowedExtraUrlSchemes is not available due to component versioning.
Loc:
[/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml(11)]
After scratching my head for a while, I can't see what I'm doing wrong
here.
If I run the following simple QML app, I can access the property
correctly:
- test.qml:
import QtQuick 2.0
import
[Touch-packages] [Bug 1389721] Re: API versioning broken in some cases
+Chris, so to give more help, the workaround:
1) create a new class which derives from the one you want to expose the
revisioned API
2) move all your revisioned API into this one
3) register the new class to the version you need with the same name as in the
previous version
From the upstream bug it looks like everything registered with
qmlRegisterUncreatableTypetype_name, revision() breaks the versioning.
We need to keep this workaround till the bug is fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1389721
Title:
API versioning broken in some cases
Status in qtdeclarative-opensource-src package in Ubuntu:
New
Bug description:
With Oxide 1.2 being the version that's shipping in the RTM image, I
want to start correctly versioning new API's so that we can upgrade
Oxide OTA safely without breaking existing applications. I'm testing
the attached patch for Oxide to add a revision to API's that were
added in 1.3, but running the test suite results in the following
failure:
Output:
--
file:///home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11:11:
.allowedExtraUrlSchemes is not available due to component versioning.
context.allowedExtraUrlSchemes: [ test, bar ]
^
* Start testing of qml-core-test *
Config: Using QtTest library 5.3.0, Qt 5.3.0
QWARN : qml-core-test::tst_CustomURLSchemes::compile()
/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml
produced 1 error(s):
/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11,11:
.allowedExtraUrlSchemes is not available due to component versioning.
Working directory: /home/chr1s/src/oxide/oxide/objdir/qt/tests/qmltests
View: QQuickView, import paths:
'/home/chr1s/src/oxide/oxide/objdir/out/bin'
'/home/chr1s/src/oxide/oxide/objdir/out/imports'
'/usr/lib/x86_64-linux-gnu/qt5/qml'
Plugin paths:
'.'
FAIL! : qml-core-test::tst_CustomURLSchemes::compile()
.allowedExtraUrlSchemes is not available due to component versioning.
Loc:
[/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml(11)]
After scratching my head for a while, I can't see what I'm doing wrong
here.
If I run the following simple QML app, I can access the property
correctly:
- test.qml:
import QtQuick 2.0
import com.canonical.Oxide 1.3
WebView {
focus: true
width: 960
height: 540
url: https://www.google.com;
context: WebContext {
allowedExtraUrlSchemes: []
}
}
However, if I run this simple app instead, then it fails with the same
message I see in the unit tests:
- test.qml:
import QtQuick 2.0
import com.canonical.Oxide 1.3
TestWebView {
focus: true
width: 960
height: 540
url: https://www.google.com;
context.allowedExtraUrlSchemes: []
}
- TestWebView.qml
import QtQuick 2.0
import com.canonical.Oxide 1.3
WebView {
context: WebContext {}
}
This last example works fine without a revision number on this API.
I consider this to be a blocker for being able to update Oxide OTA, as
we're not able to version new API's with this bug
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1389721/+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 1421712] Re: Ubuntu Phone: No keyboard in webapp after a lock screen
Alex, I'll hand this over to you, you can forward to whomever will fix. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Alexandre Abreu (abreu-alexandre) ** 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/1421712 Title: Ubuntu Phone: No keyboard in webapp after a lock screen Status in libunity-webapps package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Hi! Steps: 1. Open a webapp by first time: By example Facebook. 2. Click on username for login Keyboard appears. 3. Block the mobile 4. Unblock the mobile. 5. Click on username Bug: No keyboard. You have to kill the app. Please, see this video: https://copy.com/svmAU1RFZICrl4Lr Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1421712/+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 1428757] Re: [SDK] Header should be responsive for Tablet and Desktop form factors
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Triaged ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = High ** 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/1428757 Title: [SDK] Header should be responsive for Tablet and Desktop form factors Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: As part of our convergence path to Tablet and Desktop form factors, we will have more screen real estate and less constrained. Therefore, we have more space to provide additional affordances. - Optional subheader, with increased flexibility - Max 4 slots on the right - Capability of adding input field expanded or dropdown (not both) - Capability of adding tabs - Capability of having responsive labels display - once breakpoint is reached, labels are displayed UX spec here: https://www.dropbox.com/s/j47sua4ilof0zud/050315_Convergence%20-%20Header_gv.pdf?dl=0 VD link TBC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428757/+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 1428775] Re: [SDK] On Long Press in the Text Area, Screen should be magnified to allow precise positioning
Dropbox link broken ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Christian Dywan (kalikiana) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = High ** 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/1428775 Title: [SDK] On Long Press in the Text Area, Screen should be magnified to allow precise positioning Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: On long press, the user can drag the handle and the whole UI text zooms in 1.5x to allow easier positioning of the handle. https://www.dropbox.com/s/9uc1jtwpmrnjjgb/050315_Convergence%20-%20Text%20selection_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1428775/+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 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Olga, the dropbox link is broken... ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Zsombor Egri (zsombi) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = High ** 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/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+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 1420364] Re: dialog dark background isn't full width on all devices
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Christian Dywan (kalikiana) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = High ** 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/1420364 Title: dialog dark background isn't full width on all devices Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: on Meizu MX4, set px/GU to 22. Then try to launch the UITK dialog. The dimmed background does not fill the whole screen - see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1420364/+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 1421293] Re: Icon width is inconsistent when height is specified
Albert, haven't you provided recently a fix for this?
** 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/1421293
Title:
Icon width is inconsistent when height is specified
Status in ubuntu-ui-toolkit package in Ubuntu:
Incomplete
Bug description:
The width of an Icon {} depends if the Icon is an SVG coming from
image://theme/ or a JPG.
For the SVG the width grows as the units.gu grow, but for the JPEG it
does not and one has to manually add code to maitain the aspect ratio.
See the attached code and files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421293/+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 1428779] Re: [SDK] Tooltips
Dropbox link broken! ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Triaged ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Medium -- 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/1428779 Title: [SDK] Tooltips Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Point Click UIs will need a tooltip component, positioning a popover next to the cursor when Hovering the originating component UX here https://www.dropbox.com/s/rvs88whk2mjeap4/050315_Convergence%20-%20Tooltips_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428779/+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 1430833] Re: obscured history and copy/paste dialogs when tap on search field Edit
Pat, if you managed to drag the history popover, then that is not a toolkit component, as toolkit popovers cannot be dragged! I'll mark the bug incomplete until this is proven to be a toolkit bug. ** 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/1430833 Title: obscured history and copy/paste dialogs when tap on search field Edit Status in the base for Ubuntu mobile products: Incomplete Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Go to Today scope 2. Tap on search icon and then search field 3. Enter some search term, and repeat it few times so that you have few items in search history 4. Now tap on search field again 5. Tap on small arrow connecting the history dialog to search field Observe that dialog will move to middle of screen as seen in attachment == today-search-history.png 6. Now try tapping few times on search field and you will see the history dialog would appear obscured as seen in attachment == today- search-history2.png 7. Tap on search field and press and hold to open the copy paste option Observe that copy paste dialog is hidden as seen in attachment == today-search-hidden-copy-paste.png ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150302-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 11 10:40:12 2015 InstallationDate: Installed on 2014-10-17 (145 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity8 UpgradeStatus: Upgraded to vivid on 2014-12-18 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1430833/+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 1431579] Re: Clock App crashes when clicking on the settings icon
This seems to be related to the AlarmModel.get() function, so I add toolkit to it. ** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Critical ** 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/1431579 Title: Clock App crashes when clicking on the settings icon Status in Clock application for Ubuntu devices: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The app crashes when the settings icon is tapped. This occurs in vivid image #130 on mako. Steps to reproduce the bug: 1. Open the clock app 2. Tap the settings icon in the upper right hand corner Expected results: The app does not crash Actual results: The clock app crashes The following can be found in the logs sometimes, as a result: file:///usr/share/click/preinstalled/com.ubuntu.clock/3.3.192/share/qml/alarm/AlarmDelegate.qml:78: TypeError: Cannot read property 'enabled' of null file:///usr/share/click/preinstalled/com.ubuntu.clock/3.3.192/share/qml/alarm/AlarmUtils.qml:142: TypeError: Cannot read property 'enabled' of null file:///usr/share/click/preinstalled/com.ubuntu.clock/3.3.192/share/qml/alarm/AlarmDelegate.qml:78: TypeError: Cannot read property 'enabled' of null file:///usr/share/click/preinstalled/com.ubuntu.clock/3.3.192/share/qml/alarm/AlarmUtils.qml:142: TypeError: Cannot read property 'enabled' of null To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1431579/+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 1429899] Re: StateSaver should not restore when app launched from content-hub
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/disable-statesaver-from- urihandler -- 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/1429899 Title: StateSaver should not restore when app launched from content-hub Status in content-hub package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Testing the messaging-app state saving ability that we've been adding from this MR: https://code.launchpad.net/~tiagosh/messaging-app/state-saver2/+merge/250996 deb can be found here: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/1669/artifact/work/output/*zip*/output.zip The problem is, when the app is launched from the content-hub, the StateSaver still tries to restore it's previously saved state, but it should not and this causes problems. It should clear the state, the same way it does when launched via url-dispatcher. According to Ken, there are content-hub signals that StateSaver will need to listen to in order to know when the app is being launched by content-hub. To reproucde: 1) install the messaging-app deb from above 2) open messaging-app, swipe from bottom to create a new message 3) type some names in the recipient field, and type some message in the send field 4) do kill -2 pidOfMessagingApp to kill the messaging-app and save it's state 5) open camera-app and go to the photo roll 6) press Share from toolbar and select messaging-app from the list Expected results: - messaging-app should be displayed with a new page showing the photo as an attachment, and nothing else Actual results: - messaging-app shows the restored state from when it was last run (the values entered in Step 3 above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1429899/+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
