[Touch-packages] [Bug 1649077] Re: OSK appears blank in the lock screen
I do use BQ E4.5 as my daily phone and can confirm that this problem was not present in OTA-13. And since Mir hasn't changed between OTA-13 and OTA-14, it could be unity8 or ubuntu-keyboard causing the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1649077 Title: OSK appears blank in the lock screen Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in ubuntu-keyboard package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: After using OTA-14 a while, the OSK starts to exhibit a strange behaviour. 1. It appears blank after a while in the lock screen. You can still press randomly which then makes the OSK to appear fully. When you press a character again it starts to flicker. 2. OSK starts to flicker similar to bug #1590765 which was fixed in OTA-12. It seems to have resurfaced in OTA-14. Systems Info: OTA-14 Stable Channel Devices: E4.5, E5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649077/+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 1649077] Re: OSK appears blank in the lock screen
** Also affects: mir Importance: Undecided Status: New ** Also affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: After using OTA-14 a while, the OSK starts to exhibit a strange - behaviour. It appears blank after a while in the lock screen. You can - still press randomly which then makes the OSK to appear fully. When you - press a character again it starts to flicker. + behaviour. + + 1. It appears blank after a while in the lock screen. You can still + press randomly which then makes the OSK to appear fully. When you press + a character again it starts to flicker. + + 2. OSK starts to flicker similar to bug #1590765 which was fixed in + OTA-12. It seems to have resurfaced in OTA-14. + + Systems Info: + OTA-14 Stable Channel + Devices: E4.5, E5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1649077 Title: OSK appears blank in the lock screen Status in Canonical System Image: New Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in ubuntu-keyboard package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: After using OTA-14 a while, the OSK starts to exhibit a strange behaviour. 1. It appears blank after a while in the lock screen. You can still press randomly which then makes the OSK to appear fully. When you press a character again it starts to flicker. 2. OSK starts to flicker similar to bug #1590765 which was fixed in OTA-12. It seems to have resurfaced in OTA-14. Systems Info: OTA-14 Stable Channel Devices: E4.5, E5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649077/+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 1554621] Re: Invalid use of palette apparent with new SDK
** Changed in: ubuntu-clock-app Status: Fix Committed => 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/1554621 Title: Invalid use of palette apparent with new SDK Status in address-book-app: Fix Released Status in Canonical System Image: Fix Released Status in Ubuntu Music App: Fix Released Status in Tagger: Fix Released Status in Telegram app: Fix Released Status in Ubuntu Clock App: Fix Released Status in Ubuntu File Manager App: Fix Committed Status in camera-app package in Ubuntu: Fix Released Status in content-hub package in Ubuntu: Invalid Status in messaging-app package in Ubuntu: Fix Committed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: The content hub uses the wrong palette values for text (which becomes apparent with new UITK), see screenshot. The new UITK is landing here: https://requests.ci- train.ubuntu.com/#/ticket/905 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: content-hub 0.1+15.04.20160129.1-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Tue Mar 8 18:00:22 2016 InstallationDate: Installed on 2016-03-08 (0 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160308-020304) SourcePackage: content-hub UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1554621/+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 1640443] [NEW] Spread lags a bit at the start
Public bug reported: N4 rc-proposed Steps to reproduce: 1. Open a couple of apps 2. Swipe from the right edge to open the spread. Do this few times with varying speeds. What happens: The spread lags a tiny bit while the apps are being cropped into a square shape What should happen: The spread is smooth and fluid like the previous one. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1640443 Title: Spread lags a bit at the start Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: N4 rc-proposed Steps to reproduce: 1. Open a couple of apps 2. Swipe from the right edge to open the spread. Do this few times with varying speeds. What happens: The spread lags a tiny bit while the apps are being cropped into a square shape What should happen: The spread is smooth and fluid like the previous one. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1640443/+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 1569582] Re: Add Bluetooth apparmor policy
** Tags added: bluetooth -- 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/1569582 Title: Add Bluetooth apparmor policy Status in Canonical System Image: Fix Committed Status in apparmor-easyprof-ubuntu package in Ubuntu: Fix Released Bug description: I have created a content hub plugin that allows sending files via Bluetooth. At this point this only works when unconfined so here is a request to extend the apparmor policies to allow some things over Bluetooth. This plugin does a device discovery and then uses Bluez' obex client to transmit the file. When turning on apparmor on it, it first bails out with the messages below. However, once those are resolved, it'll probably want some more. I have attached the confined package to this bug so it can be easily tested. Please disregard the app in there completey and only evaluate the shareplugin in the package. After installing the click, open the gallery, share an image and select Bluetooth to start the process: [65927.602181] type=1107 audit(1460496066.496:2509): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65927.602199] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65927.607588] type=1107 audit(1460496066.506:2510): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65927.607606] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65928.611714] type=1107 audit(1460496067.506:2511): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65928.611733] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65929.615630] type=1107 audit(1460496068.516:2512): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65929.615649] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65930.619178] type=1107 audit(1460496069.516:2513): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65930.619197] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65931.622804] type=1107 audit(1460496070.516:2514): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65931.622822] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65932.626550] type=1107 audit(1460496071.526:2515): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65932.626569] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65933.630102] type=1107 audit(1460496072.526:2516): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65933.630121] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65934.633739] type=1107 audit(1460496073.536:2517): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [659
[Touch-packages] [Bug 1570948] Re: [Alarm] "Now" not localized in indicator datetime
That's the indicator-datetime displaying the string. Clock app doesn't get involved in displaying stuff on the indicator. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-clock-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1570948 Title: [Alarm] "Now" not localized in indicator datetime Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: New Bug description: Test case. - Switch the phone to Spanish. - Open clock app. - Create an alarm for the next minute. - Open indicator time. Expected result. - "Alarm: Now" must be translated to Spanish. Actual result. - "Now" is not localized. I can't find the string in Launchpad. current build number: 306 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1570948/+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 1568520] [NEW] Expose pressedBackgroundColor in PageHeaderStyle
Public bug reported: At the moment, when you press on a header action button, it shows a "LightGrey" background. It seems the property setting this color is defined at http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/trunk/view/head:/src/Ubuntu/Components/Themes/Ambiance/1.3/IconButtonStyle.qml#L36. This color works fine for white header backgrounds. But once you change the header background to blue, red or any other color, it looks odd. Please expose a property to change this color in the PageHeaderStyle. Something like pressedBackgroundColor would suffice. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: Confirmed ** Summary changed: - Expose pressedbackgroundcolor in PageHeaderStyle + Expose pressedBackgroundColor in PageHeaderStyle -- 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/1568520 Title: Expose pressedBackgroundColor in PageHeaderStyle Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: At the moment, when you press on a header action button, it shows a "LightGrey" background. It seems the property setting this color is defined at http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/trunk/view/head:/src/Ubuntu/Components/Themes/Ambiance/1.3/IconButtonStyle.qml#L36. This color works fine for white header backgrounds. But once you change the header background to blue, red or any other color, it looks odd. Please expose a property to change this color in the PageHeaderStyle. Something like pressedBackgroundColor would suffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1568520/+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 1568019] [NEW] Dialog freezes entire app if its caller is killed before the dialog is killed
Public bug reported: I have noticed that the SDK Dialog has the potential to freeze the app i.e prevent any further user input when the Page which houses the Dialog is killed before the dialog or for some other reason that I am unable to understand. I have created a sample app that you can find at https://code.launchpad.net/~nik90/+junk/freezebug. The sample app is quite explanatory on how to reproduce the bug. Please do note, that the app does not crash. It just doesn't accept any further input. When this happens, I see the following console error, QQmlExpression: Attempted to evaluate an expression in an invalid context ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1568019 Title: Dialog freezes entire app if its caller is killed before the dialog is killed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I have noticed that the SDK Dialog has the potential to freeze the app i.e prevent any further user input when the Page which houses the Dialog is killed before the dialog or for some other reason that I am unable to understand. I have created a sample app that you can find at https://code.launchpad.net/~nik90/+junk/freezebug. The sample app is quite explanatory on how to reproduce the bug. Please do note, that the app does not crash. It just doesn't accept any further input. When this happens, I see the following console error, QQmlExpression: Attempted to evaluate an expression in an invalid context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1568019/+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 1540240] Re: Automatic Header height adjustment should be optional
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Incomplete => 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/1540240 Title: Automatic Header height adjustment should be optional Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: I am currently developing a convergence capable CAD App and i recently switched the UI to use AdaptivePageLayout and the new headers. I have noticed that the header automatically resizes across columns to match the column with the greatest header height. This doesn't suit my particular application as I would like to maintain maximum screen space for the drawing canvas. I have attached some screenshots (early development - dont judge me!!) of what I am seeing. It would be super cool if you could include a flag or option to disable the header adjustment for any particular page or column. UX Fix: A flag will be included in the header component to disable header adjustments, allowing developers to have different header heights for convergence apps. Ideally for full screen applications the header should be set to hidden. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1540240/+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 1423107] Re: Calendars listed in app should match system settings
** Changed in: ubuntu-calendar-app Milestone: None => 0.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1423107 Title: Calendars listed in app should match system settings Status in Ubuntu Calendar App: Confirmed Status in qtorganizer5-eds package in Ubuntu: Confirmed Bug description: It's possible to disable calendars in system settings, but they still appear in the calendar app. These should be in sync. Steps to reproduce:- Install calendar app System settings -> Accounts Add a google account Enable calendar sync for calendar app Open calendar app See calendar listed in the list of calendars Close calendar app In system settings, disable calendar sync for the account Open calendar app In calendar list, note the calendar is still listed We should probably check when entering the calendar list screen if we have access to the calendar, and if we no longer do, should probably suppress the display of that calendar in the list, and events within the calendar itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1423107/+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 1533681] Re: imported google calendar events sound when they shouldn't
** Changed in: ubuntu-calendar-app Milestone: None => 0.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1533681 Title: imported google calendar events sound when they shouldn't Status in Canonical System Image: Confirmed Status in Ubuntu Calendar App: In Progress Status in indicator-datetime package in Ubuntu: In Progress Bug description: I use the calendar-app with my work google calendar. For that calendar I have alarms setup to automatically send an email 24 hours, 4 hours and 30 minutes before any event and I choose email as the reminder (as opposed to popup) so that I wouldn't be bombarded with reminders all day. Unfortunately the calendar app does not make a distinction between email and popup and every event with an email reminder gets imported as an event that gets an event notification on the phone with an alarm sound. I have a lot of events in my calendar and so my phone is constantly making noise at all times of the day. This is particularly annoying at night time since I might get a reminder as early as 3am or 4am, which wakes me up. Of course, I could use silent mode at night, but, like last night, I forgot and was awoken at 6am. Plus, I don't necessarily want the phone in silent mode-- I'd like to be able to hear if a phone call comes in since that is likely an emergency call I need to take. There are a lot of different bugs related to calendar event notifications and if some of them were fixed, it would ameliorate this bug. For example, I've been hoping for a setting to disable sounds for just the calendar (whether via the app or system settings) but otherwise get calendar notifications. Being able to change the alarm sound to 'None' would work too. TBH at this point I don't care which bug is fixed, I need to get this phone to stop sounding off constantly. WORKAROUND: 1. download https://commons.wikimedia.org/wiki/File:Silence.ogg to /home/phablet 2. use gsettings to adjust the sound: $ DISPLAY=:0.0 gsettings get com.canonical.indicator.datetime calendar-default-sound '/usr/share/sounds/ubuntu/ringtones/Marimbach.ogg' $ DISPLAY=:0.0 gsettings set com.canonical.indicator.datetime calendar-default-sound /home/phablet/Silence.ogg $ DISPLAY=:0.0 gsettings get com.canonical.indicator.datetime calendar-default-sound '/home/phablet/Silence.ogg' To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533681/+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 1474078] Re: Provide a way to disable notifications from calendar events
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1474078 Title: Provide a way to disable notifications from calendar events Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: While I like having the calendar on the phone I do not want an audible notification for the events. Would we simply add the calendar app to the Notifications page? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1474078/+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 1440111] Re: [calendar] Reminder notifications are not integrated into system notifications
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1440111 Title: [calendar] Reminder notifications are not integrated into system notifications Status in Canonical System Image: In Progress Status in Ubuntu Calendar App: Fix Released Status in Ubuntu UX: Fix Committed Status in indicator-datetime package in Ubuntu: In Progress Bug description: The calendar app does not use the standard notification system. You can't find it in the "Notifications" area of System Settings, and it uses its own notification sound regardless of what is set in "Sound". Also, reminders are not muted when the phone is in silent mode (I guess it's related). I'm on bq Aquaris, r20 and with the latest calendar-app. --- --- --- --- UX Comment: Calendar Notifications need to be overhauled: -- Calendar Notifications are displayed for too brief a period and should conform to the same timing as other notifications. -- Calendar Notifications are not currently appearing in the notification tray within indicators and should be. -- Calendar Notification title is misleading ('Alarm') and should make clear that the notification relates to a calendar event ('Event') and not a alarm-clock event. -- Calendar Notification's should NOT override silent mode (unlike clock-alarms) although the notification should still be displayed, appear in the notification within indicators and cause the device to vibrate (if enabled) - This is accepted/common behaviour for notifications of this type on mobile. Notifications Spec: https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1440111/+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 1500192] Re: New repeated event does not appear in the week view
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1500192 Title: New repeated event does not appear in the week view Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in qtpim-opensource-src package in Ubuntu: Fix Released Status in qtpim-opensource-src package in Ubuntu RTM: Fix Released Bug description: Configuration: mako OTA 6 Steps to reproduce: 1) click on the calendar (week view) to create a new event, time t date d. 2) edit the new event, choose a title 3) go to repetition, every day, 3 occurences 4) validate the event Behavior: the event does not appear in the week-view (but it appears in the day view) Expected: the event appears in the week-view To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500192/+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 1471588] Re: Wrong time with event series
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1471588 Title: Wrong time with event series Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in qtpim-opensource-src package in Ubuntu: Fix Released Status in qtpim-opensource-src package in Ubuntu RTM: Fix Released Bug description: Hello, steps to reproduce bug: On website of Google calendar I created event, repeating from Monday till Friday with time 8.00-16.00. Next I've edited event, only Thursday and changed time to 8.00 - 17.00, rest remain the same. Last step: I installed Calendar app from store, added Google online account in system settings, enable calendar part. That synced it with Calendar app. I've opened Calendar app and I see that events, but all 5 of them are 8.00 - 16.00. On Google calendar website I see Thursday with changed time (also everything works on my Arch -> KDE Kontact app). PS. Is there a possibility to add Google Tasks to Ubuntu system (Tasks app?)? Where I should report such thing? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471588/+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 1455864] Re: Recurring events not editable after first occurence passed
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1455864 Title: Recurring events not editable after first occurence passed Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in qtpim-opensource-src package in Ubuntu: Fix Released Status in qtpim-opensource-src package in Ubuntu RTM: Fix Released Bug description: Hi there, I can neither edit nor delete a series or single date out of a series, if the first event already started. Edit function is available, but edit and save brings no change to the date. Delete button is available, but no reaction on it Phone: BQ Aquaris 4.5 System: Ubuntu 14.10 (r22) Calendar Version: 0.4.627 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1455864/+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 1470583] Re: Phone notifies me of calendar events multiple times.
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1470583 Title: Phone notifies me of calendar events multiple times. Status in Ubuntu Calendar App: Fix Released Status in indicator-datetime package in Ubuntu: Invalid Status in qtorganizer5-eds package in Ubuntu: Invalid Bug description: Open calendar Create a new event by tapping anywhere in the calendar timeline Tap Untitled new event to modify the time Set time to be a few moments from now Set reminder to be "On event" Time passes... Notification appears, sound rings at time of alarm 2 minutes later Notification appears, sound rings .. and again.. I'd expect it to only go off once. $ system-image-cli --info current build number: 54 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-07-01 10:51:36 version version: 54 version ubuntu: 20150701 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1470583/+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 1447930] Re: yearly appointments repetition incorrect
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1447930 Title: yearly appointments repetition incorrect Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in qtpim-opensource-src package in Ubuntu: Fix Released Status in qtpim-opensource-src package in Ubuntu RTM: Fix Released Bug description: I have entered a wedding day in the calendar. It is of 1.9. - The repeat appointments that I have entered every year, of course, be me in the following years respectively at 1.3. displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447930/+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 1473685] Re: yearly repeating event disappears after creating
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1473685 Title: yearly repeating event disappears after creating Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in qtpim-opensource-src package in Ubuntu: Fix Released Status in qtpim-opensource-src package in Ubuntu RTM: Fix Released Bug description: Steps to reproduce: * create an event * open/edit it * set all day * set recurrence to yearly * save the event after exiting the event, it will disappear from the calendar To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473685/+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 1535207] Re: Agenda page doesn't update immediately if add/remove a daily event
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1535207 Title: Agenda page doesn't update immediately if add/remove a daily event Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in qtpim-opensource-src package in Ubuntu: Fix Released Status in qtpim-opensource-src package in Ubuntu RTM: Fix Released Bug description: Test Environment: $ system-image-cli -i current build number: 232 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-18 03:11:49 version version: 232 version ubuntu: 20160116 version device: 20160108-efc96d8 version custom: 20160111-9 Steps: 1.First launch ubuntu-calendar-app 2.Switch to Agenda view from drop-down menu on the left 3.Tap on menu on the right to create a new daily repeating events 4.Check the Agenda view >It still display empty list with "No upcoming events" 5.Switch to Year view and switch back to Agenda >New added daily events appears, but still can see "No upcoming events" in the background 6.Tap on a repeating event of a day to edit it and delete the series 7.Check the Agenda view >It still displays the event list unless user re-launch the ubuntu-calendar-app Expected result: Agenda view should refresh immediately if any changes To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1535207/+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 1544030] Re: wrong time of event shown from pulldown menu
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1544030 Title: wrong time of event shown from pulldown menu Status in Ubuntu Calendar App: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Bug description: When scheduling an event if you select 'Reminder' -> 'No reminder', the time of event shown from the pulldown top menu displays a time which is one hour BEFORE the actual set start of the event. When setting 'Reminder' to any other option, both times are equal. Fix:if it is a feature just make an option to disable it or set both times equal by default. Also, if actual time is less than one hour before the planned start of the event (with reminder set to 'No Reminder'), the event disappears from the pulldown top menu list. Fix: don't let the event disappear from the pulldown top menu until its duration has expired. Thanks! Using BQ Aquaris 4.5 / OTA 9 / calendar 0.4.757 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1544030/+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 1546466] Re: Some repeating events do not show up
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1546466 Title: Some repeating events do not show up Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in qtpim-opensource-src package in Ubuntu: Fix Released Status in qtpim-opensource-src package in Ubuntu RTM: Fix Released Bug description: When introducing a new repeating event, it is not shown in the calendar app. After a sync, it appears in Google calendar online, but it remains still invisible on the phone in Day view, or in some cases invisible in all views. Sync is also failing to complete after that. A partial sync occurs. I also noticed another wrong behaviour: since some events remained invisible, I introduced these several times, with the consequence that the webinterface of the Google calendar shows all the instances I introduced. When I delete these events from the calendar online, these events reappear in the calendar online after a sync. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546466/+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 1373945] Re: There is no way to set default calendar, it always takes Personal
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1373945 Title: There is no way to set default calendar, it always takes Personal Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in qtorganizer5-eds package in Ubuntu: Fix Committed Bug description: There is no way to set default calendar, it always takes Personal calender while creating an event. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373945/+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 1364653] Re: Daily Recurring Events need refresh to appear when created from DayView
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1364653 Title: Daily Recurring Events need refresh to appear when created from DayView Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in qtpim-opensource-src package in Ubuntu: Fix Released Status in qtpim-opensource-src package in Ubuntu RTM: Fix Released Bug description: When I create a daily recurring event from the DayView that starts on that day, the EventBubble does not immediately appear on the current Day. I can swipe to go to future days, and the EventBubble appears there. If I swipe back to return to the original Day, or I go to a different view (MonthView, WeekView, etc.) the event appears. Since the EventBubble appears after re-navigating to the page in any way, this appears to be a "refreshing" problem, where the DayView isn't updated after creating a recurring event. Steps to Reproduce 1) Open the Calendar App, and go to any day on the DayView. 2) Create a recurring event starting on that day, which re-occurs daily. 3) Save the new event and return to the DayView. The EventBubble should not appear on the DayView for the current Day. Expected: The EventBubble should appear on the DayView page immediately after returning from creating the event. A reproduction of this behavior can be seen at: https://www.youtube.com/watch?v=9NK9m8ZznrA&feature=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1364653/+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 1433121] Re: SDK docs missing palette values
This bug has been fixed as far as I can see on developer.ubuntu.com. The palette values can be found at https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.Themes.PaletteValues/. Marking this bug as fixed. ** 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/1433121 Title: SDK docs missing palette values Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: I noticed in the QtC SDK docs, that the palette values are missing..the ones like Theme.palette.foregroundText etc... This is however present in the online docs -> https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Themes.PaletteValues/. Could we please get this added as it is really helpful to know the palette values especially when the application subtheming is getting better by the day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1433121/+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 1448017] Re: Apps crash when opening tab menus in landscape mode
I cannot reproduce this bug anymore on the latest phone images. Marking this bug as fixed. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => 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/1448017 Title: Apps crash when opening tab menus in landscape mode Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: On devel-proposed, *every* application that I tested crashes when trying to open the tab menu or the header menu in landscape mode. Note: This bug is not reproducible on the RTM Utopic image as of OTA-3. Steps to reproduce: 1. Open gallery app 2. Switch to landscape mode by tilting phone. 3. Press the tab menu What happens: phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 184 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-24 11:26:49 version version: 184 version ubuntu: 20150424 version device: 20150210 version custom: 20150424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1448017/+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 1561668] [NEW] SectionStyle shouldn't use backgroundTertiaryText to set the color of selected section
Public bug reported: Looking at SectionStyle.qml [1], it seems the section headers use theme.palette.selected.backgroundTertiaryText to set the color. As I understand backgroundText, backgroundSecondaryText and backgroundTertiaryText are used to denote levels. The page sections have only 1 label and thereby should use theme.palette.selected.backgroundText instead. On talking to timp, he did make me understand that the main page header uses backgroundText while the section headers uses tertiaryText which does make sense. But that is something other app devs won't think of. May be the solution is to show a visual illustration where each SDK component shows what palette color it is using. Do note that this is not about which set (normal, disabled, selected, highlighted) to use, but rather the actual palette value. [1] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/staging/view/head:/src/Ubuntu/Components/Themes/Ambiance/1.3/SectionsStyle.qml ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1561668 Title: SectionStyle shouldn't use backgroundTertiaryText to set the color of selected section Status in Ubuntu UX: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Looking at SectionStyle.qml [1], it seems the section headers use theme.palette.selected.backgroundTertiaryText to set the color. As I understand backgroundText, backgroundSecondaryText and backgroundTertiaryText are used to denote levels. The page sections have only 1 label and thereby should use theme.palette.selected.backgroundText instead. On talking to timp, he did make me understand that the main page header uses backgroundText while the section headers uses tertiaryText which does make sense. But that is something other app devs won't think of. May be the solution is to show a visual illustration where each SDK component shows what palette color it is using. Do note that this is not about which set (normal, disabled, selected, highlighted) to use, but rather the actual palette value. [1] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/staging/view/head:/src/Ubuntu/Components/Themes/Ambiance/1.3/SectionsStyle.qml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1561668/+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 1372011] Re: ListItem.Subtitled subText color is too dark with SuruDark
** Changed in: permy Status: New => In Progress ** Changed in: permy Assignee: (unassigned) => Nekhelesh Ramananthan (nik90) ** Branch linked: lp:~nik90/permy/update-permy-1.3 -- 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/1372011 Title: ListItem.Subtitled subText color is too dark with SuruDark Status in permy: In Progress Status in Ubuntu UX: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: It is hard to read ListItem.Subtitled subText when using the SuruDark theme (or other dark themes). To manage notifications about this bug go to: https://bugs.launchpad.net/permy/+bug/1372011/+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 1408015] Re: [sdk][UX] Confirmation in the header bar confusing
** Changed in: ubuntu-calendar-app Milestone: 0.5 => 0.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1408015 Title: [sdk][UX] Confirmation in the header bar confusing Status in Quick Memo: New Status in Ubuntu Calendar App: Triaged Status in Ubuntu Clock App: Fix Released Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: Imagine a form of some sort, you fill a few fields of data top-down, and at the end of it you need to tap in the header at the top to save/confirm. Pair that with the header going off-screen to leave more screen for the content, you have to pull the header in first (and you need to know that's where the button will be). An example of this behaviour is the calendar app when adding/editing an event. One other example (although that could be improved easily by auto-saving the new note as soon as it's edited) is the Quick Memo app, where when you create a note in the first place you need to tap the ✓ icon, but when you're editing, it's all auto-saved and you need to tap 〈 to go back to the list of notes. I feel like we need to at least come up with clear guidance on what belongs in the header, and where a footer with buttons should be used (we have a way to stick something on top of the keyboard after all¹). http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView /#anchorToKeyboard-prop ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 17:03:54 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) --- UX comment & resolution -- The back button in the header should never be used as a confirmation but can mean CANCEL and not just BACK. If an action or any alterations within the content/screen have to be confirmed/saved then it requires a visible call to action. This call to action sits by default in the header unless differently specified by designer/developer. In all here described cases the UX can be improved easily by adding clarity to the UI and sometimes just adding a call to action. The header can be fixed or can go off-screen the specification for that lies with the designer/developer. This means if I have an important action in the header which I want to present to the user all the time, then the header stays fixed, even if the content is scrolled. Clock app: When creating a new alarm by swiping from the bottom of the screen, the tick (confirmation) icon should be disabled. Only after interacting with the screen, by changing one of the parameters for example, the tick should be enabled. This will signal to user that there was a change and this needs to be confirmed. Even more informative is a simple word instead of the tick: SAVE. The SAVE option is a new addition to the header and wasn't available so far. This concept is already documented in the UI - Toolkit spec which is at the bottom of this post. If user taps back before saving then the alarm won't be created. Additionally there can be visual feedback by adding the "feedback bubble" to the UI. If the user taps back before saving the feedback bubble states, e.g. "Alarm not saved". If the tick icon is tapped, it can state "Alarm saved" (see Notification spec). In the Repeat section the select all icon has to move one to the left and a tick or "save added". The behaviour will then follow as described above. Note app: There is nothing wrong with the note app approach but it is a custom made behaviour which is up to the developer. This person decided not to use our pattern and include a tick or SAVE into the header. There are many note taking apps on iOS which are not using their patterns either. This doesn't mean they are bad, they just work differently. While it is ok to use a "Send Order" or a NEXT at the end of a form, for some instances and apps it won't be efficient. This means < CANCEL/BACK and CONFIRM (tick/save/done) can sit in the header but it is not possible to control apps which don't want to user out UI- Toolkit, hence the other solutions will exist too. We are constantly improving the UI-Toolit and I will add the footer/toolbar idea to potential new projects for design. Please see for reference the notification spec: https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1# Please see for reference the UI - Toolkit spec: https://docs.google.com/document
[Touch-packages] [Bug 1554621] Re: Invalid use of palette apparent with new SDK
** Changed in: ubuntu-clock-app Status: In Progress => Fix Committed -- 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/1554621 Title: Invalid use of palette apparent with new SDK Status in address-book-app: Confirmed Status in Canonical System Image: Confirmed Status in messaging-app: Confirmed Status in Ubuntu Music App: In Progress Status in Tagger: New Status in Telegram app: Confirmed Status in Ubuntu Clock App: Fix Committed Status in Ubuntu File Manager App: Confirmed Status in camera-app package in Ubuntu: Fix Released Status in content-hub package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: The content hub uses the wrong palette values for text (which becomes apparent with new UITK), see screenshot. The new UITK is landing here: https://requests.ci- train.ubuntu.com/#/ticket/905 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: content-hub 0.1+15.04.20160129.1-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Tue Mar 8 18:00:22 2016 InstallationDate: Installed on 2016-03-08 (0 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160308-020304) SourcePackage: content-hub UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1554621/+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 1558526] Re: Animation between months are not similar
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1558526 Title: Animation between months are not similar Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: r274, rc-proposed, arale 0. swipe from top edge (open indicator) 1. be sure you are in time indicator, focus calendar 2. swipe from middle of the calendar, from the right side (will show next/futur month) 3. Watch the transition, the smooth animation. Do it 2-3 time to be sure you record it 4. now scroll from middle of the calendar to the right (to show previous/past month) 5. Wacth the transition, looks like a tiny lag appears (if you don't release the finger to force a slow transition, you will notice that tiny lag appears when the "month - year " title above the calendar refreshs itself To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1558526/+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 1525474] Re: Indic characters are not visible
Considering that Ubuntu Phones are being sold in India through SnapDeal this is an important bug to fix imo. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1525474 Title: Indic characters are not visible Status in Canonical System Image: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Ubuntu Touch is not displaying characters of many Indic scripts including Bengali (except Devnagari). Any app or webpage containing characters from these scripts are shown blank. A quick examination of /usr/share/fonts showed that the required fonts were missing. After I added fonts myself, rendering was okay. I am proposing the addition of the following packages. ttf-bengali-fonts ttf-gujarati-fonts ttf-kannada-fonts These packages would allow the rendering of the most popular indic fonts in use. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1525474/+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 1377996] Re: [phone-app] is freezing on active call screen
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1377996 Title: [phone-app] is freezing on active call screen Status in Canonical System Image: New Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. phone device (make sure phone app is not running & the device is awake) 2. accept the call from the incoming snap decision 3. wait until active call screen appears 4. navigate back to the keypad 5. tap the now green indicator bar to return back to call 6. tap the tone dial in call controls 7. Actual result: One the first, 2nd or 3rd tap the screen is frozen. Even if you hang up the phone you called from, the screen remains. Sometimes the screen freezes when you try to navigate back and forth from keypad to active call. Try several different ways. A few times, I was able to hang up the phone I was calling from but the active call screen stayed on the device. The only way to make the phone app work again was to force quit it. As an alternative route. Try to call the phone when the phone-app is running. Accept the call and wait until the active call screen appears. Try to interact with the tone dial icon in the call controls. I was able to reproduce the freeze this way as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1377996/+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 1554621] Re: Invalid use of palette apparent with new SDK in content-hub
** Changed in: ubuntu-clock-app Status: Confirmed => In Progress ** Changed in: ubuntu-clock-app Milestone: None => 3.8 ** Changed in: ubuntu-clock-app Assignee: (unassigned) => Ken VanDine (ken-vandine) -- 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/1554621 Title: Invalid use of palette apparent with new SDK in content-hub Status in address-book-app: Confirmed Status in camera-app: Confirmed Status in Canonical System Image: Confirmed Status in messaging-app: Confirmed Status in Ubuntu Music App: Confirmed Status in Tagger: New Status in Telegram app: Confirmed Status in Ubuntu Clock App: In Progress Status in Ubuntu File Manager App: Confirmed Status in content-hub package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: The content hub uses the wrong palette values for text (which becomes apparent with new UITK), see screenshot. The new UITK is landing here: https://requests.ci- train.ubuntu.com/#/ticket/905 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: content-hub 0.1+15.04.20160129.1-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Tue Mar 8 18:00:22 2016 InstallationDate: Installed on 2016-03-08 (0 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160308-020304) SourcePackage: content-hub UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1554621/+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 1393485] Re: [SDK] Need a standard way to make an Icon look disabled
@tpeeters Does this also apply to the header icons as well that cannot visually be distinguished between active and disabled icons? -- 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/1393485 Title: [SDK] Need a standard way to make an Icon look disabled Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: [Updated description] Right now if one wants to use an Icon inside a ListItem.Empty or any other AbstractButton derived class, and disable the item, there is no standard way to make the Icon look disabled without directly affecting its opacity and/or colorization. Haviing a standard way to do this would help promoting consistency in the UI. --- UX Solution --- Agreed. Disabled icons should have 30% opacity by default, but that can be changed by the App developer ––– Desired solution: Adjust the opacity to 30% (0.3) for all disabled icons. This will be consistent with our disabled states on buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1393485/+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 1439049] Re: Indicator entry doesn’t open event details
** Changed in: ubuntu-calendar-app Milestone: None => 0.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1439049 Title: Indicator entry doesn’t open event details Status in Ubuntu Calendar App: In Progress Status in indicator-datetime package in Ubuntu: Confirmed Bug description: When activating the indicator entry for an event, the calendar app is launched, but starts with the default view (e.g., the current day). I would expect the calendar to show the event details, in the same way as when I click an event in the calendar app itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1439049/+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 1408015] Re: [sdk][UX] Confirmation in the header bar confusing
** Changed in: ubuntu-calendar-app Assignee: (unassigned) => Nekhelesh Ramananthan (nik90) -- 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/1408015 Title: [sdk][UX] Confirmation in the header bar confusing Status in Quick Memo: New Status in Ubuntu Calendar App: Triaged Status in Ubuntu Clock App: Fix Released Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Imagine a form of some sort, you fill a few fields of data top-down, and at the end of it you need to tap in the header at the top to save/confirm. Pair that with the header going off-screen to leave more screen for the content, you have to pull the header in first (and you need to know that's where the button will be). An example of this behaviour is the calendar app when adding/editing an event. One other example (although that could be improved easily by auto-saving the new note as soon as it's edited) is the Quick Memo app, where when you create a note in the first place you need to tap the ✓ icon, but when you're editing, it's all auto-saved and you need to tap 〈 to go back to the list of notes. I feel like we need to at least come up with clear guidance on what belongs in the header, and where a footer with buttons should be used (we have a way to stick something on top of the keyboard after all¹). http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView /#anchorToKeyboard-prop ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 17:03:54 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) --- UX comment & resolution -- The back button in the header should never be used as a confirmation but can mean CANCEL and not just BACK. If an action or any alterations within the content/screen have to be confirmed/saved then it requires a visible call to action. This call to action sits by default in the header unless differently specified by designer/developer. In all here described cases the UX can be improved easily by adding clarity to the UI and sometimes just adding a call to action. The header can be fixed or can go off-screen the specification for that lies with the designer/developer. This means if I have an important action in the header which I want to present to the user all the time, then the header stays fixed, even if the content is scrolled. Clock app: When creating a new alarm by swiping from the bottom of the screen, the tick (confirmation) icon should be disabled. Only after interacting with the screen, by changing one of the parameters for example, the tick should be enabled. This will signal to user that there was a change and this needs to be confirmed. Even more informative is a simple word instead of the tick: SAVE. The SAVE option is a new addition to the header and wasn't available so far. This concept is already documented in the UI - Toolkit spec which is at the bottom of this post. If user taps back before saving then the alarm won't be created. Additionally there can be visual feedback by adding the "feedback bubble" to the UI. If the user taps back before saving the feedback bubble states, e.g. "Alarm not saved". If the tick icon is tapped, it can state "Alarm saved" (see Notification spec). In the Repeat section the select all icon has to move one to the left and a tick or "save added". The behaviour will then follow as described above. Note app: There is nothing wrong with the note app approach but it is a custom made behaviour which is up to the developer. This person decided not to use our pattern and include a tick or SAVE into the header. There are many note taking apps on iOS which are not using their patterns either. This doesn't mean they are bad, they just work differently. While it is ok to use a "Send Order" or a NEXT at the end of a form, for some instances and apps it won't be efficient. This means < CANCEL/BACK and CONFIRM (tick/save/done) can sit in the header but it is not possible to control apps which don't want to user out UI- Toolkit, hence the other solutions will exist too. We are constantly improving the UI-Toolit and I will add the footer/toolbar idea to potential new projects for design. Please see for reference the notification spec: https://docs.google.com/document/d/1
[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3
** Changed in: ubuntu-clock-app 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-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1508363 Title: Coordinated migration to UITK 1.3 Status in Canonical System Image: In Progress Status in Ubuntu Music App: Fix Released Status in Ubuntu Notes app: Fix Committed Status in Tagger: Fix Released Status in task-app: In Progress Status in Ubuntu Calculator App: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in Ubuntu Clock App: Fix Released Status in Ubuntu Document Viewer App: Fix Released Status in Ubuntu Shorts App: Fix Committed Status in Ubuntu Weather App: Fix Released Status in Weather: Fix Released Status in address-book-app package in Ubuntu: Fix Committed Status in calendar-app package in Ubuntu: Confirmed Status in camera-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Committed Status in gallery-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Committed Status in music-app package in Ubuntu: Confirmed Status in reminders-app package in Ubuntu: Fix Committed Status in ubuntu-clock-app package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Status in ubuntu-weather-app package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: The migration to 1.3 needs to happen in a coordinated way, so that shell and all apps we care of migrate within the same OTA window to reduce visual inconsistencies to a minimum. This bug is a means to collect all the projects affected and keep tabs on what's happening. NOTES: - The toolkit has the following modules: Ubuntu.Components 1.3 Ubuntu.Components.ListItems 1.3 Ubuntu.Components.Pickers 1.3 Ubuntu.Components.Popups 1.3 Ubuntu.Components.Styles 1.3 Ubuntu.Components.Themes 1.3 Ubuntu.Components.Themes.Ambiance 1.3 Ubuntu.Components.Themes.SuruDark 1.3 - The following modules were not altered recently: Ubuntu.Layouts 1.0 Ubuntu.PerformanceMetrics 1.0 - Theme is now theme (lowercase) - PageHeadStyle now has a "config" property In manifest.json file use: "framework": "ubuntu-sdk-15.04.1-qml" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508363/+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 1552100] Re: Move to .snap
While this may be premature on the phone, do remember that Mark said Ubuntu 16.04 will have support for snaps (or was it click packages). So If I am able to run the latest clock-app or any of the core apps on 16.04 regardless of whether the host 16.04 system has the latest dependencies, I consider this bug report worth resolving. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1552100 Title: Move to .snap Status in Canonical System Image: Opinion Status in Ubuntu Music App: Triaged Status in Ubuntu Notes app: Triaged Status in Telegram app: Triaged Status in Ubuntu Calendar App: Triaged Status in Ubuntu Clock App: Triaged Status in Ubuntu Document Viewer App: Triaged Status in Ubuntu File Manager App: Triaged Status in Ubuntu Terminal App: Triaged Status in Ubuntu Weather App: Triaged Status in webbrowser-app package in Ubuntu: Invalid Bug description: Move all packages to .snap (snappy) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552100/+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 1552100] Re: Move to .snap
** Also affects: ubuntu-clock-app Importance: Undecided Status: New ** Changed in: ubuntu-clock-app Importance: Undecided => Low ** Changed in: ubuntu-clock-app Status: New => Triaged ** Changed in: ubuntu-clock-app Milestone: None => 3.x.backlog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1552100 Title: Move to .snap Status in Canonical System Image: Opinion Status in Ubuntu Music App: Triaged Status in Ubuntu Notes app: Triaged Status in Telegram app: Triaged Status in Ubuntu Calendar App: Triaged Status in Ubuntu Clock App: Triaged Status in Ubuntu Document Viewer App: Triaged Status in Ubuntu File Manager App: Triaged Status in Ubuntu Terminal App: Triaged Status in Ubuntu Weather App: Triaged Status in webbrowser-app package in Ubuntu: Invalid Bug description: Move all packages to .snap (snappy) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552100/+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 1408015] Re: [sdk][UX] Confirmation in the header bar confusing
** Changed in: ubuntu-calendar-app Milestone: None => 0.5 ** Changed in: ubuntu-calendar-app Status: New => Triaged ** Changed in: ubuntu-calendar-app 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/1408015 Title: [sdk][UX] Confirmation in the header bar confusing Status in Quick Memo: New Status in Ubuntu Calendar App: Triaged Status in Ubuntu Clock App: Fix Released Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Imagine a form of some sort, you fill a few fields of data top-down, and at the end of it you need to tap in the header at the top to save/confirm. Pair that with the header going off-screen to leave more screen for the content, you have to pull the header in first (and you need to know that's where the button will be). An example of this behaviour is the calendar app when adding/editing an event. One other example (although that could be improved easily by auto-saving the new note as soon as it's edited) is the Quick Memo app, where when you create a note in the first place you need to tap the ✓ icon, but when you're editing, it's all auto-saved and you need to tap 〈 to go back to the list of notes. I feel like we need to at least come up with clear guidance on what belongs in the header, and where a footer with buttons should be used (we have a way to stick something on top of the keyboard after all¹). http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView /#anchorToKeyboard-prop ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 17:03:54 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) --- UX comment & resolution -- The back button in the header should never be used as a confirmation but can mean CANCEL and not just BACK. If an action or any alterations within the content/screen have to be confirmed/saved then it requires a visible call to action. This call to action sits by default in the header unless differently specified by designer/developer. In all here described cases the UX can be improved easily by adding clarity to the UI and sometimes just adding a call to action. The header can be fixed or can go off-screen the specification for that lies with the designer/developer. This means if I have an important action in the header which I want to present to the user all the time, then the header stays fixed, even if the content is scrolled. Clock app: When creating a new alarm by swiping from the bottom of the screen, the tick (confirmation) icon should be disabled. Only after interacting with the screen, by changing one of the parameters for example, the tick should be enabled. This will signal to user that there was a change and this needs to be confirmed. Even more informative is a simple word instead of the tick: SAVE. The SAVE option is a new addition to the header and wasn't available so far. This concept is already documented in the UI - Toolkit spec which is at the bottom of this post. If user taps back before saving then the alarm won't be created. Additionally there can be visual feedback by adding the "feedback bubble" to the UI. If the user taps back before saving the feedback bubble states, e.g. "Alarm not saved". If the tick icon is tapped, it can state "Alarm saved" (see Notification spec). In the Repeat section the select all icon has to move one to the left and a tick or "save added". The behaviour will then follow as described above. Note app: There is nothing wrong with the note app approach but it is a custom made behaviour which is up to the developer. This person decided not to use our pattern and include a tick or SAVE into the header. There are many note taking apps on iOS which are not using their patterns either. This doesn't mean they are bad, they just work differently. While it is ok to use a "Send Order" or a NEXT at the end of a form, for some instances and apps it won't be efficient. This means < CANCEL/BACK and CONFIRM (tick/save/done) can sit in the header but it is not possible to control apps which don't want to user out UI- Toolkit, hence the other solutions will exist too. We are constantly improving the UI-Toolit and I will add the footer/toolbar idea to potential new projects for design. Please see for reference the notification spec: https://docs.google.com/document/d/1xDSZ_
[Touch-packages] [Bug 1382516] Re: Event reminders stored in UTC but triggered in local timezone
** Changed in: ubuntu-calendar-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1382516 Title: Event reminders stored in UTC but triggered in local timezone Status in Ubuntu Calendar App: Fix Released Status in qtorganizer5-eds package in Ubuntu: Confirmed Bug description: phablet@ubuntu-phablet:~$ click list | grep com.ubuntu.calendarcom.ubuntu.calendar0.4.502 phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 4 device name: mako channel: ubuntu-touch/ubuntu-rtm/14.09 last update: 2014-10-08 09:47:10 version version: 4 version ubuntu: 20141007 version device: 20140929.1 version custom: mako-0.5 When creating events with reminders at "Event time", the reminder is stored in UTC, but triggered in local time. I first noticed this when creating events in BST (UTC+0100). STR: - Set device timezone to something other than GMT/UTC. - Open Calendar - From the actions mention, select New Event - Fill in some basics - time /date, event name, location, reminder at "Event time".. - Save the event - Wait until the alotted time, and observe the absence of a reminder. Setting my timezone to SAST (UTC+0200) and adding an event 5 minutes into the future, no reminder fired. However, changing the date to 2h5m into the future, the reminder fired 2h before the event. So it looks like the reminder is being *stored* in UTC, but *fired* in local time. Here is the entry from ~/.local/share/evolution/calendar/system/calendar.ics: BEGIN:VEVENT UID:20141017T094649Z-6046-32011-1750-1@ubuntu-phablet DTSTAMP:20141017T100018Z DTSTART:20141017T120200 DTEND:20141017T130200 X-LIC-ERROR;X-LIC-ERRORTYPE=VALUE-PARSE-ERROR:Can't parse as RECUR value in RRULE property. Removing entire property: ERROR: No Value LOCATION:Here DTSTART:20141017T120200 DTEND:20141017T130200 X-LIC-ERROR;X-LIC-ERRORTYPE=VALUE-PARSE-ERROR:Can't parse as RECUR value in RRULE property. Removing entire property: ERROR: No Value LOCATION:Here SUMMARY:Test Event SEQUENCE:1 LAST-MODIFIED:20141017T100018Z END:VEVENT END:VCALENDAR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1382516/+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 1508363] Re: Coordinated migration to UITK 1.3
** Changed in: ubuntu-calendar-app Status: In Progress => Fix Released ** Changed in: ubuntu-calendar-app Milestone: None => 0.5 ** Changed in: ubuntu-calendar-app Assignee: Alan Pope (popey) => Renato Araujo Oliveira Filho (renatofilho) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1508363 Title: Coordinated migration to UITK 1.3 Status in Canonical System Image: In Progress Status in Ubuntu Music App: Fix Released Status in Ubuntu Notes app: Fix Committed Status in Tagger: Fix Released Status in task-app: In Progress Status in Ubuntu Calculator App: Fix Committed Status in Ubuntu Calendar App: Fix Released Status in Ubuntu Clock App: Fix Committed Status in Ubuntu Document Viewer App: Fix Released Status in Ubuntu Shorts App: Fix Committed Status in Ubuntu Weather App: Fix Released Status in Weather: Fix Released Status in address-book-app package in Ubuntu: Fix Committed Status in calendar-app package in Ubuntu: Confirmed Status in camera-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Committed Status in gallery-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Committed Status in music-app package in Ubuntu: Confirmed Status in reminders-app package in Ubuntu: Fix Committed Status in ubuntu-clock-app package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Status in ubuntu-weather-app package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: The migration to 1.3 needs to happen in a coordinated way, so that shell and all apps we care of migrate within the same OTA window to reduce visual inconsistencies to a minimum. This bug is a means to collect all the projects affected and keep tabs on what's happening. NOTES: - The toolkit has the following modules: Ubuntu.Components 1.3 Ubuntu.Components.ListItems 1.3 Ubuntu.Components.Pickers 1.3 Ubuntu.Components.Popups 1.3 Ubuntu.Components.Styles 1.3 Ubuntu.Components.Themes 1.3 Ubuntu.Components.Themes.Ambiance 1.3 Ubuntu.Components.Themes.SuruDark 1.3 - The following modules were not altered recently: Ubuntu.Layouts 1.0 Ubuntu.PerformanceMetrics 1.0 - Theme is now theme (lowercase) - PageHeadStyle now has a "config" property In manifest.json file use: "framework": "ubuntu-sdk-15.04.1-qml" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508363/+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 1440111] Re: [calendar] Reminder notifications are not integrated into system notifications
** Changed in: ubuntu-calendar-app Importance: Undecided => Medium ** Changed in: ubuntu-calendar-app Assignee: (unassigned) => David Barth (dbarth) ** Changed in: ubuntu-calendar-app Milestone: None => 0.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1440111 Title: [calendar] Reminder notifications are not integrated into system notifications Status in Canonical System Image: In Progress Status in Ubuntu Calendar App: Fix Committed Status in Ubuntu UX: Fix Committed Status in indicator-datetime package in Ubuntu: In Progress Bug description: The calendar app does not use the standard notification system. You can't find it in the "Notifications" area of System Settings, and it uses its own notification sound regardless of what is set in "Sound". Also, reminders are not muted when the phone is in silent mode (I guess it's related). I'm on bq Aquaris, r20 and with the latest calendar-app. --- --- --- --- UX Comment: Calendar Notifications need to be overhauled: -- Calendar Notifications are displayed for too brief a period and should conform to the same timing as other notifications. -- Calendar Notifications are not currently appearing in the notification tray within indicators and should be. -- Calendar Notification title is misleading ('Alarm') and should make clear that the notification relates to a calendar event ('Event') and not a alarm-clock event. -- Calendar Notification's should NOT override silent mode (unlike clock-alarms) although the notification should still be displayed, appear in the notification within indicators and cause the device to vibrate (if enabled) - This is accepted/common behaviour for notifications of this type on mobile. Notifications Spec: https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1440111/+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 1474078] Re: Provide a way to disable notifications from calendar events
** Changed in: ubuntu-calendar-app Assignee: (unassigned) => David Barth (dbarth) ** Changed in: ubuntu-calendar-app Milestone: None => 0.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1474078 Title: Provide a way to disable notifications from calendar events Status in Canonical System Image: In Progress Status in Ubuntu Calendar App: Fix Committed Status in indicator-datetime package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: While I like having the calendar on the phone I do not want an audible notification for the events. Would we simply add the calendar app to the Notifications page? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1474078/+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 1549783] Re: Indicator shows "Tomorrow" for an alarm happening today when checked after midnight
** Description changed: BQ E4.5 (krillin) running OTA9.1 I have 2 recurring alarms set for 0730 and 0800. If I pull down the clock indicator bar after midnight, the 0730 alarm is listed as "Tomorrow". The Clock app lists the alarm correctly (although, if I rememebr correctly, there was previously a bug where the clock app would get this wrong too). The alarm functions correctly, but the indicator is unsettling. + + Steps to reproduce bug: + 1. Create an alarm for *tomorrow morning*, say at 08:00 AM using the clock app. + 2. When you swipe down the datetime indicator, it should correctly say that the alarm is scheduled for tomorrow 08:00 AM. + 3. Open the system-settings app, and manually change the time to after midnight, say 02:00 AM next day. + 4. Now swipe down the datetime indicator and it still says alarm scheduled for tomorrow 08:00 AM instead of "08:00AM". + 5. Reopen the clock app and you will notice that it correctly say alarm is scheduled to run in another 6 hours (08:00AM minus 02:00AM) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1549783 Title: Indicator shows "Tomorrow" for an alarm happening today when checked after midnight Status in indicator-datetime package in Ubuntu: Confirmed Bug description: BQ E4.5 (krillin) running OTA9.1 I have 2 recurring alarms set for 0730 and 0800. If I pull down the clock indicator bar after midnight, the 0730 alarm is listed as "Tomorrow". The Clock app lists the alarm correctly (although, if I rememebr correctly, there was previously a bug where the clock app would get this wrong too). The alarm functions correctly, but the indicator is unsettling. Steps to reproduce bug: 1. Create an alarm for *tomorrow morning*, say at 08:00 AM using the clock app. 2. When you swipe down the datetime indicator, it should correctly say that the alarm is scheduled for tomorrow 08:00 AM. 3. Open the system-settings app, and manually change the time to after midnight, say 02:00 AM next day. 4. Now swipe down the datetime indicator and it still says alarm scheduled for tomorrow 08:00 AM instead of "08:00AM". 5. Reopen the clock app and you will notice that it correctly say alarm is scheduled to run in another 6 hours (08:00AM minus 02:00AM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1549783/+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
I cannot reproduce this bug in rc-proposed images. Thereby marking this bug invalid. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Triaged => 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/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: Invalid 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 1487696] Re: [Custom sound]It is not possible to stop upload new sound
** Changed in: ubuntu-clock-app Milestone: 3.7 => 3.8 -- 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/1487696 Title: [Custom sound]It is not possible to stop upload new sound Status in Ubuntu Clock App: Triaged Status in content-hub package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Prepare some big sound file (about 100MB). You could just download some from Youtube 2. Run Clock 3. Edit alarm 4. Click button "Add custom sound" 5 Select big sound file 6. The copying message will appear Currently: - "Cancel" button is not working. - After closing Clock application, an reopening it the sound alarm name is "qt_temp". Fortunately it is working corretly Expected - "Cancel" button is working. - if file is big (above 50MB) some warning should be displayed - Before copying, the free disc space needs to be checked - After closing Clock application during file copying, the correct name should be in alarm sounds list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1487696/+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 1532607] Re: Phone not usable while a call comes in - followed by "restart"
I also noticed a few things after the crash, - the first being the proximity sensor which now behaves like the phone is in a call and blanks the screen when your hands reach the top of the phone during normal usage. - Second being the call which is dropped is not recorded/listed in the dialer app. I suppose this could be because dialer-app only adds call to the history list after it is ended. The crash triggers seems rather random. I have had it crash with just one app running and also with several apps running. Can't find a reliable way to reproduce it :/ Hopefully the unity-system- compositor.log provided by pat should help. I will upload mine as well in the next comment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1532607 Title: Phone not usable while a call comes in - followed by "restart" Status in Canonical System Image: Confirmed Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: My system: current build number: 225 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-09 06:52:53 version version: 225 version ubuntu: 20160109 version device: 20151216-378d4f3 version custom: 2015--36-46-vivid What happened: Someone called me and I wanted to take the call on the phone (nothing attached to the phone). The screen was locked and I pressed the power button to unlock the screen. The phone did not react on any pushed buttons. The phone continued ringing but I was not able to do anything with the phone during this time. During the next minute the phone was blocked. After this period a "restart" followed. "Restart": The restart was not a real reset. The phone screen was black. Then approx. 1 - 2 minutes after the call was gone, the screen went on again and the ubuntu logo with the dots appeared (same screen when you start the phone but without the "bq"-screen). I did not need to enter the PIN code of the SIM card. The phone was again fully operational. This happened on January, 10th at approx. 13:30 h. I have attached the sys.log for your review and hopefully for tracing back the issue to the root cause. Matthias To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+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 1539396] Re: [regression] Unity8 restarts in the middle of a call since the OTA-9 update
Sorry about the empty tar. This one should have the correct logs. ** Attachment added: "unitylogs.tar.gz" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539396/+attachment/4559000/+files/unitylogs.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539396 Title: [regression] Unity8 restarts in the middle of a call since the OTA-9 update Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: New Bug description: I have had Unity8 restarting while making a call or in the middle of a call since the OTA-9 update. It occurred at least 3-4 times during the day. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539396/+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 1539396] Re: [regression] Unity8 restarts in the middle of a call since the OTA-9 update
I'm afraid /var/crash folder is empty since crash reporting is disabled by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539396 Title: [regression] Unity8 restarts in the middle of a call since the OTA-9 update Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: New Bug description: I have had Unity8 restarting while making a call or in the middle of a call since the OTA-9 update. It occurred at least 3-4 times during the day. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539396/+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 1539396] Re: [regression] Unity8 restarts in the middle of a call since the OTA-9 update
Attached /home/phablet/.cache/upstart/unity8.log* ** Attachment added: "Unity8 Logs" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539396/+attachment/4558938/+files/unity8-logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539396 Title: [regression] Unity8 restarts in the middle of a call since the OTA-9 update Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: New Bug description: I have had Unity8 restarting while making a call or in the middle of a call since the OTA-9 update. It occurred at least 3-4 times during the day. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539396/+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 1539396] [NEW] [regression] Unity8 restarts in the middle of a call since the OTA-9 update
Public bug reported: I have had Unity8 restarting while making a call or in the middle of a call since the OTA-9 update. It occurred at least 3-4 times during the day. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539396 Title: [regression] Unity8 restarts in the middle of a call since the OTA-9 update Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: I have had Unity8 restarting while making a call or in the middle of a call since the OTA-9 update. It occurred at least 3-4 times during the day. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539396/+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 1508081] Re: Fails to receive OTA updates
When looking at http://paste.ubuntu.com/14689175/ (ubuntu-download- manager.INFO log file), I0128 20:44:51.668818 4255 network_session.cpp:68] Connection type gsm <-- it thinks its on GSM Elleo: iirc it won't do automatic downloads of updates in GSM mode, unless you've set it to allow that in settings I think it'll just queue it up and wait for the network type to change to wifi I think we need to rethink the logic of that as queueing it up then prevents the user from being able to manually press the download button I think nik90: can you try connecting to wifi and see if it suddenly starts going? By changing the auto-download settings in the settings-app to always download, I was able to get OTA-9. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1508081 Title: Fails to receive OTA updates Status in Canonical System Image: In Progress Status in ubuntu-download-manager package in Ubuntu: In Progress Bug description: Ubuntu Touch 15.04 (r23) [mako] Issue: Phone appears to fail to receive OTA updates. Previously, I jumped from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears to be released on 2015 Oct 16. Expected behavior: System Settings > System > Updates (or System Settings > About this phone > Check for updates) reveals new image that I can release and download. Actual behavior: Checking for updates... > Software is up to date See the comment regarding similar issues for large app installs. It seems if anything interrupts the transfer or if the connection is somewhat slow the download performance degenerates then times out. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508081/+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 1508081] Re: Fails to receive OTA updates
I am experiencing this issue with my pristine BQ E4.5 device. Here is the output of ubuntu-download-manager.ERROR located in /var/log/ubuntu- download-manager Log file created at: 2016/01/12 14:47:54 Running on machine: ubuntu-phablet Log line format: [IWEF]mmdd hh:mm:ss.uu threadid file:line] msg E0112 14:47:54.00 30763 downloads_db.cpp:133] Could not create the data path /var/cache/ubuntu-download-manager E0112 14:47:54.005391 30763 downloads_db.cpp:147] out of memory Error opening database -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1508081 Title: Fails to receive OTA updates Status in Canonical System Image: In Progress Status in ubuntu-download-manager package in Ubuntu: In Progress Bug description: Ubuntu Touch 15.04 (r23) [mako] Issue: Phone appears to fail to receive OTA updates. Previously, I jumped from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears to be released on 2015 Oct 16. Expected behavior: System Settings > System > Updates (or System Settings > About this phone > Check for updates) reveals new image that I can release and download. Actual behavior: Checking for updates... > Software is up to date See the comment regarding similar issues for large app installs. It seems if anything interrupts the transfer or if the connection is somewhat slow the download performance degenerates then times out. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508081/+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 1508363] Re: Coordinated migration to UITK 1.3
** Changed in: ubuntu-clock-app Milestone: None => 3.7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1508363 Title: Coordinated migration to UITK 1.3 Status in Canonical System Image: In Progress Status in Ubuntu Music App: Fix Released Status in Ubuntu Notes app: New Status in Ubuntu Calculator App: Fix Committed Status in Ubuntu Calendar App: In Progress Status in Ubuntu Clock App: Fix Committed Status in Ubuntu Document Viewer App: Fix Released Status in Ubuntu Shorts App: Fix Committed Status in Ubuntu Weather App: Fix Released Status in Weather: New Status in address-book-app package in Ubuntu: Fix Committed Status in calendar-app package in Ubuntu: Confirmed Status in camera-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Committed Status in gallery-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Committed Status in music-app package in Ubuntu: Confirmed Status in reminders-app package in Ubuntu: Fix Committed Status in ubuntu-clock-app package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Status in ubuntu-weather-app package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: The migration to 1.3 needs to happen in a coordinated way, so that shell and all apps we care of migrate within the same OTA window to reduce visual inconsistencies to a minimum. This bug is a means to collect all the projects affected and keep tabs on what's happening. NOTES: - The toolkit has the following modules: Ubuntu.Components 1.3 Ubuntu.Components.ListItems 1.3 Ubuntu.Components.Pickers 1.3 Ubuntu.Components.Popups 1.3 Ubuntu.Components.Styles 1.3 Ubuntu.Components.Themes 1.3 Ubuntu.Components.Themes.Ambiance 1.3 Ubuntu.Components.Themes.SuruDark 1.3 - The following modules were not altered recently: Ubuntu.Layouts 1.0 Ubuntu.PerformanceMetrics 1.0 - Theme is now theme (lowercase) - PageHeadStyle now has a "config" property In manifest.json file use: "framework": "ubuntu-sdk-15.04.1-qml" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508363/+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 1364647] Re: Can't hear clock alarm when headphones are plugged in but not in your ears
Could we try to target this for OTA-8 or even OTA-9 consideirng it is quite a nuisance that alarms cannot be heard if headphones are used to listen to music while sleeping. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1364647 Title: Can't hear clock alarm when headphones are plugged in but not in your ears Status in Canonical System Image: Confirmed Status in Ubuntu Clock App: Invalid Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When a bluetooth or wired headset the phone embedded speakerphone should ring anyway as you probably won't wear an headset while sleeping, while you prefer keeping your headset connected all the times. -- SOLUTION -- Alarms should *always* be played to the speaker phones, as well as in the wired/wireless headset. (The equivalent for the ringtone is bug 1364647.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1364647/+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 1502684] Re: Enable Seconds on the Clock
Thanks for taking the time to report this bug. The clock app does not follow the gsettings show-seconds. Confined apps afaik don't have access to read gsettings. That said, it is a good idea to respect the settings of the user by following the indicator-datetime preferences. Will talk to the designers and indicator-datetime developers about this. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-clock-app Milestone: None => 3.x.backlog ** Changed in: ubuntu-clock-app Importance: Undecided => Medium ** Changed in: ubuntu-clock-app Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1502684 Title: Enable Seconds on the Clock Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: New Bug description: on Ubuntu touch when ever trying to set the clock to display seconds on the clock using gsettings, the value is getting updated but the clock is not showing the seconds. Following is the command that i used to enable seconds on the clock gsettings set com.canonical.indicator.datetime show-seconds true After this when i check the value, it is showing true but the clock is not showing the seconds even after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1502684/+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 1502684] Re: Enable Seconds on the Clock
@charles, since clock app cannot read gsettings, could you perhaps expose this as a dbus settings (similar to the alarm settings properties) that clock app can then read and enable seconds if indicator-datetime is showing it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1502684 Title: Enable Seconds on the Clock Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: New Bug description: on Ubuntu touch when ever trying to set the clock to display seconds on the clock using gsettings, the value is getting updated but the clock is not showing the seconds. Following is the command that i used to enable seconds on the clock gsettings set com.canonical.indicator.datetime show-seconds true After this when i check the value, it is showing true but the clock is not showing the seconds even after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1502684/+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 1500050] Re: No way to stop an alarm that has been snoozed
** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1500050 Title: No way to stop an alarm that has been snoozed Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: New Bug description: Once a user snoozes an alarm, there is no way to stop the alarm without having to wait for the snooze period to be over. The indicator datetime should provide options to completely stop the alarm like Android does. This pattern can already been seen in the messaging indicator where users can reply to messages. Another example is a missed call where users can either call back or message them via the action buttons show in the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1500050/+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 1500050] [NEW] No way to stop an alarm that has been snoozed
Public bug reported: Once a user snoozes an alarm, there is no way to stop the alarm without having to wait for the snooze period to be over. The indicator datetime should provide options to completely stop the alarm like Android does. This pattern can already been seen in the messaging indicator where users can reply to messages. Another example is a missed call where users can either call back or message them via the action buttons show in the indicator. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1500050 Title: No way to stop an alarm that has been snoozed Status in indicator-datetime package in Ubuntu: New Bug description: Once a user snoozes an alarm, there is no way to stop the alarm without having to wait for the snooze period to be over. The indicator datetime should provide options to completely stop the alarm like Android does. This pattern can already been seen in the messaging indicator where users can reply to messages. Another example is a missed call where users can either call back or message them via the action buttons show in the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1500050/+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 1427566] Re: [Clock][UX] Add timers functionality
@Robie, that's a great idea. I have appended it to the bug description to ensure we don't forget it. ** Description changed: I'm greatly missing timers from the clock app. In Android I use them all the time for fixed time periods (laundry/bread/cooking/tea is ready, etc.), and it's rather inconvenient to have to create a gazillion alarms at a fixed time for these. I'm not sure why they got removed, but could we have them back please? Thanks for considering! - Before we will implement this we need to fix: https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1480200 + + -- Additional feature request, + I have a UX request when setting the timer. In addition to setting the time remaining until it expires (as you'd expect), I'd like to also switch to the ability to setting the clock time that I want it to expire. This would be very similar to setting an alarm of course, but the alarm setting UI is geared towards persistent alarms, not ephemeral ones. + + Example use case: there's a one-off thing I need to do at 2pm. I could + set an alarm for 2pm by adding a new alarm, and then going in and + deleting the alarm after it has rung but this is tedious. Alternatively + I could calculate the time until 2pm myself and then quickly set a timer + for that length of time. This way there is no alarm to delete after it + has expired. I'd like to just go to the timer section and add a timer to + ring at 2pm by toggling to an "ETA" display instead of "time remaining" + and setting it from there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1427566 Title: [Clock][UX] Add timers functionality Status in Indicator Date and Time: New Status in Ubuntu Clock App: Triaged Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I'm greatly missing timers from the clock app. In Android I use them all the time for fixed time periods (laundry/bread/cooking/tea is ready, etc.), and it's rather inconvenient to have to create a gazillion alarms at a fixed time for these. I'm not sure why they got removed, but could we have them back please? Thanks for considering! Before we will implement this we need to fix: https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1480200 -- Additional feature request, I have a UX request when setting the timer. In addition to setting the time remaining until it expires (as you'd expect), I'd like to also switch to the ability to setting the clock time that I want it to expire. This would be very similar to setting an alarm of course, but the alarm setting UI is geared towards persistent alarms, not ephemeral ones. Example use case: there's a one-off thing I need to do at 2pm. I could set an alarm for 2pm by adding a new alarm, and then going in and deleting the alarm after it has rung but this is tedious. Alternatively I could calculate the time until 2pm myself and then quickly set a timer for that length of time. This way there is no alarm to delete after it has expired. I'd like to just go to the timer section and add a timer to ring at 2pm by toggling to an "ETA" display instead of "time remaining" and setting it from there. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+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 1494620] Re: Allow turning alarm off directly in the indicator
** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-clock-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1494620 Title: Allow turning alarm off directly in the indicator Status in indicator-datetime package in Ubuntu: New Bug description: Hello, since I switched from Android to Ubuntu full-time I've been among other things using my Ubuntu phone as my alarm. However, I mostly wake up a few minutes before the alarm actually starts and in that case I no longer want it to make any noises once I am already up. On Android I could kill the alarm directly from the "indicator" but here I have to go to the indicator, hit the alarm listed there, an app opens, I have to slide from the bottom to reveal all alarms and then I can kill it. It is too much complicated to do such an easy task. I know this is not really a bug, just an idea, and I would very much appreciate it to be implemented :), would save me some tome each morning :). I suggest to implement slide left/right to kill it or maybe better just a simple "delete" button :). Thank you very much for considering this and supplying some more thoughts on this topic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1494620/+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 1427566] Re: [Clock][UX] Add timers functionality
** Changed in: ubuntu-clock-app Milestone: 3.6 => 3.x.backlog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1427566 Title: [Clock][UX] Add timers functionality Status in Indicator Date and Time: New Status in Ubuntu Clock App: Triaged Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I'm greatly missing timers from the clock app. In Android I use them all the time for fixed time periods (laundry/bread/cooking/tea is ready, etc.), and it's rather inconvenient to have to create a gazillion alarms at a fixed time for these. I'm not sure why they got removed, but could we have them back please? Thanks for considering! Before we will implement this we need to fix: https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1480200 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+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 1408015] Re: [sdk][UX] Confirmation in the header bar confusing
** Changed in: ubuntu-clock-app 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/1408015 Title: [sdk][UX] Confirmation in the header bar confusing Status in Quick Memo: New Status in Ubuntu Calendar App: New Status in Ubuntu Clock App: Fix Released Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Imagine a form of some sort, you fill a few fields of data top-down, and at the end of it you need to tap in the header at the top to save/confirm. Pair that with the header going off-screen to leave more screen for the content, you have to pull the header in first (and you need to know that's where the button will be). An example of this behaviour is the calendar app when adding/editing an event. One other example (although that could be improved easily by auto-saving the new note as soon as it's edited) is the Quick Memo app, where when you create a note in the first place you need to tap the ✓ icon, but when you're editing, it's all auto-saved and you need to tap 〈 to go back to the list of notes. I feel like we need to at least come up with clear guidance on what belongs in the header, and where a footer with buttons should be used (we have a way to stick something on top of the keyboard after all¹). http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView /#anchorToKeyboard-prop ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 17:03:54 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) --- UX comment & resolution -- The back button in the header should never be used as a confirmation but can mean CANCEL and not just BACK. If an action or any alterations within the content/screen have to be confirmed/saved then it requires a visible call to action. This call to action sits by default in the header unless differently specified by designer/developer. In all here described cases the UX can be improved easily by adding clarity to the UI and sometimes just adding a call to action. The header can be fixed or can go off-screen the specification for that lies with the designer/developer. This means if I have an important action in the header which I want to present to the user all the time, then the header stays fixed, even if the content is scrolled. Clock app: When creating a new alarm by swiping from the bottom of the screen, the tick (confirmation) icon should be disabled. Only after interacting with the screen, by changing one of the parameters for example, the tick should be enabled. This will signal to user that there was a change and this needs to be confirmed. Even more informative is a simple word instead of the tick: SAVE. The SAVE option is a new addition to the header and wasn't available so far. This concept is already documented in the UI - Toolkit spec which is at the bottom of this post. If user taps back before saving then the alarm won't be created. Additionally there can be visual feedback by adding the "feedback bubble" to the UI. If the user taps back before saving the feedback bubble states, e.g. "Alarm not saved". If the tick icon is tapped, it can state "Alarm saved" (see Notification spec). In the Repeat section the select all icon has to move one to the left and a tick or "save added". The behaviour will then follow as described above. Note app: There is nothing wrong with the note app approach but it is a custom made behaviour which is up to the developer. This person decided not to use our pattern and include a tick or SAVE into the header. There are many note taking apps on iOS which are not using their patterns either. This doesn't mean they are bad, they just work differently. While it is ok to use a "Send Order" or a NEXT at the end of a form, for some instances and apps it won't be efficient. This means < CANCEL/BACK and CONFIRM (tick/save/done) can sit in the header but it is not possible to control apps which don't want to user out UI- Toolkit, hence the other solutions will exist too. We are constantly improving the UI-Toolit and I will add the footer/toolbar idea to potential new projects for design. Please see for reference the notification spec: https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1# Please see for reference the UI - Toolkit spec: https://docs.google.com
[Touch-packages] [Bug 1354370] Re: [Alarm][UX] default sound for alarm doesn't get its job done
** Changed in: ubuntu-clock-app 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-touch-sounds in Ubuntu. https://bugs.launchpad.net/bugs/1354370 Title: [Alarm][UX] default sound for alarm doesn't get its job done Status in clock-app: Invalid Status in Ubuntu Clock App: Fix Released Status in Ubuntu UX: Fix Committed Status in ubuntu-touch-sounds package in Ubuntu: Fix Released Bug description: While the default sound for alarms is a nice sound, it's not really suited for an alarm. It's way too low and soft. I mostly don't even hear it when I'm awake and there's not much chance this sound would wake me up from sleeping. IMO it should be something a bit more aggressive. To manage notifications about this bug go to: https://bugs.launchpad.net/clock-app/+bug/1354370/+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 1487696] Re: [Custom sound]It is not possible to stop upload new sound
** Summary changed: - [Custom sound]It is not possible to stop upload new soun + [Custom sound]It is not possible to stop upload new sound -- 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/1487696 Title: [Custom sound]It is not possible to stop upload new sound Status in Ubuntu Clock App: Triaged Status in content-hub package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Prepare some big sound file (about 100MB). You could just download some from Youtube 2. Run Clock 3. Edit alarm 4. Click button "Add custom sound" 5 Select big sound file 6. The copying message will appear Currently: - "Cancel" button is not working. - After closing Clock application, an reopening it the sound alarm name is "qt_temp". Fortunately it is working corretly Expected - "Cancel" button is working. - if file is big (above 50MB) some warning should be displayed - Before copying, the free disc space needs to be checked - After closing Clock application during file copying, the correct name should be in alarm sounds list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1487696/+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 1487696] Re: [Custom sound][content-hub] It is not possible to stop upload new sound
After discussing with Kenvandine, instead of copying the files from music-app over to the clock-app directory, we need to using hardlinks instead. This way the transfer will be instant and the user will not hit this bug anymore. ** Changed in: content-hub (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-clock-app Status: Incomplete => Triaged ** Summary changed: - [Custom sound][content-hub] It is not possible to stop upload new sound + [Custom sound]It is not possible to stop upload new soun -- 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/1487696 Title: [Custom sound]It is not possible to stop upload new soun Status in Ubuntu Clock App: Triaged Status in content-hub package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Prepare some big sound file (about 100MB). You could just download some from Youtube 2. Run Clock 3. Edit alarm 4. Click button "Add custom sound" 5 Select big sound file 6. The copying message will appear Currently: - "Cancel" button is not working. - After closing Clock application, an reopening it the sound alarm name is "qt_temp". Fortunately it is working corretly Expected - "Cancel" button is working. - if file is big (above 50MB) some warning should be displayed - Before copying, the free disc space needs to be checked - After closing Clock application during file copying, the correct name should be in alarm sounds list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1487696/+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 1476713] Re: Certain scopes previews don't show Comment box even after installing them
** Also affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1476713 Title: Certain scopes previews don't show Comment box even after installing them Status in Canonical System Image: New Status in unity-scope-click package in Ubuntu: New Bug description: I have noticed for quite some time that certain scopes like Ubuntu News (by Chris Wayne), Uapp Explorer don't show comment boxes in the scope preview page. As a result I am unable to review those scopes. I am unable to notice in a pattern as for other scopes I can review them properly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1476713/+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 1489037] Re: Change defaut alarm sound to "Alarm clock.ogg"
** Description changed: With OTA-6 (as per bug 1354370), the default alarm sound has been changed from "Suru arpeggio.ogg" to "Alarm clock.ogg". Indicator- datetime will have to set this as default on its end. + + Note: Clock App will set "Alarm clock.ogg" as the default alarm sound + for new alarms created by the user starting with clock app v3.5.362. + This bug is to ensure that the fallback alarm played by indicator- + datetime is also "Alarm clock.ogg" (which is used when the user sets an + invalid alarm tone). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1489037 Title: Change defaut alarm sound to "Alarm clock.ogg" Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: With OTA-6 (as per bug 1354370), the default alarm sound has been changed from "Suru arpeggio.ogg" to "Alarm clock.ogg". Indicator- datetime will have to set this as default on its end. Note: Clock App will set "Alarm clock.ogg" as the default alarm sound for new alarms created by the user starting with clock app v3.5.362. This bug is to ensure that the fallback alarm played by indicator- datetime is also "Alarm clock.ogg" (which is used when the user sets an invalid alarm tone). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489037/+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 1489322] [NEW] [Wily Qtcreator 3.5] SDK Docs are not shown in Contents view in Assistant and Qtcreator
Public bug reported: Using Qtcreator 3.5 in Wily, I cannot find the Ubuntu SDK docs under Contents in the Help tab. As a result, it is not possible to see all the Ubuntu SDK compnents in one area to look at. It only appears under Index. krnekhelesh@dell-jenkins:~/Documents/replace-alarmsound-checkbox$ apt-cache policy qtcreator-plugin-ubuntu qtcreator-plugin-ubuntu: Installed: 3.5.0+15.10.20150817-0ubuntu2 Candidate: 3.5.0+15.10.20150817-0ubuntu2 Version table: *** 3.5.0+15.10.20150817-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ wily/universe i386 Packages 100 /var/lib/dpkg/status krnekhelesh@dell-jenkins:~/Documents/replace-alarmsound-checkbox$ apt-cache policy qtdeclarative5-ubuntu-ui-toolkit-plugin qtdeclarative5-ubuntu-ui-toolkit-plugin: Installed: 1.3.1603+15.10.20150812-0ubuntu1 Candidate: 1.3.1603+15.10.20150812-0ubuntu1 Version table: *** 1.3.1603+15.10.20150812-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ wily/main i386 Packages 100 /var/lib/dpkg/status ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Description changed: Using Qtcreator 3.5 in Wily, I cannot find the Ubuntu SDK docs under Contents in the Help tab. As a result, it is not possible to see all the Ubuntu SDK compnents in one area to look at. It only appears under Index. + + krnekhelesh@dell-jenkins:~/Documents/replace-alarmsound-checkbox$ apt-cache policy qtcreator-plugin-ubuntu + qtcreator-plugin-ubuntu: + Installed: 3.5.0+15.10.20150817-0ubuntu2 + Candidate: 3.5.0+15.10.20150817-0ubuntu2 + Version table: + *** 3.5.0+15.10.20150817-0ubuntu2 0 + 500 http://archive.ubuntu.com/ubuntu/ wily/universe i386 Packages + 100 /var/lib/dpkg/status + krnekhelesh@dell-jenkins:~/Documents/replace-alarmsound-checkbox$ apt-cache policy qtdeclarative5-ubuntu-ui-toolkit-plugin + qtdeclarative5-ubuntu-ui-toolkit-plugin: + Installed: 1.3.1603+15.10.20150812-0ubuntu1 + Candidate: 1.3.1603+15.10.20150812-0ubuntu1 + Version table: + *** 1.3.1603+15.10.20150812-0ubuntu1 0 + 500 http://archive.ubuntu.com/ubuntu/ wily/main i386 Packages + 100 /var/lib/dpkg/status -- 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/1489322 Title: [Wily Qtcreator 3.5] SDK Docs are not shown in Contents view in Assistant and Qtcreator Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Using Qtcreator 3.5 in Wily, I cannot find the Ubuntu SDK docs under Contents in the Help tab. As a result, it is not possible to see all the Ubuntu SDK compnents in one area to look at. It only appears under Index. krnekhelesh@dell-jenkins:~/Documents/replace-alarmsound-checkbox$ apt-cache policy qtcreator-plugin-ubuntu qtcreator-plugin-ubuntu: Installed: 3.5.0+15.10.20150817-0ubuntu2 Candidate: 3.5.0+15.10.20150817-0ubuntu2 Version table: *** 3.5.0+15.10.20150817-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ wily/universe i386 Packages 100 /var/lib/dpkg/status krnekhelesh@dell-jenkins:~/Documents/replace-alarmsound-checkbox$ apt-cache policy qtdeclarative5-ubuntu-ui-toolkit-plugin qtdeclarative5-ubuntu-ui-toolkit-plugin: Installed: 1.3.1603+15.10.20150812-0ubuntu1 Candidate: 1.3.1603+15.10.20150812-0ubuntu1 Version table: *** 1.3.1603+15.10.20150812-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ wily/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1489322/+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 1489037] [NEW] Change defaut alarm sound to "Alarm clock.ogg"
Public bug reported: With OTA-6 (as per bug 1354370), the default alarm sound has been changed from "Suru arpeggio.ogg" to "Alarm clock.ogg". Indicator- datetime will have to set this as default on its end. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1489037 Title: Change defaut alarm sound to "Alarm clock.ogg" Status in indicator-datetime package in Ubuntu: New Bug description: With OTA-6 (as per bug 1354370), the default alarm sound has been changed from "Suru arpeggio.ogg" to "Alarm clock.ogg". Indicator- datetime will have to set this as default on its end. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1489037/+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 1354370] Re: [Alarm][UX] default sound for alarm doesn't get its job done
** Changed in: ubuntu-ux 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-touch-sounds in Ubuntu. https://bugs.launchpad.net/bugs/1354370 Title: [Alarm][UX] default sound for alarm doesn't get its job done Status in clock-app: Invalid Status in Ubuntu Clock App: Fix Committed Status in Ubuntu UX: Fix Committed Status in ubuntu-touch-sounds package in Ubuntu: Fix Released Bug description: While the default sound for alarms is a nice sound, it's not really suited for an alarm. It's way too low and soft. I mostly don't even hear it when I'm awake and there's not much chance this sound would wake me up from sleeping. IMO it should be something a bit more aggressive. To manage notifications about this bug go to: https://bugs.launchpad.net/clock-app/+bug/1354370/+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 1475223] Re: Crash during Clock application start on Desktop
** Changed in: ubuntu-clock-app Importance: Undecided => High ** Changed in: ubuntu-clock-app 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/1475223 Title: Crash during Clock application start on Desktop Status in Ubuntu Clock App: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Statistically once per 8 Clock runs, the application is crashing with following BackTrace: #0 0x754539fc in g_type_check_instance (type_instance=type_instance@entry=0xf1a0b0) at /build/buildd/glib2.0-2.44.1/./gobject/gtype.c:4136 #1 0x754496fe in g_signal_emit_valist (instance=0xf1a0b0, signal_id=289, detail=0, var_args=var_args@entry=0x7fffd250) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3090 #2 0x7544a8ff in g_signal_emit (instance=, signal_id=, detail=) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361 #3 0x7fffbe19e271 in () at /usr/lib/x86_64-linux-gnu/libgeoclue.so.0 #4 0x7fffdfb0ef3c in marshal_dbus_message_to_g_marshaller (closure=0x1520db0, return_value=0x0, n_param_values=, param_values=, invocation_hint=0x7fffd530, marshal_data=0x0) at dbus-gproxy.c:1736 #8 0x7544a8ff in (instance=instance@entry=0xf0f780, signal_id=, detail=) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361 #5 0x754302d5 in g_closure_invoke (closure=0x1520db0, return_value=0x0, n_param_values=3, param_values=0x7fffd590, invocation_hint=0x7fffd530) at /build/buildd/glib2.0-2.44.1/./gobject/gclosure.c:768 #6 0x7544203c in signal_emit_unlocked_R (node=node@entry=0x151e740, detail=detail@entry=1533, instance=instance@entry=0xf0f780, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd590) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3549 #7 0x7544a698 in g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fffd740) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3305 #9 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (message=0x5307c0, proxy=0xf0f780 [DBusGProxy]) at dbus-gproxy.c:1789 #10 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (connection=, message=0x5307c0, user_data=0xf1f540) at dbus-gproxy.c:1356 #11 0x7fffec3e21d1 in dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #12 0x7fffdfb095d5 in message_queue_dispatch (source=, callback=, user_data=) at dbus-gmain.c:90 #13 0x7515ac3d in g_main_context_dispatch (context=0x7fffe40016f0) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3122 #14 0x7515ac3d in g_main_context_dispatch (context=context@entry=0x7fffe40016f0) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #15 0x7515af20 in g_main_context_iterate (context=context@entry=0x7fffe40016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3808 ---Type to continue, or q to quit--- #16 0x7515afcc in g_main_context_iteration (context=0x7fffe40016f0, may_block=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869 #17 0x767bcc57 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x767613e2 in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7676902c in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00404098 in () #21 0x75ac1a40 in __libc_start_main (main= 0x4037d0, argc=4, argv=0x7fffdf38, init=, fini=, rtld_fini=, stack_end=0x7fffdf28) at libc-start.c:289 #22 0x004058b9 in () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+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 1297357] Re: Click App Preview of the core-apps are of low quality
** Changed in: ubuntu-clock-app Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1297357 Title: Click App Preview of the core-apps are of low quality Status in Dropping Letters: Triaged Status in Ubuntu Music App: Triaged Status in notes-app: New Status in Sudoku App: Triaged Status in Ubuntu Calculator App: Fix Released Status in Ubuntu Calendar App: Triaged Status in Ubuntu Clock App: Fix Released Status in Ubuntu File Manager App: Triaged Status in Ubuntu Shorts App: Triaged Status in Ubuntu Weather App: Triaged Status in friends-app package in Ubuntu: Won't Fix Status in gallery-app package in Ubuntu: New Bug description: On a Ubuntu Touch phone, navigate to the app lens and long-press any core app to see its application preview. Considering that the core apps come preinstalled on the phone, they need to provide better app previews. You will notice that the following mistakes, - Many times the short and long description are exactly the same leading to duplicate sentences being shown - App Descriptions are too small - Screenshots need to be updated with the latest designs or completely missing (in case of gallery-app, friends, system settings) Clock App - Application tagline and description are duplicated. The description can be a bit more elaborate. Friends App - Missing Screenshots and an app description. Only the tagline is shown - No developer team name/author mentioned Shorts App - Tagline and app description start with same phrase. This could be improved better. The app description could perhaps elaborate on the features that shorts app provides like the ability to add remote feeds etc. Calculator App - Tagline and app description are duplicated - Screenshot #2 doesn't look good. For instance, it could show the names of the calculation instead of showing an empty label Music App - Application tagline and description are duplicated - Screenshots needs to be updated with the current design Gallery App - No screenshots provided Camera App - No screenshots. What I mean here is that perhaps a screenshots of the interface with buttons can be shown. Media Player App - No screenshots, description or tagline - Developer name/author also missing System Settings - Tagline and app description missing - Developer name/author missing Dialer App, Messaging App, Contacts App, Browser App - App description missing - Developer team name/author missing To manage notifications about this bug go to: https://bugs.launchpad.net/dropping-letters/+bug/1297357/+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 1486008] Re: leading actions width is too small making it very difficult to press on Nexus 4 (mako)
Indeed it is not a design issue, more a implementation/environment issue specific to Nexus 4. -- 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/1486008 Title: leading actions width is too small making it very difficult to press on Nexus 4 (mako) Status in Ubuntu UX: Incomplete Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Since a recent update to the ListItem leading actions in Ubuntu.Components 1.2, where the width of the action was clamped, the width is too small to press comfortably on a phone resulting in it missing 9 out of 10 tries. It affects the usability of the action and may be become a release blocker for apps that have recently switched over to the new list items. Sample App import QtQuick 2.4 import Ubuntu.Components 1.2 MainView { applicationName: "testdelete.nik90" width: units.gu(100) height: units.gu(75) Page { title: "Swipe to Delete" ListItem { id: listItem anchors.top: parent.top Label { text: "Swipe me right to delete this listitem" wrapMode: Text.WordWrap anchors { left: parent.left; leftMargin: units.gu(2); right: parent.right; verticalCenter: parent.verticalCenter } } leadingActions: ListItemActions { actions: [ Action { iconName: "delete" onTriggered: listItem.destroy() } ] } } } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1486008/+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 1486008] Re: leading actions width is too small making it very difficult to press on Nexus 4 (mako)
I have attached the screenshot as requested. Visually the leading edge action width looks reasonable. However for some reason, this bug is only reproducible on a Nexus 4 (Mako). There were others who confirmed this wasn't an issue on their BQ devices. ** Summary changed: - leading actions width is too small making it very difficult to press + leading actions width is too small making it very difficult to press on Nexus 4 (mako) ** Attachment added: "bug.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1486008/+attachment/4449908/+files/bug.png -- 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/1486008 Title: leading actions width is too small making it very difficult to press on Nexus 4 (mako) Status in Ubuntu UX: Incomplete Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Since a recent update to the ListItem leading actions in Ubuntu.Components 1.2, where the width of the action was clamped, the width is too small to press comfortably on a phone resulting in it missing 9 out of 10 tries. It affects the usability of the action and may be become a release blocker for apps that have recently switched over to the new list items. Sample App import QtQuick 2.4 import Ubuntu.Components 1.2 MainView { applicationName: "testdelete.nik90" width: units.gu(100) height: units.gu(75) Page { title: "Swipe to Delete" ListItem { id: listItem anchors.top: parent.top Label { text: "Swipe me right to delete this listitem" wrapMode: Text.WordWrap anchors { left: parent.left; leftMargin: units.gu(2); right: parent.right; verticalCenter: parent.verticalCenter } } leadingActions: ListItemActions { actions: [ Action { iconName: "delete" onTriggered: listItem.destroy() } ] } } } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1486008/+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 1486008] [NEW] leading actions width is too small making it very difficult to press
Public bug reported: Since a recent update to the ListItem leading actions in Ubuntu.Components 1.2, where the width of the action was clamped, the width is too small to press comfortably on a phone resulting in it missing 9 out of 10 tries. It affects the usability of the action and may be become a release blocker for apps that have recently switched over to the new list items. Sample App import QtQuick 2.4 import Ubuntu.Components 1.2 MainView { applicationName: "testdelete.nik90" width: units.gu(100) height: units.gu(75) Page { title: "Swipe to Delete" ListItem { id: listItem anchors.top: parent.top Label { text: "Swipe me right to delete this listitem" wrapMode: Text.WordWrap anchors { left: parent.left; leftMargin: units.gu(2); right: parent.right; verticalCenter: parent.verticalCenter } } leadingActions: ListItemActions { actions: [ Action { iconName: "delete" onTriggered: listItem.destroy() } ] } } } } ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1486008 Title: leading actions width is too small making it very difficult to press Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Since a recent update to the ListItem leading actions in Ubuntu.Components 1.2, where the width of the action was clamped, the width is too small to press comfortably on a phone resulting in it missing 9 out of 10 tries. It affects the usability of the action and may be become a release blocker for apps that have recently switched over to the new list items. Sample App import QtQuick 2.4 import Ubuntu.Components 1.2 MainView { applicationName: "testdelete.nik90" width: units.gu(100) height: units.gu(75) Page { title: "Swipe to Delete" ListItem { id: listItem anchors.top: parent.top Label { text: "Swipe me right to delete this listitem" wrapMode: Text.WordWrap anchors { left: parent.left; leftMargin: units.gu(2); right: parent.right; verticalCenter: parent.verticalCenter } } leadingActions: ListItemActions { actions: [ Action { iconName: "delete" onTriggered: listItem.destroy() } ] } } } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1486008/+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 1411187] Re: [clock] Add option to not have snooze
** Changed in: ubuntu-clock-app Milestone: 3.5 => 3.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1411187 Title: [clock] Add option to not have snooze Status in Ubuntu Clock App: Triaged Status in Ubuntu UX: Fix Committed Status in unity-notifications: New Status in indicator-datetime package in Ubuntu: Triaged Status in unity-notifications package in Ubuntu: New Bug description: Snooze is evil. I suggest to add to snooze dropdown menu in the option the voice "No snooze" or something like this Documentation: https://docs.google.com/a/canonical.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g34303b1ce_2_11 https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g36c1a0cdd_010 https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit https://developer.gnome.org/notification-spec/ [UX Comment] As it seems unlikely that we will be able to implement snooze on/off & snooze duration for individual alarms, but do have an application-wide setting that allows snooze duration to be set (but not disabled), I'd recommend the options relating to snooze in application settings be changed to the following: - No snooze - 5 minutes - 10 minutes - 15 minutes This way the list is still short (four options, as it is currently) but the options provided are likely to be more useful (current 2 minute snooze doesn't seem very useful, nor does the difference between 4 mins and 5 min snooze periods). [UX Comment 2] Additionally, notifications for snoozing alarms should come in two forms: 1. With the options 'OK' (ceases alarm) and 'Snooze' (sets the alarm to the snooze period elected by the user) 2. With the option 'OK' (ceases the alarm) when snooze is not enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411187/+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 1362964] Re: Clock icon almost always shows the wrong time
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1362964 Title: Clock icon almost always shows the wrong time Status in Ubuntu Clock App: Triaged Status in unity8 package in Ubuntu: New Bug description: Problem occurs with: Ubuntu 14.10 r203 Does not occur with: iOS, Windows Phone 1. In the Launcher or Dash, find the Clock app. What you see: The icon always shows a time approximately 10:06:18, regardless of the actual time. What you should see: The icon shows the current time, or no time at all. The equivalent for the Calendar is bug 1362962. This depends on bug 1453795 for Unity letting an app change its own icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362964/+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 1475081] Re: Alarm sounds during call
** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-clock-app Milestone: None => 3.x.backlog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1475081 Title: Alarm sounds during call Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: New Bug description: If you have set an alarm and you are on a call when the alarm is due to ring, it does ring out (through the speakers). You should get some kind of 'bleep' through the earpiece instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475081/+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 1466820] Re: Notification by sound or vibration doesn't work
Is this still an issue? ** Changed in: ubuntu-clock-app Status: New => Incomplete ** Changed in: indicator-datetime (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1466820 Title: Notification by sound or vibration doesn't work Status in Ubuntu Clock App: Incomplete Status in indicator-datetime package in Ubuntu: Incomplete Bug description: Since I updated to the newest version of the alarm-clock-app, there is no notification by sound or vibration anymore. But the screen notification is displayed. * I deleted all the alarms and recreated them * I tried silent and non silent mode and different volume setting * I even tried it with headphones and without As suggested I attached the files in .local/share/evolution/tasks Device: BQ Aquarius E4.5 Channel: stable OS: 15.04 r23 ubuntu-clock-app 3.3.280.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1466820/+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 1466002] Re: Clock display not using the same format as the indicator
** Changed in: ubuntu-clock-app Milestone: None => 3.x.backlog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1466002 Title: Clock display not using the same format as the indicator Status in Indicator Date and Time: New Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Triaged Bug description: Environment: mako on latest rc proposed (17.06.2015) Reproduce: 1. Set Norwegian locale 2. Open Clock App What happens: Clock app says "11.06" and the indicator says "11:06". What should have happened: Both should use the same format. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1466002/+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 1475223] Re: Crash during Clock application start on Desktop
** Changed in: ubuntu-clock-app Milestone: None => 3.x.backlog -- 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/1475223 Title: Crash during Clock application start on Desktop Status in Ubuntu Clock App: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Statistically once per 8 Clock runs, the application is crashing with following BackTrace: #0 0x754539fc in g_type_check_instance (type_instance=type_instance@entry=0xf1a0b0) at /build/buildd/glib2.0-2.44.1/./gobject/gtype.c:4136 #1 0x754496fe in g_signal_emit_valist (instance=0xf1a0b0, signal_id=289, detail=0, var_args=var_args@entry=0x7fffd250) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3090 #2 0x7544a8ff in g_signal_emit (instance=, signal_id=, detail=) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361 #3 0x7fffbe19e271 in () at /usr/lib/x86_64-linux-gnu/libgeoclue.so.0 #4 0x7fffdfb0ef3c in marshal_dbus_message_to_g_marshaller (closure=0x1520db0, return_value=0x0, n_param_values=, param_values=, invocation_hint=0x7fffd530, marshal_data=0x0) at dbus-gproxy.c:1736 #8 0x7544a8ff in (instance=instance@entry=0xf0f780, signal_id=, detail=) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361 #5 0x754302d5 in g_closure_invoke (closure=0x1520db0, return_value=0x0, n_param_values=3, param_values=0x7fffd590, invocation_hint=0x7fffd530) at /build/buildd/glib2.0-2.44.1/./gobject/gclosure.c:768 #6 0x7544203c in signal_emit_unlocked_R (node=node@entry=0x151e740, detail=detail@entry=1533, instance=instance@entry=0xf0f780, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd590) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3549 #7 0x7544a698 in g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fffd740) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3305 #9 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (message=0x5307c0, proxy=0xf0f780 [DBusGProxy]) at dbus-gproxy.c:1789 #10 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (connection=, message=0x5307c0, user_data=0xf1f540) at dbus-gproxy.c:1356 #11 0x7fffec3e21d1 in dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #12 0x7fffdfb095d5 in message_queue_dispatch (source=, callback=, user_data=) at dbus-gmain.c:90 #13 0x7515ac3d in g_main_context_dispatch (context=0x7fffe40016f0) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3122 #14 0x7515ac3d in g_main_context_dispatch (context=context@entry=0x7fffe40016f0) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #15 0x7515af20 in g_main_context_iterate (context=context@entry=0x7fffe40016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3808 ---Type to continue, or q to quit--- #16 0x7515afcc in g_main_context_iteration (context=0x7fffe40016f0, may_block=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869 #17 0x767bcc57 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x767613e2 in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7676902c in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00404098 in () #21 0x75ac1a40 in __libc_start_main (main= 0x4037d0, argc=4, argv=0x7fffdf38, init=, fini=, rtld_fini=, stack_end=0x7fffdf28) at libc-start.c:289 #22 0x004058b9 in () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+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 1354370] Re: [Alarm][UX] default sound for alarm doesn't get its job done
** Changed in: ubuntu-clock-app 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-touch-sounds in Ubuntu. https://bugs.launchpad.net/bugs/1354370 Title: [Alarm][UX] default sound for alarm doesn't get its job done Status in clock-app: Invalid Status in Ubuntu Clock App: Fix Committed Status in Ubuntu UX: In Progress Status in ubuntu-touch-sounds package in Ubuntu: Fix Released Bug description: While the default sound for alarms is a nice sound, it's not really suited for an alarm. It's way too low and soft. I mostly don't even hear it when I'm awake and there's not much chance this sound would wake me up from sleeping. IMO it should be something a bit more aggressive. To manage notifications about this bug go to: https://bugs.launchpad.net/clock-app/+bug/1354370/+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 1484736] [NEW] Locked & Hidden Page header is shown briefly when returning to the page
Public bug reported: While playing with U.C 1.3, I noticed the following bug with page headers. Assume you have a pagestack with 2 pages, rootPage and secondPage. The rootPage header is locked and not visible. When you push secondPage and then pop it, you will briefly notice the rootPage header being shown which then slides out of view. This is rather every time the hide animation is shown. Affects ubuntu-clock-app which hides & locks the page header. Here is a sample app to reproduce the bug: import QtQuick 2.4 import Ubuntu.Components 1.3 MainView { applicationName: "testheader.nik90" width: units.gu(100) height: units.gu(75) PageStack { id: mainStack Component.onCompleted: push(rootPage) Page { id: rootPage head { visible: false locked: true } Column { anchors { left: parent.left; right: parent.right; top: parent.top; margins: units.gu(2) } spacing: units.gu(2) Label { width: parent.width wrapMode: Text.WordWrap text: "Steps to reproduce bug: 1. Press \"Click Me\" button to push second page. 2. Press \"Back\" header button to go back to the root page 3. Notice how the root page header is shown briefly and then slides out of sight" } Button { text: "Click Me" color: UbuntuColors.green anchors.horizontalCenter: parent.horizontalCenter onClicked: mainStack.push(secondPage) } } } Page { id: secondPage title: "Second Page" visible: false } } } ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1484736 Title: Locked & Hidden Page header is shown briefly when returning to the page Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: While playing with U.C 1.3, I noticed the following bug with page headers. Assume you have a pagestack with 2 pages, rootPage and secondPage. The rootPage header is locked and not visible. When you push secondPage and then pop it, you will briefly notice the rootPage header being shown which then slides out of view. This is rather every time the hide animation is shown. Affects ubuntu-clock-app which hides & locks the page header. Here is a sample app to reproduce the bug: import QtQuick 2.4 import Ubuntu.Components 1.3 MainView { applicationName: "testheader.nik90" width: units.gu(100) height: units.gu(75) PageStack { id: mainStack Component.onCompleted: push(rootPage) Page { id: rootPage head { visible: false locked: true } Column { anchors { left: parent.left; right: parent.right; top: parent.top; margins: units.gu(2) } spacing: units.gu(2) Label { width: parent.width wrapMode: Text.WordWrap text: "Steps to reproduce bug: 1. Press \"Click Me\" button to push second page. 2. Press \"Back\" header button to go back to the root page 3. Notice how the root page header is shown briefly and then slides out of sight" } Button { text: "Click Me" color: UbuntuColors.green anchors.horizontalCenter: parent.horizontalCenter onClicked: mainStack.push(secondPage) } } } Page { id: secondPage title: "Second Page" visible: false } } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1484736/+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 1427566] Re: [Clock][UX] Add timers functionality
** Changed in: ubuntu-clock-app Milestone: 3.5 => 3.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1427566 Title: [Clock][UX] Add timers functionality Status in Indicator Date and Time: New Status in Ubuntu Clock App: Triaged Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I'm greatly missing timers from the clock app. In Android I use them all the time for fixed time periods (laundry/bread/cooking/tea is ready, etc.), and it's rather inconvenient to have to create a gazillion alarms at a fixed time for these. I'm not sure why they got removed, but could we have them back please? Thanks for considering! Before we will implement this we need to fix: https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1480200 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+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 1354370] Re: [Alarm][UX] default sound for alarm doesn't get its job done
** Branch linked: lp:~nik90/ubuntu-clock-app/update-default-alarm-sound -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-sounds in Ubuntu. https://bugs.launchpad.net/bugs/1354370 Title: [Alarm][UX] default sound for alarm doesn't get its job done Status in clock-app: Invalid Status in Ubuntu Clock App: In Progress Status in Ubuntu UX: In Progress Status in ubuntu-touch-sounds package in Ubuntu: Fix Released Bug description: While the default sound for alarms is a nice sound, it's not really suited for an alarm. It's way too low and soft. I mostly don't even hear it when I'm awake and there's not much chance this sound would wake me up from sleeping. IMO it should be something a bit more aggressive. To manage notifications about this bug go to: https://bugs.launchpad.net/clock-app/+bug/1354370/+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 1354370] Re: [Alarm][UX] default sound for alarm doesn't get its job done
Adding ubuntu-clock-app project as the clock app needs to set the newly added sounds as default. ** Also affects: ubuntu-clock-app Importance: Undecided Status: New ** Changed in: ubuntu-clock-app Milestone: None => 3.5 ** Changed in: ubuntu-clock-app Importance: Undecided => Medium ** Changed in: ubuntu-clock-app Assignee: (unassigned) => Nekhelesh Ramananthan (nik90) ** Changed in: ubuntu-clock-app Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-sounds in Ubuntu. https://bugs.launchpad.net/bugs/1354370 Title: [Alarm][UX] default sound for alarm doesn't get its job done Status in clock-app: Invalid Status in Ubuntu Clock App: In Progress Status in Ubuntu UX: In Progress Status in ubuntu-touch-sounds package in Ubuntu: Fix Released Bug description: While the default sound for alarms is a nice sound, it's not really suited for an alarm. It's way too low and soft. I mostly don't even hear it when I'm awake and there's not much chance this sound would wake me up from sleeping. IMO it should be something a bit more aggressive. To manage notifications about this bug go to: https://bugs.launchpad.net/clock-app/+bug/1354370/+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 1408015] Re: [sdk][UX] Confirmation in the header bar confusing
** Description changed: Imagine a form of some sort, you fill a few fields of data top-down, and at the end of it you need to tap in the header at the top to save/confirm. Pair that with the header going off-screen to leave more screen for the content, you have to pull the header in first (and you need to know that's where the button will be). An example of this behaviour is the calendar app when adding/editing an event. One other example (although that could be improved easily by auto-saving the new note as soon as it's edited) is the Quick Memo app, where when you create a note in the first place you need to tap the ✓ icon, but when you're editing, it's all auto-saved and you need to tap 〈 to go back to the list of notes. I feel like we need to at least come up with clear guidance on what belongs in the header, and where a footer with buttons should be used (we have a way to stick something on top of the keyboard after all¹). http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView /#anchorToKeyboard-prop ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 17:03:54 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) --- UX comment & resolution -- - The back button in the header should never be used as a confirmation but can mean CANCEL and not just BACK. + The back button in the header should never be used as a confirmation but can mean CANCEL and not just BACK. If an action or any alterations within the content/screen have to be confirmed/saved then it requires a visible call to action. This call to action sits by default in the header unless differently specified by designer/developer. In all here described cases the UX can be improved easily by adding clarity to the UI and sometimes just adding a call to action. The header can be fixed or can go off-screen the specification for that lies with the designer/developer. This means if I have an important action in the header which I want to present to the user all the time, then the header stays fixed, even if the content is scrolled. - Calendar app: - When creating a new alarm by swiping from the bottom of the screen, the tick (confirmation) icon should be disabled. Only after interacting with the screen, by changing one of the parameters for example, the tick should be enabled. This will signal to user that there was a change and this needs to be confirmed. Even more informative is a simple word instead of the tick: SAVE. The SAVE option is a new addition to the header and wasn't available so far. + Clock app: + When creating a new alarm by swiping from the bottom of the screen, the tick (confirmation) icon should be disabled. Only after interacting with the screen, by changing one of the parameters for example, the tick should be enabled. This will signal to user that there was a change and this needs to be confirmed. Even more informative is a simple word instead of the tick: SAVE. The SAVE option is a new addition to the header and wasn't available so far. This concept is already documented in the UI - Toolkit spec which is at the bottom of this post. If user taps back before saving then the alarm won't be created. Additionally there can be visual feedback by adding the "feedback bubble" to the UI. If the user taps back before saving the feedback bubble states, e.g. "Alarm not saved". If the tick icon is tapped, it can state "Alarm saved" (see Notification spec). In the Repeat section the select all icon has to move one to the left and a tick or "save added". The behaviour will then follow as described above. Note app: - There is nothing wrong with the note app approach but it is a custom made behaviour which is up to the developer. This person decided not to use our pattern and include a tick or SAVE into the header. There are many note taking apps on iOS which are not using their patterns either. This doesn't mean they are bad, they just work differently. + There is nothing wrong with the note app approach but it is a custom made behaviour which is up to the developer. This person decided not to use our pattern and include a tick or SAVE into the header. There are many note taking apps on iOS which are not using their patterns either. This doesn't mean they are bad, they just work differently. While it is ok to use a "Send Order" or a NEXT at the end of a form, for some instances and apps it won't be efficient. This means < CANCEL/BACK and CONFIRM (tick/save/done) can sit in the header but it is not possible to control
[Touch-packages] [Bug 1350891] Re: [Scopes][UX] Suru Background should scroll
** Changed in: ubuntu-clock-app Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1350891 Title: [Scopes][UX] Suru Background should scroll Status in Canonical System Image: Invalid Status in Ubuntu Clock App: Invalid Status in Ubuntu UX: Fix Released Status in unity8 package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: Invalid Bug description: On the dash, the Suru paper folds stays fixed at the bottom, while it should rather scroll away. We should also 'tile' the background, so the paper fold is displayed again after scrolling a certain amount of vertical space. -- Desired resolution: Background must be fixed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1350891/+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 1408015] Re: [sdk][UX] Confirmation in the header bar confusing
** Changed in: ubuntu-clock-app Milestone: 3.x.backlog => 3.5 ** Changed in: ubuntu-clock-app Assignee: (unassigned) => Nekhelesh Ramananthan (nik90) ** Changed in: ubuntu-clock-app Status: Incomplete => 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/1408015 Title: [sdk][UX] Confirmation in the header bar confusing Status in Quick Memo: New Status in Ubuntu Calendar App: New Status in Ubuntu Clock App: In Progress Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Imagine a form of some sort, you fill a few fields of data top-down, and at the end of it you need to tap in the header at the top to save/confirm. Pair that with the header going off-screen to leave more screen for the content, you have to pull the header in first (and you need to know that's where the button will be). An example of this behaviour is the calendar app when adding/editing an event. One other example (although that could be improved easily by auto-saving the new note as soon as it's edited) is the Quick Memo app, where when you create a note in the first place you need to tap the ✓ icon, but when you're editing, it's all auto-saved and you need to tap 〈 to go back to the list of notes. I feel like we need to at least come up with clear guidance on what belongs in the header, and where a footer with buttons should be used (we have a way to stick something on top of the keyboard after all¹). http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView /#anchorToKeyboard-prop ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 17:03:54 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) --- UX comment & resolution -- The back button in the header should never be used as a confirmation but can mean CANCEL and not just BACK. If an action or any alterations within the content/screen have to be confirmed/saved then it requires a visible call to action. This call to action sits by default in the header unless differently specified by designer/developer. In all here described cases the UX can be improved easily by adding clarity to the UI and sometimes just adding a call to action. The header can be fixed or can go off-screen the specification for that lies with the designer/developer. This means if I have an important action in the header which I want to present to the user all the time, then the header stays fixed, even if the content is scrolled. Calendar app: When creating a new alarm by swiping from the bottom of the screen, the tick (confirmation) icon should be disabled. Only after interacting with the screen, by changing one of the parameters for example, the tick should be enabled. This will signal to user that there was a change and this needs to be confirmed. Even more informative is a simple word instead of the tick: SAVE. The SAVE option is a new addition to the header and wasn't available so far. This concept is already documented in the UI - Toolkit spec which is at the bottom of this post. If user taps back before saving then the alarm won't be created. Additionally there can be visual feedback by adding the "feedback bubble" to the UI. If the user taps back before saving the feedback bubble states, e.g. "Alarm not saved". If the tick icon is tapped, it can state "Alarm saved" (see Notification spec). In the Repeat section the select all icon has to move one to the left and a tick or "save added". The behaviour will then follow as described above. Note app: There is nothing wrong with the note app approach but it is a custom made behaviour which is up to the developer. This person decided not to use our pattern and include a tick or SAVE into the header. There are many note taking apps on iOS which are not using their patterns either. This doesn't mean they are bad, they just work differently. While it is ok to use a "Send Order" or a NEXT at the end of a form, for some instances and apps it won't be efficient. This means < CANCEL/BACK and CONFIRM (tick/save/done) can sit in the header but it is not possible to control apps which don't want to user out UI- Toolkit, hence the other solutions will exist too. We are constantly improving the UI-Toolit and I will add the footer
[Touch-packages] [Bug 1482282] Re: Clock app buttons vibrate when "Other vibrations" is off
*** This bug is a duplicate of bug 1466659 *** https://bugs.launchpad.net/bugs/1466659 >From my testing, it seems QML components derived from the SDK AbstractButton [1] do not seem to obey the "Other vibrations" settings. Clock app does not have any individual settings that overrides the system's vibrate setting. In the clock app settings page, we do have a settings option called "Vibration", but thats meant for Alarms, that is when an alarms rings, a snap notification is shown along with the alarm ringtone played and vibration. That vibration is what the settings option is meant to enable/disable. Those are two different use-cases. Also the issue of AbstractButton not obeying the system "Other Vibrations" settings was reported previously at bug 1466659. As such I am marking this bug a duplicate. If you want the string "Vibration" to be changed to "Vibrate on alarm", please create a new bug report to track that issue. [1] https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.AbstractButton/ ** This bug has been marked a duplicate of bug 1466659 Disabling "Other vibrations" in Sound settings is not working as expected. -- 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/1482282 Title: Clock app buttons vibrate when "Other vibrations" is off Status in Ubuntu Clock App: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Ubuntu 15.04 r82 1. In System Settings > "Sound", turn off "Other vibrations". 2. Launch the Clock app. 3. Tap "Add City". 4. Tap the back button in the header. What happens: 3. The phone vibrates. 4. The phone vibrates. What should happen: 3. The phone doesn't vibrate. 4. The phone doesn't vibrate. This might be the result of confusion with the Clock app's "Vibration" setting. It's understandable that the Clock app might want its alarms to vibrate, but that does not mean its buttons should regardless of System Settings. Probably the setting should be relabelled "Vibrate on alarm" or similar. Separately, this is a toolkit issue. The Clock app appears to be using a standard header control, but somehow even the header's buttons are not following the "Other vibrations" setting. If following that setting is something app developers have to remember to do, inevitably sometimes they will forget. They shouldn't have to remember. [Originally mentioned by Victor Thompson in bug 1412622.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1482282/+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 1408015] Re: [sdk][UX] Confirmation in the header bar confusing
@Olga, thnx for the design resolution. I can make the above changes to the clock app to resolve the issue. The one thing I am not clear about is the "feedback bubble" that you mentioned. I looked at the Notification Spec document and the feedback bubble shown there are ones shown by Unity8 and not something I have seen apps themselves being able to show. Could you elaborate a bit more on that? -- 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/1408015 Title: [sdk][UX] Confirmation in the header bar confusing Status in Quick Memo: New Status in Ubuntu Calendar App: New Status in Ubuntu Clock App: Incomplete Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Imagine a form of some sort, you fill a few fields of data top-down, and at the end of it you need to tap in the header at the top to save/confirm. Pair that with the header going off-screen to leave more screen for the content, you have to pull the header in first (and you need to know that's where the button will be). An example of this behaviour is the calendar app when adding/editing an event. One other example (although that could be improved easily by auto-saving the new note as soon as it's edited) is the Quick Memo app, where when you create a note in the first place you need to tap the ✓ icon, but when you're editing, it's all auto-saved and you need to tap 〈 to go back to the list of notes. I feel like we need to at least come up with clear guidance on what belongs in the header, and where a footer with buttons should be used (we have a way to stick something on top of the keyboard after all¹). http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView /#anchorToKeyboard-prop ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 17:03:54 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) --- UX comment & resolution -- The back button in the header should never be used as a confirmation but can mean CANCEL and not just BACK. If an action or any alterations within the content/screen have to be confirmed/saved then it requires a visible call to action. This call to action sits by default in the header unless differently specified by designer/developer. In all here described cases the UX can be improved easily by adding clarity to the UI and sometimes just adding a call to action. The header can be fixed or can go off-screen the specification for that lies with the designer/developer. This means if I have an important action in the header which I want to present to the user all the time, then the header stays fixed, even if the content is scrolled. Calendar app: When creating a new alarm by swiping from the bottom of the screen, the tick (confirmation) icon should be disabled. Only after interacting with the screen, by changing one of the parameters for example, the tick should be enabled. This will signal to user that there was a change and this needs to be confirmed. Even more informative is a simple word instead of the tick: SAVE. The SAVE option is a new addition to the header and wasn't available so far. This concept is already documented in the UI - Toolkit spec which is at the bottom of this post. If user taps back before saving then the alarm won't be created. Additionally there can be visual feedback by adding the "feedback bubble" to the UI. If the user taps back before saving the feedback bubble states, e.g. "Alarm not saved". If the tick icon is tapped, it can state "Alarm saved" (see Notification spec). In the Repeat section the select all icon has to move one to the left and a tick or "save added". The behaviour will then follow as described above. Note app: There is nothing wrong with the note app approach but it is a custom made behaviour which is up to the developer. This person decided not to use our pattern and include a tick or SAVE into the header. There are many note taking apps on iOS which are not using their patterns either. This doesn't mean they are bad, they just work differently. While it is ok to use a "Send Order" or a NEXT at the end of a form, for some instances and apps it won't be efficient. This means < CANCEL/BACK and CONFIRM (tick/save/done) can sit in the header but it is not possible to control apps which don't want to user out UI- Toolkit, hence the other solutions will exist too. We are constantly i
[Touch-packages] [Bug 1481648] Re: [Indicators] WorldCity timezone should be shown in the datetime indicator
** Changed in: ubuntu-clock-app Importance: Undecided => Low ** Changed in: ubuntu-clock-app Status: New => Confirmed ** Changed in: ubuntu-clock-app Milestone: None => 3.x.backlog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1481648 Title: [Indicators] WorldCity timezone should be shown in the datetime indicator Status in Ubuntu Clock App: Confirmed Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Bug description: It is far easier and quicker to check the world city timezones if it were shown in the datetime indicator than from the clock app which takes a few seconds and open. Ubuntu Touch uses the indicators and scopes for quickly exposing information and the timezone info satisfies that criteria. Datetime indicator should show all the worldcity timezones that have been added in the clock app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1481648/+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 1481648] [NEW] WorldCity timezone should be shown in the datetime indicator
Public bug reported: It is far easier and quicker to check the world city timezones if it were shown in the datetime indicator than from the clock app which takes a few seconds and open. Ubuntu Touch uses the indicators and scopes for quickly exposing information and the timezone info satisfies that criteria. Datetime indicator should show all the worldcity timezones that have been added in the clock app. ** Affects: ubuntu-clock-app Importance: Undecided Status: New ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Description changed: It is far easier and quicker to check the world city timezones if it were shown in the datetime indicator than from the clock app which takes a few seconds and open. Ubuntu Touch uses the indicators and scopes for quickly exposing information and the timezone info satisfies that criteria. + + Datetime indicator should show all the worldcity timezones that have + been added in the clock app. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1481648 Title: WorldCity timezone should be shown in the datetime indicator Status in Ubuntu Clock App: New Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: It is far easier and quicker to check the world city timezones if it were shown in the datetime indicator than from the clock app which takes a few seconds and open. Ubuntu Touch uses the indicators and scopes for quickly exposing information and the timezone info satisfies that criteria. Datetime indicator should show all the worldcity timezones that have been added in the clock app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1481648/+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 1371694] Re: TimePicker behaves erratically after changing system timezone
** Also affects: ubuntu-clock-app Importance: Undecided Status: New ** Also affects: ubuntu-calendar-app Importance: Undecided Status: New ** Changed in: ubuntu-clock-app Milestone: None => 3.x.backlog ** Changed in: ubuntu-clock-app Importance: Undecided => Critical ** Changed in: ubuntu-clock-app Importance: Critical => 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/1371694 Title: TimePicker behaves erratically after changing system timezone Status in Ubuntu Calendar App: New Status in Ubuntu Clock App: New Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: import QtQuick 2.3 import Ubuntu.Components 1.1 import Ubuntu.Components.Pickers 1.0 MainView { width: units.gu(40) height: units.gu(65) applicationName: "com.ubuntu.developer.nik90.test2" Page { title: i18n.tr("DatePicker Bug") DatePicker { anchors { top: parent.top left: parent.left right: parent.right } clip: true mode: "Hours|Minutes" } } } Steps to reproduce bug: 1. Open the above sample app ^^ on the device 2. Then open the system settings app. 3. Change the timezone 4. Switch back to the sample app 5. Click on any value in the timepicker What happens: The timepicker changes the value back to some random value and behaves erratically Output log when that happens: file:///usr/lib/i386-linux-gnu/qt5/qml/Ubuntu/Components/Pickers/DatePicker.qml:389:5: QML HoursModel: Binding loop detected for property "date" file:///usr/lib/i386-linux-gnu/qt5/qml/Ubuntu/Components/Pickers/DatePicker.qml:389:5: QML HoursModel: Binding loop detected for property "date" file:///usr/lib/i386-linux-gnu/qt5/qml/Ubuntu/Components/Pickers/Picker.qml:219:9: QML Binding: Binding loop detected for property "value" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1371694/+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 1427566] Re: [Clock][UX] Add timers functionality
** Changed in: ubuntu-clock-app Milestone: 3.x.backlog => 3.5 ** Changed in: ubuntu-clock-app Status: Incomplete => Triaged ** Changed in: ubuntu-clock-app Assignee: (unassigned) => Bartosz Kosiorek (gang65) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1427566 Title: [Clock][UX] Add timers functionality Status in Indicator Date and Time: New Status in Ubuntu Clock App: Triaged Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: New Bug description: I'm greatly missing timers from the clock app. In Android I use them all the time for fixed time periods (laundry/bread/cooking/tea is ready, etc.), and it's rather inconvenient to have to create a gazillion alarms at a fixed time for these. I'm not sure why they got removed, but could we have them back please? Thanks for considering! To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+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 1429273] Re: Clock App crashes when editing an alarm on vivid
** Changed in: ubuntu-clock-app Milestone: devel => 3.4 -- 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/1429273 Title: Clock App crashes when editing an alarm on vivid Status in Canonical System Image: Fix Released Status in Ubuntu Clock App: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Vivid: New Bug description: Steps to reproduce the bug: 1. Ensure that you are on a vivid touch image 124 *and* with the final 1.2 release of UITK which can be found at https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/uitk12_final_vivid_landing/+merge/251578, 2. Open the clock app 3. Create an alarm and save it. 4. Press on the saved alarm to edit it. What happens: Clock app crashes What should happen: d'uh it shouldnt crash. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1429273/+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 1364647] Re: [Sound] Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used
** Changed in: ubuntu-clock-app Milestone: 3.x.backlog => 3.4 ** Changed in: ubuntu-clock-app Status: Opinion => Triaged ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1364647 Title: [Sound] Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used Status in Ubuntu Clock App: Triaged Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: When a bluetooth or wired headset the phone embedded speakerphone should ring anyway as you probably won't wear an headset while sleeping, while you prefer keeping your headset connected all the times. -- SOLUTION -- Calls and Alarms should *always* be played to the speaker phones, as well as in the wired/wireless headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1364647/+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