[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
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/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
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/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-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 DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1450767] Re: [clock] Snooze time more than 10 minutes
** Changed in: ubuntu-clock-app Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1450767 Title: [clock] Snooze time more than 10 minutes Status in Ubuntu Clock App: Fix Released Status in Ubuntu UX: Fix Committed Status in indicator-datetime package in Ubuntu: Invalid Bug description: Can we have snooze times that are more than 10 minutes? Perhaps full flexibility in specifying a duration (some times I like to use 15m, but I guess more than 30 or 60 minutes would be too much). https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit?pli=1#slide=id.g18895458d_024 [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). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1450767/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1411187] Re: [clock] Add option to not have snooze
** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1411187 Title: [clock] Add option to not have snooze Status in Clock application for Ubuntu devices: Triaged Status in Ubuntu UX bugs: Fix Committed Status in indicator-datetime 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 UX Solution I've added the option to turn snooze off when editing an alarm, plus I've added an option 'Don't snooze in settings' https://docs.google.com/a/canonical.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g34303b1ce_2_11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411187/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1450767] Re: [clock] Snooze time more than 10 minutes
** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1450767 Title: [clock] Snooze time more than 10 minutes Status in Clock application for Ubuntu devices: In Progress Status in Ubuntu UX bugs: Triaged Status in indicator-datetime package in Ubuntu: New Bug description: Can we have snooze times that are more than 10 minutes? Perhaps full flexibility in specifying a duration (some times I like to use 15m, but I guess more than 30 or 60 minutes would be too much). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1450767/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1466820] Re: Notification by sound or vibration doesn't work
** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1466820 Title: Notification by sound or vibration doesn't work Status in Clock application for Ubuntu devices: New Status in indicator-datetime package in Ubuntu: New 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1466002] Re: Clock display not using the same format as the indicator
** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1466002 Title: Clock display not using the same format as the indicator Status in Clock application for Ubuntu devices: New Status in indicator-datetime package in Ubuntu: New 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/ubuntu-clock-app/+bug/1466002/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1466002] Re: Clock display not using the same format as the indicator
Thanks for taking the time to report this bug report. The clock app displays the digital time following the user locale and using standard Qt.locale() functions. I would suspect indicator-datetime is at fault here. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1466002 Title: Clock display not using the same format as the indicator Status in Clock application for Ubuntu devices: New Status in indicator-datetime package in Ubuntu: New 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/ubuntu-clock-app/+bug/1466002/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1437316] Re: [Clock] Too easy to accidentally turn off the alarm instead of snoozing
Removing ubuntu-clock-app task from this bug report since the work needs to only be done in indicator-datetime. ** No longer affects: ubuntu-clock-app -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1437316 Title: [Clock] Too easy to accidentally turn off the alarm instead of snoozing Status in Ubuntu UX bugs: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Bug description: While half asleep and when I want to snooze, it's too easy to hit the wrong button and accidentally turn off the alarm instead of activating the snooze option. I expect the snooze button to be more easily available, and for the turn off button to be made harder to activate - for example with a slide or something. Other phones I've had have had the snooze button much bigger, or the snooze activate when the phone is turned over, or something like that, to assist with preventing accidental alarm switch off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1437316/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1321309] Re: [Indicators] Missed calendar or alarm events need to be properly indicated
** No longer affects: ubuntu-clock-app -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1321309 Title: [Indicators] Missed calendar or alarm events need to be properly indicated Status in The Date and Time Indicator: Confirmed Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Imagine a scenario where you have a calendar event or a clock alarm to go of at 10:00. If you get a call at the same time, then obviously the call gets the highest priority and the alarm or calendar audible notification is suppressed by the system. So a phone user can actually miss the event. This can be resolved by turning the alarm icon shown in the indicator to blue similar to messages to indicate that an alarm or event was missed by the user. --- Desired solution: The alarm icon turns its state to active like notification center/messages indicator as suggested in the bug description. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1321309/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1364568] Re: Feature: Option to have the alarm get louder as time goes on.
Removing ubuntu-clock-app as the execution of alarms is done by indicator-datetime and the implementation is localized to it. ** No longer affects: ubuntu-clock-app -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1364568 Title: Feature: Option to have the alarm get louder as time goes on. Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I know a lot of alarms start off quiet, and gradually get louder as time goes on. Might be a nice feature. The only con of this is feature creep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1364568/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456126] Re: Alarm snooze countdown is not start from the time of tapping on Snooze button
** Project changed: ubuntu-clock-app = indicator-datetime ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456126 Title: Alarm snooze countdown is not start from the time of tapping on Snooze button Status in The Date and Time Indicator: New Status in indicator-datetime package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 42 device name: arale channel: ubuntu-touch/tangxi/devel-proposed last update: 2015-05-15 04:19:20 version version: 42 version device: 1e1b1cebe8900f5b62bed050a5c23a7765e62600d394cba528169d257e6ab36c version custom: 8274419d06b4da1424e7f7339ff2f8276b38951951d8900e148a4fdfce8fba0d Steps to reproduce: 1.Launch Clock app and set Snooze time for 5 minnutes 2.Create a alarm and wait for it to trigger 3.Waiting for more than one minutes, then tap on Snooze 4.Waiting for the alarm rings again 5.Check the real time interval after tap on Snooze Expected results: The time interval is 5 minutes after the time of tapping on Snooze Actual results: The alarm snooze countdown is start from the time of alarm rings To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1456126/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456347] Re: Possibility to set the last active alarm from the quick menu
Thanks for the bug report. By the clock quick settings menu, I presume the indicator that you swipe from the top to bottom. If that's the case, let me redirect this bug report to the correct project. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New ** No longer affects: ubuntu-clock-app -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456347 Title: Possibility to set the last active alarm from the quick menu Status in Ubuntu UX bugs: New Status in indicator-datetime package in Ubuntu: New Bug description: When I set the alarm I want to do this quickly and not wait for the clock app to open. Bug 1362548 already reports this problem. A even quicker option would be to have the alarm item always in the clock quick settings menu and to be able to set the last active alarm with a simple on off switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456347/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1437316] Re: [Clock] Too easy to accidentally turn off the alarm instead of snoozing
Thanks for taking the time to report this bug. I can confirm this issue as well. Often I turn of the alarm while trying to snooze it. We need a better design for this. May be something similar to the call accepting/declining design that vivid has at the moment? ** Summary changed: - Too easy to accidentally turn off the alarm instead of snoozing + [Clock] Too easy to accidentally turn off the alarm instead of snoozing ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-clock-app Status: New = Confirmed ** Changed in: ubuntu-clock-app Importance: Undecided = Medium ** Changed in: ubuntu-clock-app Milestone: None = 3.x.backlog -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1437316 Title: [Clock] Too easy to accidentally turn off the alarm instead of snoozing Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu UX bugs: New Status in indicator-datetime package in Ubuntu: New Bug description: While half asleep and when I want to snooze, it's too easy to hit the wrong button and accidentally turn off the alarm instead of activating the snooze option. I expect the snooze button to be more easily available, and for the turn off button to be made harder to activate - for example with a slide or something. Other phones I've had have had the snooze button much bigger, or the snooze activate when the phone is turned over, or something like that, to assist with preventing accidental alarm switch off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1437316/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1427714] [NEW] Clock app requires timers support from the platform
Public bug reported: Similar to alarms, the clock app requires the platform to wake up and notify the user when a timer is complete. The clock app cannot do this by itself since it would be suspended as per the app life cycle policies. Clock App Timer design is tracked at bug 1427566. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Clock app requires SDK to expose timer API + Clock app requires timers support from the platform ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Description changed: Similar to alarms, the clock app requires the platform to wake up and notify the user when a timer is complete. The clock app cannot do this by itself since it would be suspended as per the app life cycle policies. + + Clock App Timer design is tracked at bug 1427566. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1427714 Title: Clock app requires timers support from the platform Status in indicator-datetime package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Similar to alarms, the clock app requires the platform to wake up and notify the user when a timer is complete. The clock app cannot do this by itself since it would be suspended as per the app life cycle policies. Clock App Timer design is tracked at bug 1427566. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1427714/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1427714] Re: Clock app requires timers support from the platform
Clock App Timer design is tracked at bug 1427566. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1427714 Title: Clock app requires timers support from the platform Status in indicator-datetime package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Similar to alarms, the clock app requires the platform to wake up and notify the user when a timer is complete. The clock app cannot do this by itself since it would be suspended as per the app life cycle policies. Clock App Timer design is tracked at bug 1427566. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1427714/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1426363] [NEW] I-dt should send the alarm QOrganizerItemId to the clock app when the user clicks on an alarm shown in the indicator
Public bug reported: When users press on an alarm shown in the indicator-datetime, the clock app is supposed to be open with that specific alarm details shown. However at the moment the clock app does not know which alarm was pressed. It requires i-dt to send QOrganizerItemId to the clock app when this happens. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1426363 Title: I-dt should send the alarm QOrganizerItemId to the clock app when the user clicks on an alarm shown in the indicator Status in indicator-datetime package in Ubuntu: New Bug description: When users press on an alarm shown in the indicator-datetime, the clock app is supposed to be open with that specific alarm details shown. However at the moment the clock app does not know which alarm was pressed. It requires i-dt to send QOrganizerItemId to the clock app when this happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1426363/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1364568] Re: Feature: Option to have the alarm get louder as time goes on.
** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1364568 Title: Feature: Option to have the alarm get louder as time goes on. Status in Clock application for Ubuntu devices: Confirmed Status in indicator-datetime package in Ubuntu: New Bug description: I know a lot of alarms start off quiet, and gradually get louder as time goes on. Might be a nice feature. The only con of this is feature creep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1364568/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1426519] Re: i-dt should support ical's url property for launching related apps
In the description, you mentioned that Clock-app could specify the
information it needs in the URL, then open the right page when passed
that information later. indicator-datetime would act as a simple pass-
through. Isn't it the other way around? The use case that I see is
that when the user presses on an alarm shown in i-dt, i-dt then passes
the necessary information that clock app requires to identify the alarm
chosen by the user to open it.
I would still need to discuss with zsombor as to what information is
required by the alarms API to open a specific alarm.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1426519
Title:
i-dt should support ical's url property for launching related apps
Status in Clock application for Ubuntu devices:
New
Status in indicator-datetime package in Ubuntu:
New
Status in reminders-app package in Ubuntu:
New
Status in ubuntu-calendar-app package in Ubuntu:
New
Bug description:
indicator-datetime needs a way to dispatch an arbitrary URL when a
user clicks on an ical event menuitem.
In practice, datetime currently has clock-app hardwired for
dispatching alarms (dispatch_url('appid://com.ubuntu.clock/clock
/current-user-version')) and calendar-app for everything else
(dispatch_url('appid://com.ubuntu.calendar/calendar/current-user-
version')).
There are two use cases that can be supported by datetime handling the
URL property http://www.kanzaki.com/docs/ical/url.html:
(1) Clicking on an alarm menuitem opens up clock-app to that specific
alarm, rather than to clock-app's main page. Clock-app could specify
the information it needs in the URL, then open the right page when
passed that information later. indicator-datetime would act as a
simple pass-through.
(2) non-calendar, non-alarm items such as from the reminders app as
requested by mzanetti. The pattern would be the same as clock-app:
Reminders would add whatever URL it wants, then datetime would act as
a simple pass-through. This is preferable to adding more special cases
to indicator-datetime.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1426519/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1421559] Re: Should be able to silence alarm using power button
Adding ubuntu-ux to get design opinion. Perhaps we could also add a settings option in the clock app to allow the user to decide if he would like to dismiss/snooze the alarm on pressing the power button. ** Changed in: ubuntu-clock-app Importance: Undecided = Wishlist ** Changed in: ubuntu-clock-app Status: New = Confirmed ** Changed in: ubuntu-clock-app Milestone: None = ota-2 ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1421559 Title: Should be able to silence alarm using power button Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu UX bugs: New Status in indicator-datetime package in Ubuntu: New Bug description: krillin @rtm #16 Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, press OK on alarm What should have happened: I should be able to silence the alarm using the power button—like on iOS. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class. Removing the phone from my pocket, swiping, unlocking and dismissing the alarm, always takes about 3-4 rings. Related to bug 1340329. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1421559/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered
** Changed in: ubuntu-clock-app Status: Fix Committed = Fix Released ** Changed in: ubuntu-clock-app (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1362341 Title: OneTime alarms are not automatically dismissed or delete after they are triggered Status in the base for Ubuntu mobile products: Fix Released Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Status in ubuntu-clock-app package in Ubuntu: Fix Released Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: Steps to reproduce: 1. Create a one time alarm to ring in a few minutes 2. Let the alarm ring 3. Dismiss the alarm What happens: The OneTime alarm is still shown as enabled and as a result shows the wrong status in the clock app. The alarm is no longer shown in the indicator-datetime. What should happen: The OneTime alarm is either disabled or deleted from the alarm model. The clock app cannot disable the alarm since most likely the clock app is not even open at the time the alarm is triggered. Since the alarm is no longer shown in the indicator-datetime, my intuition tells me that indicator-datetime and EDS did its job. Its now up to the SDK Alarms API to update the alarm model correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362341/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
@Andrea, considering that this is a potential security bug where a
ubuntu desktop gets unlocked on its own, wouldn't it be recommended to
issue an update asap instead of with the next SRU?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
Fix Committed
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug description:
I have a user reporting an incidence that trusty unity desktop got
unlocked on its own:
In the morning, after coming to my desk, I just pressed the space bar
on my desktop to get the monitors woken up. The monitors came up with
the locked screen and then after a while it got unlocked to my
surprise!
There was compiz crash file on his system at that time. However, I
don't have the right debug symbols to which file (or function) it
crashed into. Here is the top part of the stack trace when I ran
apport-retrace -s on his crash file:
---
--- stack trace ---
#0 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 in g_settings_backend_read (backend=optimized out,
key=key@entry=0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen,
expected_type=0x7ff1877135a0 g_variant_type_info_basic_chars,
default_value=default_value@entry=0) at
/build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
value = optimized out
#4 0x7ff17f401c7b in g_settings_read_from_backend
(settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920,
user_value_only=user_value_only@entry=0, default_value=default_value@entry=0)
at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
value = optimized out
fixup = optimized out
path = 0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen
#5 0x7ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570,
key=0x2087618 disable-lock-screen) at
/build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c
disable-lock-screen, is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0
g_variant_type_info_basic_chars, minimum = 0x0, maximum = 0x0, default_value
= 0xb9c5b30, ref_count = 0}
value = optimized out
__FUNCTION__ = g_settings_get_value
-
The top part of the trash file when viewed in TextEdit has the information
:
-
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Dec 12 10:16:52 2014
DistroRelease: Ubuntu 14.04
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1405349348
ProcCmdline: compiz
--
His system is Ubuntu trusty 14.04.1 LTS. Unity installed
7.2.3+14.04.20140826-0ubuntu1.0.1 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1321309] Re: [Indicators] Missed calendar or alarm events need to be properly indicated
** Changed in: ubuntu-clock-app Milestone: ota-1 = ota-2 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1321309 Title: [Indicators] Missed calendar or alarm events need to be properly indicated Status in The Date and Time Indicator: Confirmed Status in Clock application for Ubuntu devices: Triaged Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-datetime package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Imagine a scenario where you have a calendar event or a clock alarm to go of at 10:00. If you get a call at the same time, then obviously the call gets the highest priority and the alarm or calendar audible notification is suppressed by the system. So a phone user can actually miss the event. This can be resolved by turning the alarm icon shown in the indicator to blue similar to messages to indicate that an alarm or event was missed by the user. --- Desired solution: The alarm icon turns its state to active like notification center/messages indicator as suggested in the bug description. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1321309/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered
** Branch linked: lp:~nik90/ubuntu-clock-app/3-fix-alarm-refresh-ui -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1362341 Title: OneTime alarms are not automatically dismissed or delete after they are triggered Status in the base for Ubuntu mobile products: Fix Released Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: In Progress Status in indicator-datetime package in Ubuntu: Fix Released Status in ubuntu-clock-app package in Ubuntu: New Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: Steps to reproduce: 1. Create a one time alarm to ring in a few minutes 2. Let the alarm ring 3. Dismiss the alarm What happens: The OneTime alarm is still shown as enabled and as a result shows the wrong status in the clock app. The alarm is no longer shown in the indicator-datetime. What should happen: The OneTime alarm is either disabled or deleted from the alarm model. The clock app cannot disable the alarm since most likely the clock app is not even open at the time the alarm is triggered. Since the alarm is no longer shown in the indicator-datetime, my intuition tells me that indicator-datetime and EDS did its job. Its now up to the SDK Alarms API to update the alarm model correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362341/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1411171] Re: Repeating alarms appear disabled in clock app after it went off once
@lukasz, yeah this would also be affecting vivid. However at the moment the alarms feature in vivid is broken badly due to SDK Alarms API (alarms backend rewritten for performance and other benefits). Thereby it is difficult to identify if fixes like the above work or not. I would recommend waiting for the SDK Alarms API to settle down a bit in vivid before pushign this fix to vivid. ** Changed in: ubuntu-clock-app Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1411171 Title: Repeating alarms appear disabled in clock app after it went off once Status in the base for Ubuntu mobile products: Confirmed Status in Clock application for Ubuntu devices: Fix Released Status in indicator-datetime package in Ubuntu: In Progress Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: krillin #198 Repeating alarm is disabled after the first time it goes off. Test Case: 1. Setup a repeating alarm (everyday from Monday to Friday for example) and enable it 2. Close the clock app 3. Wait until it goes off 4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next occurrence) 5. Resume the device 6. Launch the clock app 7. Go the alarms and verify the status of the alarm Actual Result: The alarm is disabled but it shows in the indicator. The next and next-next occurrences of the alarm are scheduled correctly. Expected Result Alarm is still enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1350331] Re: Dash doesn't close when Drag and dropping from it to another window
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350331 Title: Dash doesn't close when Drag and dropping from it to another window Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open one nautilus window and another window, so that nautilus is not focused 2. Open the dash File lens (Super+F) 3. Start dragging a file from that to the nautilus launcher icon 4. Wait some delay Expected Result: 4. The dash is closed and nautilus window is focused Actual result: 4. The nautilus window is focused, but the dash is not closed [ Test Case ] See above. [ Regression Potential ] Any code change in Unity has the potential to introduce crashes in Unity. This particular fix has the potential to not close the dash after a drag-and-drop operation, which could conceivably result in a desktop lock-up requiring a restart. [ Other Info ] The Ubuntu 14.04 LTS SRU fix was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1350331/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1059275] Re: reset now deprecated, man page not updated
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1059275 Title: reset now deprecated, man page not updated Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] The manpage for the unity command reflects the actual available options. [ Test Case ] Run man unity. It should not say --reset is a valid command-line switch (option). [ Regression Potential ] This is a change to the man page. I suppose it might be a regression if the man page still does not match the option available in the 'unity' command. Not terribly serious. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1059275/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered
** Changed in: ubuntu-clock-app Status: Confirmed = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1362341 Title: OneTime alarms are not automatically dismissed or delete after they are triggered Status in the base for Ubuntu mobile products: Fix Released Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: In Progress Status in indicator-datetime package in Ubuntu: Fix Released Status in ubuntu-clock-app package in Ubuntu: New Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: Steps to reproduce: 1. Create a one time alarm to ring in a few minutes 2. Let the alarm ring 3. Dismiss the alarm What happens: The OneTime alarm is still shown as enabled and as a result shows the wrong status in the clock app. The alarm is no longer shown in the indicator-datetime. What should happen: The OneTime alarm is either disabled or deleted from the alarm model. The clock app cannot disable the alarm since most likely the clock app is not even open at the time the alarm is triggered. Since the alarm is no longer shown in the indicator-datetime, my intuition tells me that indicator-datetime and EDS did its job. Its now up to the SDK Alarms API to update the alarm model correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362341/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered
** Branch linked: lp:~nik90/ubuntu-clock-app/update-alarm-page-ui- correctly -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1362341 Title: OneTime alarms are not automatically dismissed or delete after they are triggered Status in the base for Ubuntu mobile products: Fix Released Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: In Progress Status in indicator-datetime package in Ubuntu: Fix Released Status in ubuntu-clock-app package in Ubuntu: New Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: Steps to reproduce: 1. Create a one time alarm to ring in a few minutes 2. Let the alarm ring 3. Dismiss the alarm What happens: The OneTime alarm is still shown as enabled and as a result shows the wrong status in the clock app. The alarm is no longer shown in the indicator-datetime. What should happen: The OneTime alarm is either disabled or deleted from the alarm model. The clock app cannot disable the alarm since most likely the clock app is not even open at the time the alarm is triggered. Since the alarm is no longer shown in the indicator-datetime, my intuition tells me that indicator-datetime and EDS did its job. Its now up to the SDK Alarms API to update the alarm model correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362341/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1387231] Re: [regression][clock] alarm still rings once it's been disabled or deleted
As of Ubuntu RTM r13, this bug has been fixed. Marking it as fix released. ** Changed in: ubuntu-clock-app Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1387231 Title: [regression][clock] alarm still rings once it's been disabled or deleted Status in the base for Ubuntu mobile products: Confirmed Status in Clock application for Ubuntu devices: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Bug description: (r135) Steps to reproduce: 1. Create a single type alarm to ring in the next 5 minutes. 2. Wait for the alarm to ring. 3. After dismissing the alarm, delete it from the clock app. Actual behaviour: Once the alarm's been deleted, it still rings! Expected behaviour: Once you delete the alarm, this shouldn't ring anymore. Mako, Image #5 ubuntu rtm, Steps to reproduce: 1. Create an alarm to ring in the next 5 minutes. 2. Disable the alarm after it is created. Actual Behaviour: Alarm still rings! Expected Behaviour: Once you disable an alarm, it shouldn't ring anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387231/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1411171] Re: Repeating alarm disabled after it went off once
I suspect this is a side effect that was introduced while fixing https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362341. Instead of disabling just one-time alarms after they ring, I presume indicator- datetime mistakingly disables recurring alarms as well. Clock app merely displays the EDS data and in this case it seems the EDS is being changed incorrectly. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1411171 Title: Repeating alarm disabled after it went off once Status in Clock application for Ubuntu devices: Confirmed Status in indicator-datetime package in Ubuntu: New Bug description: krillin #198 Repeating alarm is disabled after the first time it goes off. Test Case: 1. Setup a repeating alarm (everyday from Monday to Friday for example) and enable it 2. Close the clock app 3. Wait until it goes off 4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next occurrence) 5. Resume the device 6. Launch the clock app 7. Go the alarms and verify the status of the alarm Actual Result: The alarm is disabled but it shows in the indicator. The next and next-next occurrences of the alarm are scheduled correctly. Expected Result Alarm is still enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411171/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1411171] Re: Repeating alarms are disabled after it went off once
** Summary changed: - Repeating alarm disabled after it went off once + Repeating alarms are disabled after it went off once ** Changed in: ubuntu-clock-app Milestone: None = ota-1 ** Tags added: alarm ** Summary changed: - Repeating alarms are disabled after it went off once + Repeating alarms appear disabled in clock app after it went off once ** Changed in: ubuntu-clock-app Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1411171 Title: Repeating alarms appear disabled in clock app after it went off once Status in Clock application for Ubuntu devices: Confirmed Status in indicator-datetime package in Ubuntu: New Bug description: krillin #198 Repeating alarm is disabled after the first time it goes off. Test Case: 1. Setup a repeating alarm (everyday from Monday to Friday for example) and enable it 2. Close the clock app 3. Wait until it goes off 4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next occurrence) 5. Resume the device 6. Launch the clock app 7. Go the alarms and verify the status of the alarm Actual Result: The alarm is disabled but it shows in the indicator. The next and next-next occurrences of the alarm are scheduled correctly. Expected Result Alarm is still enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411171/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354498] Re: Switcher Icons emblem (count) is too small
The switcher count now scales with with icon size. Thnx for the fix. ** Tags removed: switcher verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354498 Title: Switcher Icons emblem (count) is too small Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact] The emblem size does not change as the icon size is adjusted. [ Test Case ] (1) Use the System Settings Displays Scale for menus and title bars slider to adjust the Swicther icon size. (2) Observe the size of the badge. It should scale with the icon size. [ Regression Potential Any code change to the Unity desktop shell has the potential to introduce new crashers or lockers. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time with no apparent regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1354498/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1371764] Re: Screen does not lock when an unity indicator is open
** Tags removed: verification-needed-trusty ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1371764 Title: Screen does not lock when an unity indicator is open Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Screen does not lock when a Unity indicator is open. [ Test Case ] 1. Open an unity Indicator 2. Close the laptop lid¹ Expected behavior: 3. The indicator menu should be closed and the screen is locked Actual behavior: 3. The screen is not locked with the menu visible, it gets locked as soon as the menu is closed. [1] instead of this action, you can also run the script below just before opening an indicator: sleep 3 gdbus call --session --dest com.canonical.Unity \ --object-path /com/canonical/Unity/Session \ --method com.canonical.Unity.Session.Lock [ Regression Potential ] Worst case is the lock screen still does not come up if an indicator is open, which could be a potential security problem. [ Other Info ] The fix for Ubuntu 14.04 LTS is cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regression. This is a special case of bug #49579, although this applies only to the unity indicators. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371764/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1237132] Re: Change Show Desktop icon option label when this option is in the state where it will reverse the prior show desktop action.
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1237132 Title: Change Show Desktop icon option label when this option is in the state where it will reverse the prior show desktop action. Status in Ayatana Design: Fix Committed Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] The label on the show desktop / show windows icon in the Unity Switcher does not change even when the function of the button has changed. This can be just a little bit confusing. [ Test Case ] (1) Open several applications with windows. (2) Using Alt-Tab, bring up the Switcher and keeping the Alt key depressed and using the Tab key, navigate to the leftmost icon, which should be labeled Show Desktop. Release all keys. Only the desktop should be displayed. (3) Again using Alt-Tab, navigate back to the leftmost icon. Its label should have changed to Restore Windows to indicate its changed function. [ Regression Potential ] About the worst that could happen is the incorrect label is applied to the icon in the Switcher. [ Other Info ] The Ubuntu 14.04 LTS SRU has been cherry-picked from the Ubuntu 14.04 release where it has shown to be stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1237132/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1362346] Re: Dash/Hud/Spread search bar text doesn't honour the font scaling settings
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1362346 Title: Dash/Hud/Spread search bar text doesn't honour the font scaling settings Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Text scaling value is ignored by the dash search bar and the spread filter bar. - From u-c-c → accessibility → enable Big Text option Text should size should be increased in both search bar hint and content. [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell has the potential to introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1362346/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1373695] Re: Not resizable windows can be moved by dragging them on every edge
** Tags removed: verification-needed-trusty ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373695 Title: Not resizable windows can be moved by dragging them on every edge Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open a non resizable window such as Calculator or Unity Control Center 2. Move the mouse to the edge of the window, outside the window itself but in the area that is close at least 10 px. 3. Press the mouse and start to drag Expected behavior: 4. nothing happens Actual behavior 5. the hand cursor is shown and window can be dragged around As side effect, if LIMs are enabled, moving the mouse over a window edge makes the menus to show. [ Test Case ] See above. [ Regression Potential ] Any change to the Unity desktop shell could potentially introduce new crashed or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1373695/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1385285] Re: Clicking in panel elements when the expo is active, performs to the maximized windows
Tested on trusty and bug seems to be fixed with 7.2.4. ** Tags removed: verification-needed-trusty ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1385285 Title: Clicking in panel elements when the expo is active, performs to the maximized windows Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open a maximized window (it must be focused when using global menus, not with LIMs) 2. Hit Super+s to enter in expo mode 3. Click in the panel, in different areas and you'll get: - top-left corner buttons will work (although when not visible) - grab area will make possible to grab and focus (when in LIM mode) a window [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell could potentially introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream Unity where it has been in the Ubuntu Vivid Vervet dev release form several weeks without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1385285/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1384910] Re: Switching maximized windows using the spread might lead to wrong title and positioning
This bug is fixed in 7.2.4. Thnx for the fix. ** Tags removed: verification-needed-trusty ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1384910 Title: Switching maximized windows using the spread might lead to wrong title and positioning Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open at least two maximized windows 2. Select one of the windows (last opened seems better) 3. Hit Super + W 4. Start writing to select the other(s) window opened 5. Select it, hitting enter. The title will be wrong (the one of the previous title) while the window buttons will be in the wrong position (see attached sreenshot, in LIM mode, or empty panel otherwise). [ Test Case ] See above. [ Regression Potential ] Any change to the Unity desktop shell could potentially introducer a new crash or lockup. [ Additional Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream Unity where it has been included in the Ubuntu Vivid Vervet dev release for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1384910/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1383468] Re: Windows in non-focused workspaces have not decorations in expo
This bug does seem to be fixed with Unity 7.2.4 proposed update. However it introduces a visual regression that has been reported at https://bugs.launchpad.net/unity/+bug/1411041. I have thereby marked this as verification-failed as per https://wiki.ubuntu.com/QATeam/PerformingSRUVerification. ** Tags removed: verification-needed-trusty ** Tags added: verification-failed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1383468 Title: Windows in non-focused workspaces have not decorations in expo Status in Unity: Fix Committed Status in Unity 7.2 series: New Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] 1. Open multiple windows and put them in different workspaces 2. Hit Super+S to open the expo 3. Notice that windows that are not in the focused workspaces have no decorations [ Test Case ] See above: decorations should be present with fix. [ Regression Potential ] Decorations in the Spread could be drawn incorrectly. [ Other Info ] Fix for Ubuntu 14.01 LTS was cherry-picked from upstream Unity where it has been in production testing in Ubuntu Vivid Vervet dev release for a few months with no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1383468/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1361751] Re: Launcher Icon shortcut labels don't honor text scaling
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1361751 Title: Launcher Icon shortcut labels don't honor text scaling Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Text scaling value is ignored by icons overlay text. - From u-c-c → accessibility → enable Big Text option Icons overlay text should honor that setting. [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell has the potential to introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for several weeks without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1361751/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1361713] Re: Launcher icon count does not honour the text scaling
Bug fixed in Unity 7.2.4 proposed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1361713 Title: Launcher icon count does not honour the text scaling Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Text scaling value is ignored by icon count (emblem). - From u-c-c → accessibility → enable Big Text option Icon count text should be bigger. [ Test Case ] See above. [ Regression Potential ] Any modification to Unity desktop shell sources has the potential to introduce desktop shell crashes or lockups. [ Addition Info ] The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time with no apparent regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1361713/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1332509] Re: Lockscreen misses arrow activator.
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1332509 Title: Lockscreen misses arrow activator. Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] Unity lock screen password entry should have an activator arrow like unity-greeter. [Test Case] Using the Unity desktop shell, lock the screen using Super-L (or you favourite method). When the lockscreen is displayed, a little wedgie should be displayed at the right-hand end of the password entry field, and clicking on that wedgie should perform the authentication action. [Regression Potential] This is a cosmetic change to allow click-clicky mouse interaction to work just like hitting [Enter]. The biggest potential for regression is that the asset (artwork) does not get displayed or the mouse click does not work just like hitting Enter does. [Other Info] The Ubuntu 14.04 LTS SRU was cherry-picked from Ubuntu 14.10 whwere it has been in production use for some months without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1332509/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1362162] Re: Dash buttons do not honour the text scaling
Fixed in Unity 7.2.4. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1362162 Title: Dash buttons do not honour the text scaling Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Text scaling value is ignored by dash buttons (filters and preview actions). - From u-c-c → accessibility → enable Big Text option Filters and preview action buttons should match this option. [ Test Case ] See above. [ Regression Potential ] Any code change in the Unity desktop shell has the potential to introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1362162/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1349281] Re: The exposed open windows are not displayed in the geometric order
The placement of windows in the spread is much more logical now. Thnx for the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1349281 Title: The exposed open windows are not displayed in the geometric order Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] When multiple non-maximised windows of the same program are open and one clicks on the icon of the program in the launcher, they are all shown one next to each other but in an unexpected, difficult-to- predict order: windows that are in the top-left corner of the workspace can be shown in the exposé in the right bottom position or on the left bottom corner. This makes very hard to switch between similarly looking windows like terminals. [ Test Case ] * launch four or so terminal windows; * write something different on each of them to be able to tell them apart; * move each window to a different corner, possibly using the auto-resizing feature of Unity; * click on the terminal icon in the launcher; * many terminal windows are displayed; * choose the thumbnail in the right-top corner; * very likely a window that was in another corner has been selected; * try again various time and realize how confusing this all is. [ Potential Regressions ] An invalid ordering calculation might still position windows in the exposé in unexpected ways. This is not a serious regression and has not been observed under production situations. [ Additional Info ] The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity as released in Ubuntu 14.10 where it demonstrated stability under daily use. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349281/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1398287] Re: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen
@franz, It will be released to trusty in Unity version 7.2.4 SRU as can be seen at the top of this bug report. The exact ETA is however unknown. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1398287 Title: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When the power button is pressed, the shutdown dialog will be displayed. Then clicks the 'Lock' button on the HUD and it sometimes takes about 30~60s to lock screen. This happens on many Intel-only platforms. PS: If user moves the cursor out of the dialog window after clicking the 'Lock' button, it will switch to lock screen immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398287/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1387231] Re: [regression][clock] alarm still rings once it's been disabled or deleted
** Changed in: ubuntu-clock-app Milestone: rtm = ota-1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1387231 Title: [regression][clock] alarm still rings once it's been disabled or deleted Status in Clock application for Ubuntu devices: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: (r135) Steps to reproduce: 1. Create a single type alarm to ring in the next 5 minutes. 2. Wait for the alarm to ring. 3. After dismissing the alarm, delete it from the clock app. Actual behaviour: Once the alarm's been deleted, it still rings! Expected behaviour: Once you delete the alarm, this shouldn't ring anymore. Mako, Image #5 ubuntu rtm, Steps to reproduce: 1. Create an alarm to ring in the next 5 minutes. 2. Disable the alarm after it is created. Actual Behaviour: Alarm still rings! Expected Behaviour: Once you disable an alarm, it shouldn't ring anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1387231/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1387231] Re: [clock] alarm still rings once it's been deleted
The bug about the alarm ringing even when it is disabled is a known issue which occurred due to upstream change in the Ubuntu SDK which wasn't synced yet to indicator-datetime. As a result, indicator-datetime wasn't aware that the alarm was disabled. I have informed charles about this issue and he has a branch https://code.launchpad.net/~charlesk /indicator-datetime/lp-1317861-handle-trigger-valarms-in-ical which fixes this and also a couple of other alarm related issues. I was caught by surprise when I read the alarm ringing after it was deleted. I will modify this bug report to say it rang after being disabled by the user instead. ** Summary changed: - [clock] alarm still rings once it's been deleted + [clock] alarm still rings once it's been disabled ** Changed in: ubuntu-clock-app Status: Incomplete = Confirmed ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-clock-app Milestone: None = rtm ** Changed in: ubuntu-clock-app Importance: Undecided = Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1387231 Title: [clock] alarm still rings once it's been disabled or deleted Status in Clock application for Ubuntu devices: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: (r135) Steps to reproduce: 1. Create a single type alarm to ring in the next 5 minutes. 2. Wait for the alarm to ring. 3. After dismissing the alarm, delete it from the clock app. Actual behaviour: Once the alarm's been deleted, it still rings! Expected behaviour: Once you delete the alarm, this shouldn't ring anymore. Mako, Image #5 ubuntu rtm, Steps to reproduce: 1. Create an alarm to ring in the next 5 minutes. 2. Disable the alarm after it is created. Actual Behaviour: Alarm still rings! Expected Behaviour: Once you disable an alarm, it shouldn't ring anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1387231/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1387231] Re: [clock] alarm still rings once it's been disabled
** Changed in: ubuntu-clock-app Assignee: (unassigned) = Charles Kerr (charlesk) ** Summary changed: - [clock] alarm still rings once it's been disabled + [clock] alarm still rings once it's been disabled or deleted ** Description changed: (r135) Steps to reproduce: 1. Create a single type alarm to ring in the next 5 minutes. 2. Wait for the alarm to ring. 3. After dismissing the alarm, delete it from the clock app. Actual behaviour: Once the alarm's been deleted, it still rings! Expected behaviour: Once you delete the alarm, this shouldn't ring anymore. + + + + Mako, Image #5 ubuntu rtm, + + Steps to reproduce: + + 1. Create an alarm to ring in the next 5 minutes. + 2. Disable the alarm after it is created. + + Actual Behaviour: + + Alarm still rings! + + Expected Behaviour: + + Once you disable an alarm, it shouldn't ring anymore. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1387231 Title: [clock] alarm still rings once it's been disabled or deleted Status in Clock application for Ubuntu devices: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: (r135) Steps to reproduce: 1. Create a single type alarm to ring in the next 5 minutes. 2. Wait for the alarm to ring. 3. After dismissing the alarm, delete it from the clock app. Actual behaviour: Once the alarm's been deleted, it still rings! Expected behaviour: Once you delete the alarm, this shouldn't ring anymore. Mako, Image #5 ubuntu rtm, Steps to reproduce: 1. Create an alarm to ring in the next 5 minutes. 2. Disable the alarm after it is created. Actual Behaviour: Alarm still rings! Expected Behaviour: Once you disable an alarm, it shouldn't ring anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1387231/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1387231] Re: [regression][clock] alarm still rings once it's been disabled or deleted
** Summary changed: - [clock] alarm still rings once it's been disabled or deleted + [regression][clock] alarm still rings once it's been disabled or deleted -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1387231 Title: [regression][clock] alarm still rings once it's been disabled or deleted Status in Clock application for Ubuntu devices: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: (r135) Steps to reproduce: 1. Create a single type alarm to ring in the next 5 minutes. 2. Wait for the alarm to ring. 3. After dismissing the alarm, delete it from the clock app. Actual behaviour: Once the alarm's been deleted, it still rings! Expected behaviour: Once you delete the alarm, this shouldn't ring anymore. Mako, Image #5 ubuntu rtm, Steps to reproduce: 1. Create an alarm to ring in the next 5 minutes. 2. Disable the alarm after it is created. Actual Behaviour: Alarm still rings! Expected Behaviour: Once you disable an alarm, it shouldn't ring anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1387231/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1317861] Re: Alarm icon inappropriately shown for reminders too
** Changed in: indicator-datetime (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1317861 Title: Alarm icon inappropriately shown for reminders too Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: The alarm indicator icon seems to be shown if you have any reminder set up, which basically means if you have any recurring event with a reminder, it will be shown constantly. I think the icon should only be shown when you have an alarm set up. The relevant design spec: https://wiki.ubuntu.com/TimeAndDate#Phone.2BAC8-tablet-1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 9 13:08:23 2014 SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1317861/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1337917] Re: Alarm does not ring when phone is muted
** Changed in: ubuntu-clock-app Assignee: (unassigned) = Ricardo Salveti (rsalveti) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1337917 Title: Alarm does not ring when phone is muted Status in Clock application for Ubuntu devices: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: I expect the alarm to go off even if the phone is muted. I am not sure if this is a simple fix or all the things mentioned at https://wiki.ubuntu.com/SilentMode need to be implemented first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1337917/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1321309] Re: [Indicators] Missed calendar or alarm events need to be properly indicated
** Changed in: ubuntu-clock-app Milestone: rtm = ota-1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1321309 Title: [Indicators] Missed calendar or alarm events need to be properly indicated Status in The Date and Time Indicator: Confirmed Status in Clock application for Ubuntu devices: Triaged Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in “indicator-datetime” package in Ubuntu: New Status in “ubuntu-themes” package in Ubuntu: New Bug description: Imagine a scenario where you have a calendar event or a clock alarm to go of at 10:00. If you get a call at the same time, then obviously the call gets the highest priority and the alarm or calendar audible notification is suppressed by the system. So a phone user can actually miss the event. This can be resolved by turning the alarm icon shown in the indicator to blue similar to messages to indicate that an alarm or event was missed by the user. --- Desired solution: The alarm icon turns its state to active like notification center/messages indicator as suggested in the bug description. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1321309/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1372065] Re: Alarms and calendar events are mixed in the indicator
Today I tested on ubuntu-rtm/devel-proposed image 49 and noticed the following behavior, - Enabled Alarms show up as alarms in the indicator-datetime - Disabled alarms show up as events in indicator-datetime (known issue bug 1361702) @dpm, is this what you experience as well? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1372065 Title: Alarms and calendar events are mixed in the indicator Status in The Date and Time Indicator: New Status in Calendar application for Ubuntu devices: New Status in Clock application for Ubuntu devices: New Status in “indicator-datetime” package in Ubuntu: New Bug description: See the attached screenshot. It shows the indicator displaying: - An alarm (Despertador) - Several calendar events (Daniel/David 1:1, Core apps branches review, etc.) There are several issues: - All alarms/events are listed under Clock (Rellotge). I would expect the events to be listed under the calendar entry (diumenge, 21 de setembre de 2014) - The alarm has an event icon, and upon tapping on it, it opens the calendar. Expected: alarms have an alarm icon, tapping on it opens the clock - The events have an alarm icon, and upon tapping on any of them, they open the clock. Expected: events have an event icon, tapping on them opens the calendar Using image 48 from ubuntu-rtm/devel-proposed on mako. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1372065/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1372065] Re: Alarms and calendar events are mixed in the indicator
hmm if they don't show in the indicator then the alarm won't ring. This is bad! -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1372065 Title: Alarms and calendar events are mixed in the indicator Status in The Date and Time Indicator: New Status in Calendar application for Ubuntu devices: New Status in Clock application for Ubuntu devices: New Status in “indicator-datetime” package in Ubuntu: New Bug description: See the attached screenshot. It shows the indicator displaying: - An alarm (Despertador) - Several calendar events (Daniel/David 1:1, Core apps branches review, etc.) There are several issues: - All alarms/events are listed under Clock (Rellotge). I would expect the events to be listed under the calendar entry (diumenge, 21 de setembre de 2014) - The alarm has an event icon, and upon tapping on it, it opens the calendar. Expected: alarms have an alarm icon, tapping on it opens the clock - The events have an alarm icon, and upon tapping on any of them, they open the clock. Expected: events have an event icon, tapping on them opens the calendar Using image 48 from ubuntu-rtm/devel-proposed on mako. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1372065/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1372065] Re: Alarms and calendar events are mixed in the indicator
Which channel and image did you test this on? I noticed locally that when creating events in the calendar app, they show up as alarms in the indicator. But I have never had the issue of clock alarms showing up as calendar events (nor can I reproduce it on rtm r1 mako). That has to be regression. ** Changed in: ubuntu-clock-app Status: New = Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1372065 Title: Alarms and calendar events are mixed in the indicator Status in The Date and Time Indicator: New Status in Calendar application for Ubuntu devices: New Status in Clock application for Ubuntu devices: Incomplete Status in “indicator-datetime” package in Ubuntu: New Bug description: See the attached screenshot. It shows the indicator displaying: - An alarm (Despertador) - Several calendar events (Daniel/David 1:1, Core apps branches review, etc.) There are several issues: - All alarms/events are listed under Clock (Rellotge). I would expect the events to be listed under the calendar entry (diumenge, 21 de setembre de 2014) - The alarm has an event icon, and upon tapping on it, it opens the calendar. Expected: alarms have an alarm icon, tapping on it opens the clock - The events have an alarm icon, and upon tapping on any of them, they open the clock. Expected: events have an event icon, tapping on them opens the calendar To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1372065/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1370594] Re: Alarm notifications shown do not follow design spec
** Changed in: indicator-datetime Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1370594 Title: Alarm notifications shown do not follow design spec Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: At the moment the alarm notifications look like https://imgur.com/2Fu8Cg7 while it should instead look like https://imgur.com/Y8SHGnw. The main differences include - No ubuntushape border - Ok button is coloured green To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1370594/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354400] Re: Implement Alarm Snooze functionality
** Changed in: ubuntu-clock-app Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: Fix Released Status in Ubuntu UX bugs: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1332095] Re: alarms don't update their times when the timezone changes
** Changed in: indicator-datetime Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1332095 Title: alarms don't update their times when the timezone changes Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: reported by Renato in irc. Alarms created in ubuntu-clock-app are floating, which means that if you set a 6am alarm, it should go off at 6am no matter what timezone you're in. Indicator-datetime currently doesn't update its alarm list as a result of timezone changes, which could be a problem if you've got an early appointment... To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1332095/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1364374] Re: In the alarms notification bubble there are also seconds
** Changed in: indicator-datetime Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1364374 Title: In the alarms notification bubble there are also seconds Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: When an alarm rings, in the notification bubble there is also seconds, not only hours and minutes (see screenshot). This IMO is useless, because you cannot set the seconds of the alarm, so they are always :00 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1364374/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354400] Re: Implement Alarm Snooze functionality
** Changed in: ubuntu-clock-app Status: Triaged = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: In Progress Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354400] Re: Implement Alarm Snooze functionality
** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = In Progress ** Changed in: ubuntu-clock-app Assignee: (unassigned) = Nekhelesh Ramananthan (nik90) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: Triaged Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1321309] Re: [Indicators] Missed calendar or alarm events need to be properly indicated
Here is a reply from Matthieu James, We chose to use the red icon. I pushed it in my bzr branch and requested a merge: https://code.launchpad.net/~tiheum/ubuntu-themes /suru-icons/+merge/231533. It should be available soon. So when there is a missed alarm, the red alarm icon should be shown to indicate the missed state. With that I am marking the status back to Triaged. ** Changed in: ubuntu-clock-app Status: Confirmed = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1321309 Title: [Indicators] Missed calendar or alarm events need to be properly indicated Status in The Date and Time Indicator: Confirmed Status in Clock application for Ubuntu devices: Triaged Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in “indicator-datetime” package in Ubuntu: New Status in “ubuntu-themes” package in Ubuntu: New Bug description: Imagine a scenario where you have a calendar event or a clock alarm to go of at 10:00. If you get a call at the same time, then obviously the call gets the highest priority and the alarm or calendar audible notification is suppressed by the system. So a phone user can actually miss the event. This can be resolved by turning the alarm icon shown in the indicator to blue similar to messages to indicate that an alarm or event was missed by the user. --- Desired solution: The alarm icon turns its state to active like notification center/messages indicator as suggested in the bug description. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1321309/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1350017] Re: [clock-app] There is no vibration when an alarm goes off
** Changed in: ubuntu-clock-app Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350017 Title: [clock-app] There is no vibration when an alarm goes off Status in Clock application for Ubuntu devices: Fix Released Status in Ubuntu UX bugs: Fix Committed Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: It'd be probably nice to also have vibration beside the sound alert when an alarm triggers. - Design Solution -- Giorgio Venturi updated the design spec for the clock app at [1]. The vibration will be enabled by default for all alarms. The user however will be provided a global setting to disable that if required. [1] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350017/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1318997] Re: [clock] Provide a way to change alarm sound
** Changed in: ubuntu-clock-app/reboot Status: In Progress = Fix Committed ** Changed in: ubuntu-clock-app Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1318997 Title: [clock] Provide a way to change alarm sound Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Won't Fix Status in Ubuntu Clock App reboot series: Fix Committed Status in Ubuntu UX bugs: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The alarms API provides to way to set different alarm sounds for every alarm. Let's provide that feature to the users so that they can change the alarm sound while creating an alarm. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1318997/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1350017] Re: [clock-app] There is no vibration when an alarm goes off
** Changed in: ubuntu-clock-app Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350017 Title: [clock-app] There is no vibration when an alarm goes off Status in Clock application for Ubuntu devices: Fix Committed Status in Ubuntu UX bugs: Fix Committed Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: It'd be probably nice to also have vibration beside the sound alert when an alarm triggers. - Design Solution -- Giorgio Venturi updated the design spec for the clock app at [1]. The vibration will be enabled by default for all alarms. The user however will be provided a global setting to disable that if required. [1] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350017/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354400] [NEW] Implement Alarm Snooze functionality
Public bug reported: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post-RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 ** Affects: ubuntu-clock-app Importance: Critical Status: Triaged ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: Triaged Status in “indicator-datetime” package in Ubuntu: New Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354400] Re: Implement Alarm Snooze functionality
** Description changed: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post-RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. + This will require a Go/No-Go decision from Charles Kerr regarding the + implementation in indicator-datetime since as mentioned above this will + be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: Triaged Status in “indicator-datetime” package in Ubuntu: New Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1318997] Re: [clock] Provide a way to change alarm sound
** Changed in: ubuntu-clock-app Status: New = Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1318997 Title: [clock] Provide a way to change alarm sound Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Won't Fix Status in Ubuntu Clock App reboot series: In Progress Status in Ubuntu UX bugs: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The alarms API provides to way to set different alarm sounds for every alarm. Let's provide that feature to the users so that they can change the alarm sound while creating an alarm. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1318997/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1350017] Re: [clock-app] There is no vibration when an alarm goes off
** Branch linked: lp:~nik90/ubuntu-clock-app/add-vibration-support ** Changed in: ubuntu-clock-app Status: Triaged = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350017 Title: [clock-app] There is no vibration when an alarm goes off Status in Clock application for Ubuntu devices: In Progress Status in Ubuntu UX bugs: New Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: It'd be probably nice to also have vibration beside the sound alert when an alarm triggers. - Design Solution -- Giorgio Venturi updated the design spec for the clock app at [1]. The vibration will be enabled by default for all alarms. The user however will be provided a global setting to disable that if required. [1] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350017/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1337917] Re: Alarm does not ring when phone is muted
Raising priority to critical since this is a must for RTM and missing alarms due to the phone being silent doesn't look too good. ** Changed in: ubuntu-clock-app Importance: High = Critical ** Changed in: ubuntu-clock-app Status: Confirmed = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1337917 Title: Alarm does not ring when phone is muted Status in Clock application for Ubuntu devices: Triaged Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: I expect the alarm to go off even if the phone is muted. I am not sure if this is a simple fix or all the things mentioned at https://wiki.ubuntu.com/SilentMode need to be implemented first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1337917/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1340329] Re: Phone should turn on screen and unlock it when an alarm is triggered
** Changed in: ubuntu-clock-app Status: In Progress = Fix Released ** Changed in: ubuntu-clock-app Status: Fix Released = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1340329 Title: Phone should turn on screen and unlock it when an alarm is triggered Status in Clock application for Ubuntu devices: Fix Committed Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: When an alarm is triggered, the phone screen stays turned off. It should turn on and unlock automatically so that the user can quickly dismiss the alarm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1340329/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1350426] Re: Alarm notification should be changed to an interactive notification
** Changed in: ubuntu-clock-app Assignee: (unassigned) = Charles Kerr (charlesk) ** Changed in: ubuntu-clock-app Status: Triaged = In Progress ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350426 Title: Alarm notification should be changed to an interactive notification Status in Clock application for Ubuntu devices: In Progress Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: As per the latest design spec, the snap notification that is shown when an alarm is triggered will be replaced with a interactive notification. The design spec for the interactive notification is shown at [1]. Please ensure that the strings shown in the spec are translatable. The timing of how long the notification should be shown are similar to the snap notification behavior we have atm. https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350426/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
