[Dx-packages] [Bug 1321309] Re: [Indicators] Missed calendar or alarm events need to be properly indicated
** Changed in: ubuntu-ux 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 Canonical System Image: Confirmed Status in Indicator Date and Time: Confirmed Status in Ubuntu theme: New Status in Ubuntu UX: 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. ——— UX Comment ——— I can think of two possibilities for the resolution of this bug: 1) We change the alarm icon in the status bar for alarm-missed icon (https://drive.google.com/drive/u/1/folders/0BzbnWoHmYF3ablBITVByRnpzdEk 2) Once the incoming call event has finished or the user has acted on it by answering the call, we fire a notification bubble (as well as it’s associated auditory feedback) to communicate the missed event. If the user doesn’t act on the incoming call event, the alarm goes off after incoming call timeout. --> My recommendation would be to use a combination of both. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+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 1539621] Re: Add an option to cancel pending snooze
** Changed in: ubuntu-ux Assignee: John Lea (johnlea) => James Mulholland (jamesmulholland) ** Changed in: ubuntu-ux Status: New => Triaged ** Changed in: ubuntu-ux Importance: High => Wishlist -- 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/1539621 Title: Add an option to cancel pending snooze 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 ubuntu-ui-toolkit package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: It’s happened to me a few times that my alarm wakes me up in the morning, I tap the snooze button to sleep 10 minutes more, but end up getting up before then. In that case, it would be very handy to have an option to cancel the pending snooze so that the alarm doesn’t go off again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539621/+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 1504057] Re: [indicators] Bluetooth icon should turn blue when there's traffic happening
** Changed in: ubuntu-ux Importance: High => Medium ** Changed in: indicator-bluetooth (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1504057 Title: [indicators] Bluetooth icon should turn blue when there's traffic happening Status in Canonical System Image: New Status in Ubuntu UX: Triaged Status in indicator-bluetooth package in Ubuntu: New Bug description: The Bluetooth icon in the panel is currently an outline icon when Bluetooth is turned on but nothing is connected, it will turn to the filled icon when something connects. Additionally it would be useful if the icon would turn blue when there is actual traffic happening. This is something I've been used to from previous phones and it helps greatly to identify the state of the connection. For instance, the Music player playing music to a Bluetooth headset would be immediately visible when you've put the headset away already and forgot to stop the music player. Also, it causes bug reports of failed connections to be more detailed as this gives details to the developer whether the connection failed when establishing the ACL link or if something failed after a profile has been connected already. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1504057/+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 1387691] Re: Media Player should not be visible in the app scope and launcher
** Changed in: mediaplayer-app (Ubuntu) Status: Fix Released = Triaged ** Changed in: mediaplayer-app (Ubuntu RTM) Status: Fix Released = Triaged ** Changed in: url-dispatcher (Ubuntu) Status: Fix Released = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1387691 Title: Media Player should not be visible in the app scope and launcher Status in Canonical System Image: Fix Released Status in Ubuntu UX: Fix Committed Status in mediaplayer-app package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: Triaged Status in mediaplayer-app package in Ubuntu RTM: Triaged Status in url-dispatcher package in Ubuntu RTM: Invalid Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings Update --- --- --- --- --- UX Comment: Fix appears partially released. Implemented: - Mediaplayer app not displayed in App Scope/ Ubuntu Store Not implemented: - Mediaplayer app not displayed in Launcher (still visible in launcher, can be 'pinned' to launcher, etc). - Mediaplayer displayed in Settings Update To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+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 750497] Re: Workspace switcher has no quicklist
** Also affects: ayatana-design Importance: Undecided Status: New ** No longer affects: ubuntu-ux -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/750497 Title: Workspace switcher has no quicklist Status in Ayatana Design: New Status in Unity: Incomplete Status in unity-2d: Incomplete Status in unity package in Ubuntu: Incomplete Status in unity-2d package in Ubuntu: Incomplete Bug description: Binary package hint: unity This is the only Unity launcher item with no right-click quicklist. To me it seems important to have consistency. Though of course we know that we shouldn't just add things for the sake of it. I don't know if added Switch to Workspace X options is considered a good idea? ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,regex,vpswitch,move,animation,imgpng,mousepoll,grid,unitymtgrabhandles,gnomecompat,place,workarounds,wall,wobbly,expo,ezoom,staticswitcher,session,fade,scale,unityshell] Date: Mon Apr 4 18:06:36 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110127) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to natty on 2011-03-09 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/750497/+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: [System Settings] Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used
** Summary changed: - [Sound][ux] Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used + [System Settings] Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used -- 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: [System Settings] Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used Status in Ubuntu Clock App: Incomplete 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 -- 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 1401802] Re: [Scopes] Calendar reminder notifications became queued, non-interactive and easy to miss
** Summary changed: - Calendar reminder notifications became queued, non-interactive and easy to miss + [Scopes] Calendar reminder notifications became queued, non-interactive and easy to miss -- 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/1401802 Title: [Scopes] Calendar reminder notifications became queued, non- interactive and easy to miss Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Triaged Bug description: With the recent indicator-datetime update the reminder notifications time out and are not interactive any more, meaning that: - can't dismiss (have to wait for the sound/notification to time out) - can't snooze (I know the feature didn't work, but that was a missing feature, not a thing we didn't want?) - if you missed the notification, you missed the reminder Not sure if the reason is the same, but they started queueing, too, i.e. if there's two reminders for the same time, sound will play for both (bug #1340248), but the two notifications will be shown one after another. This is a UX regression in my opinion, even if it fixes bug #1320880. There is actually no clear design for this, I'm afraid, https://sites.google.com/a/canonical.com/apps-and-platform-team/3-platform/2-notifications ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-datetime 13.10.0+15.04.20141208-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf Date: Fri Dec 12 08:59:10 2014 InstallationDate: Installed on 2014-12-12 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141212-020204) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1401802/+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 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.
** Changed in: ubuntu-ux Assignee: Paty Davila (dizzypaty) = Alex Milazzo (digitalalex) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1367818 Title: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state. Status in Canonical System Image: Fix Released Status in Ubuntu UX: Triaged Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu RTM: Fix Released Bug description: - When the sound is muted, the volume icon to the left of the volume slider should have a red / running through it. - Add an explicit Mute button to the sound indicator menu. - Pressing and holding the icon to the left of the volume slider should mute volume straight away. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+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: [Clock][ux] Should be able to silence alarm using power button
** Changed in: ubuntu-ux Assignee: Paty Davila (dizzypaty) = James Mulholland (jamesjosephmulholland) -- 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: [Clock][ux] Should be able to silence alarm using power button Status in Ubuntu Clock App: Incomplete Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed 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. On iOS and Android power button enable snooze to prevent accidential disabling alarm. 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. Also when someone forget phone in the office, then it will be no possibility to disable alarm. 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 1421696] Re: Ubuntu Phone notification: having to click on the icon is not obvious
** Changed in: ubuntu-ux Importance: Undecided = Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1421696 Title: Ubuntu Phone notification: having to click on the icon is not obvious Status in Ubuntu UX: Triaged Status in indicator-messages package in Ubuntu: Incomplete Bug description: In the BQ E4.5 Ubuntu Edition, if you got a new notification, you have to click just in the icon for going to the application. By example: You receive a Telegram message. You dragdown the status bar (green envelope) and you see the message. If you click in the notification nothing happens. You need to click in its icon. This is not intuitive. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1421696/+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
** Changed in: ubuntu-ux Assignee: Paty Davila (dizzypaty) = James Mulholland (jamesjosephmulholland) -- 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: 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 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
** Changed in: ubuntu-ux Importance: High = Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in the base for Ubuntu mobile products: New Status in The Messaging Menu: New Status in Ubuntu UX bugs: Triaged Status in indicator-messages package in Ubuntu: Confirmed Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+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 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.
** Changed in: ubuntu-ux Assignee: Matthew Paul Thomas (mpt) = Paty Davila (dizzypaty) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1367818 Title: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state. Status in the base for Ubuntu mobile products: Fix Released Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu RTM: Fix Released Bug description: - When the sound is muted, the volume icon to the left of the volume slider should have a red / running through it. - Add an explicit Mute button to the sound indicator menu. - Pressing and holding the icon to the left of the volume slider should mute volume straight away. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+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 935750] Re: [dash] Search field not common to lenses
Marking as won't fix because this bug is assigned to the Unity8 project where it is not relevant. ** Changed in: ubuntu-ux Status: Triaged = Won't Fix ** Changed in: ubuntu-ux Importance: Medium = Undecided -- 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/935750 Title: [dash] Search field not common to lenses Status in Ubuntu UX bugs: Won't Fix Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: After typing in the home lens's search field and seeing no results, I figured I was using the wrong lens so I switched to another one. Because the search field is specific to the lens, I had to retype my search terms. I didn't realize until I started this report that the home lens search would search all the lenses. (Or, I'm assuming that's what it does now, based on a different search which produced results.) - UPDATE: This is a bug for the desktop, Unity7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/935750/+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 1436351] Re: icon does not change in silent mode
** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1436351 Title: icon does not change in silent mode Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: New Status in indicator-sound package in Ubuntu: Confirmed Bug description: If I pull down on the indicator-network and check 'Silent Mode', the icon does not change. $ system-image-cli -i current build number: 214 device name: mako channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-11 22:07:13 version version: 214 version ubuntu: 20150312 version device: 20150116 version custom: mako-1.1 Bug 1367818 seems related, but is marked Fix Released. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436351/+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 1420758] Re: [Indicators] The indicator envelop icon should not change colour to green and only be present when there are new notifications.
** Changed in: ubuntu-ux Status: New = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1420758 Title: [Indicators] The indicator envelop icon should not change colour to green and only be present when there are new notifications. Status in Ubuntu UX bugs: Fix Committed Status in indicator-messages package in Ubuntu: New Bug description: Actual behaviour: - Green envelope is displayed when there are incoming notifications. - Envelope icon turns white when user sees the notification centre. - Envelope icon turns grey when there are no notifications. The presence of a grey envelope notification icon (when there are no notifications) can mislead users into thinking they have an outstanding notification. The presence of this icon (with the exception of informational icons) suggest that something is active/on or requires attention (eg. unread messages or missed calls). Users only expect to see the icon when there are incoming notifications. Expected behaviour: - Monochrome envelope icon. - The white envelope icon only appears on the status bar when new notifications arrive. - If user sees the notification centre (or acts on the notification when it arrives), the envelope icon should disappear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1420758/+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 1149495] Re: Dash home application icon is different from app-lens icon
** Description changed: In Ubuntu 13.04 daily builds, application icon in dash home which shows recently used applications is the old app icon while app-lens icon is updated to a new one, an A with a progressbar (see the screenshot attached). The home application icon should be the same. + + - + Desired resolution: + + - The icon should be the A version in both places ** Changed in: ayatana-design Assignee: (unassigned) = John Lea (johnlea) ** Changed in: ayatana-design Importance: Undecided = Medium ** Changed in: ayatana-design Status: New = Fix Committed ** Changed in: unity Status: Incomplete = Triaged ** Changed in: unity (Ubuntu) Status: Incomplete = Triaged -- 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/1149495 Title: Dash home application icon is different from app-lens icon Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: In Ubuntu 13.04 daily builds, application icon in dash home which shows recently used applications is the old app icon while app-lens icon is updated to a new one, an A with a progressbar (see the screenshot attached). The home application icon should be the same. - Desired resolution: - The icon should be the A version in both places To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1149495/+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 1149495] Re: Dash home application icon is different from app-lens icon
Description updated -- 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/1149495 Title: Dash home application icon is different from app-lens icon Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: In Ubuntu 13.04 daily builds, application icon in dash home which shows recently used applications is the old app icon while app-lens icon is updated to a new one, an A with a progressbar (see the screenshot attached). The home application icon should be the same. - Desired resolution: - The icon should be the A version in both places To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1149495/+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 1388189] Re: [Notifications] retain notifications that the user has not acted on
** Summary changed: - retain notifications that the user has not acted on + [Notifications] retain notifications that the user has not acted on -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1388189 Title: [Notifications] retain notifications that the user has not acted on Status in Ubuntu UX bugs: Triaged Status in indicator-messages package in Ubuntu: New Bug description: It would be nice if the messages I receive but have not yet acted on would persist across reboots. That way I would not forget about an important message or miss an update, or miss something if the shell restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1388189/+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 1378350] Re: [Browser] Need to allow multiple apps to handle the same url patterns
** Summary changed: - Need to allow multiple apps to handle the same url patterns + [Browser] Need to allow multiple apps to handle the same url patterns -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1378350 Title: [Browser] Need to allow multiple apps to handle the same url patterns Status in Ubuntu UX bugs: Triaged Status in url-dispatcher package in Ubuntu: Triaged Bug description: Steps: * install gmail and dekko apps Expected: * when using a mailto: URL (see bug #1351222) URL, the user should be asked which app to open (and cache the response optionally?) Current: * not sure what would happen ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1378350/+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 1373404] Re: No warning of high volume level
** Description changed: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 - For the purpose of this Decision, a ‘personal music player’ means a - portable device, that is not covered by Directive 1999/5/EC or Directive - 2006/95/EC, with headphones or earphones, used to listen to recorded, - generated or broadcasted sound. + Desired resolution: - 1. For the purpose of Article 4(1)(a) of Directive 2001/95/EC, the - safety requirement for personal music players shall be the following: - Personal music players shall be designed and manufactured in a manner - that ensures that, under reasonably foreseeable conditions of use, they - are inherently safe and do not cause hearing damage. - - 2. The requirement set out in paragraph 1 shall include in particular - the following: - - (1) Exposure to sound levels shall be time limited to avoid hearing - damage. At 80 dB(A) exposure time shall be limited to 40 hours/week, - whereas at 89 dB(A) exposure time shall be limited to 5 hours/week. For - other exposure levels a linear intra- and extrapolation applies. Account - shall be taken of the dynamic range of sound and the reasonably - foreseeable use of the products. - - (2) Personal music players shall provide adequate warnings on the risks involved in using the device and to the ways of avoiding them and information to users in cases where exposure poses a risk of hearing damage. - - - Related documents: - http://ec.europa.eu/health/opinions/en/hearing-loss-personal-music-player-mp3/ - http://europa.eu/rapid/press-release_IP-08-1492_en.htm - http://ec.europa.eu/news/environment/090928_en.htm - http://europa.eu/rapid/press-release_IP-09-1364_en.htm - - Design: - - https://wiki.ubuntu.com/Sound#limits: Whenever you are using - headphones, Ubuntu should frequently measure the volume of sound output. - Whenever it is over 47 dB(A), your quota should be reduced - accordingly... - - [Originally reported in private bug 1370591.] + - For RTM the design spec'ed in the following section of the Sound wiki + page should be implemented + https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373404 Title: No warning of high volume level Status in Sound Menu: New Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: New Status in “pulseaudio” package in Ubuntu: Triaged Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: In Progress Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1373404/+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 1260978] Re: [Greeter] should be able to control music service while greeter locked
** Summary changed: - should be able to control music service while greeter locked + [Greeter] should be able to control music service while greeter locked -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1260978 Title: [Greeter] should be able to control music service while greeter locked Status in Media Hub: New Status in Ubuntu UX bugs: Triaged Status in “indicator-sound” package in Ubuntu: Opinion Status in “ubuntu-music-app” package in Ubuntu: Opinion Status in “ubuntu-settings-components” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: Opinion Bug description: Not sure what component to file this against-- please reassign as desired. I use my phone to play music on random while I'm driving. This works great except when I want to advance or pause the song, where I have to go through the greeter first to access the player. This can either take my attention away from driving or I need to wait until the next stop light to advance the song. This is less of a concern when the greeter can just be swiped with one gesture, but is a big concern if you enable the passcode lock where you have to add the passcode to access the player. If the music is playing, the greeter should allow rudimentary manipulation of the music, eg, pause/play and forward/back. Other platforms seem to allow for this (eg android). To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1260978/+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 1358890] Re: Competing notifications when two alarms kick at the same time
** Changed in: indicator-datetime Status: Confirmed = Triaged ** Summary changed: - Competing notifications when two alarms kick at the same time + [Notifications] Competing notifications when two alarms kick at the same time -- 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/1358890 Title: [Notifications] Competing notifications when two alarms kick at the same time Status in The Date and Time Indicator: Triaged Status in Ubuntu UX bugs: Confirmed Status in “indicator-datetime” package in Ubuntu: New Bug description: A cousin of bug #1354406 Some of the early testers are hitting a use case that we didn't account for, that of multiple alarms set for the same time. Indicator-datetime currently tries to pull up notifications for, and play sounds for, both notifications. That's happening by accident and is clearly not the right approach. I can think of a couple of approaches we might take: (1) Queue the alarms such that only one triggers at a time. This has the advantage of being simple, both in concept and in code. I'm not certain this is the most user-friendly approach, as it could be frustrating have to dismiss a queue of alarms. (2) Somehow fold multiple alarms together. This has the advantage of being friendlier to the user as only a single snooze/dismiss prompt would be given. However it opens other questions, e.g. which of the alarms' sounds should play? Of these two I slghtly prefer (1) for its simplicity; however, neither of these options seems perfect and I'm hoping Design may have a better suggestion To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1358890/+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 1350952] Re: [Indicators] replace the text Empty! with something more useful
** Summary changed: - replace the text Empty! with something more useful + [Indicators] replace the text Empty! with something more useful ** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350952 Title: [Indicators] replace the text Empty! with something more useful Status in Ubuntu UX bugs: Triaged Status in “indicator-messages” package in Ubuntu: New Bug description: when clearing the menu on this indicator (and others), the text Empty! is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1350952/+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 1348538] Re: Display should come on when started charging
** Changed in: ubuntu-ux Importance: Undecided = Low ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1348538 Title: Display should come on when started charging Status in Ubuntu UX bugs: Triaged Status in “indicator-power” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “unity-system-compositor” package in Ubuntu: New Bug description: The display should be triggered to turn on for a $timeout when connected to a charger, so that users can see charging commenced. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-system-compositor (not installed) ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 25 09:45:42 2014 SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1348538/+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 1348538] Re: [power] Display should come on when started charging
** Summary changed: - Display should come on when started charging + [power] Display should come on when started charging -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1348538 Title: [power] Display should come on when started charging Status in Ubuntu UX bugs: Triaged Status in “indicator-power” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “unity-system-compositor” package in Ubuntu: New Bug description: The display should be triggered to turn on for a $timeout when connected to a charger, so that users can see charging commenced. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-system-compositor (not installed) ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 25 09:45:42 2014 SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1348538/+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 1186181] Re: battery icon unreliable at low battery levels
** Also affects: ubuntu-ux Importance: Undecided Status: New ** Summary changed: - battery icon unreliable at low battery levels + [Indicator] battery icon unreliable at low battery levels ** Changed in: ubuntu-ux Assignee: (unassigned) = Daniela Ferrai (dferrai) ** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1186181 Title: [Indicator] battery icon unreliable at low battery levels Status in The Power Indicator: Triaged Status in Ubuntu UX bugs: Triaged Status in “indicator-power” package in Ubuntu: Triaged Bug description: Battery icon does not reliably display correct values at low battery levels. The icon works fine until you get below 30%. At 10-30% a small red icon should be displayed, and another icon should be displayed at 10%. Currently, the icon doesn't seem to change to anything smaller than the 40% icon. I have sometimes seen the red 20% icon, but it's very unreliable, and typically switches back to the 40% icon moments after resuming the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1186181/+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
** Summary changed: - Provide a way to change alarm sound + [clock] Provide a way to change alarm sound ** Changed in: ubuntu-ux Assignee: Benjamin Keyser (bjkeyser) = Giorgio Venturi (giorgio-venturi) ** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: ubuntu-ux 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/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: New Status in Ubuntu Clock App reboot series: In Progress Status in Ubuntu UX bugs: Triaged 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 939427] Re: [Launcher] Impossible to reveal the launcher with a stylus on a Wacom tablet
** Summary changed: - Impossible to reveal the launcher with a stylus on a Wacom tablet + [Launcher] Impossible to reveal the launcher with a stylus on a Wacom tablet ** Changed in: ubuntu-ux Importance: Undecided = Low ** Changed in: ubuntu-ux Status: New = Triaged -- 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/939427 Title: [Launcher] Impossible to reveal the launcher with a stylus on a Wacom tablet Status in Ubuntu UX bugs: Triaged Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When i run my Lenovo X200 Tablet in tablet mode, i can't reveal the launcher as it is not possible to push the mouse arrow with a stylus against the edge of the screen as needed by the new reveal behavior. I'm running precise with unity 5.4.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/939427/+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 1317860] Re: [system] the phone should switch itself off before completely draining battery
** Description changed: the phone should switch itself off at around ~5% remaining battery. This is to preserve a little battery for use cases such as: * turn it back on once or twice for urgent short phone calls * prevent the battery from going into a state where it can't be charged any more * have enough power to turn itself on again and trigger an alarm + + + Desired resolution + + The following actions should take place as the phone/tablet runs out of battery: + at 10% - Notification battery under 10% + at 5% - Notification saying battery level is critical, will shutdown soon. + at 1-2% - Shell fades out, animation fades in (same as startup animation), phone initiates full shutdown. + + The notification should be a clickable notification with the tap action + mapped to dismiss. ** Changed in: indicator-power Assignee: (unassigned) = Ricardo Mendoza (ricmm) ** Changed in: indicator-power (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1317860 Title: [system] the phone should switch itself off before completely draining battery Status in The Power Indicator: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “indicator-power” package in Ubuntu: Confirmed Bug description: the phone should switch itself off at around ~5% remaining battery. This is to preserve a little battery for use cases such as: * turn it back on once or twice for urgent short phone calls * prevent the battery from going into a state where it can't be charged any more * have enough power to turn itself on again and trigger an alarm Desired resolution The following actions should take place as the phone/tablet runs out of battery: at 10% - Notification battery under 10% at 5% - Notification saying battery level is critical, will shutdown soon. at 1-2% - Shell fades out, animation fades in (same as startup animation), phone initiates full shutdown. The notification should be a clickable notification with the tap action mapped to dismiss. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1317860/+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 1260978] Re: [Greeter] should be able to control music service from the greeter
** Changed in: ubuntu-ux Importance: Undecided = Wishlist ** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: unity8 (Ubuntu) Status: Incomplete = New ** Also affects: unity8 Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1260978 Title: [Greeter] should be able to control music service from the greeter Status in Ubuntu UX bugs: Triaged Status in The Unity 8 shell: New Status in “indicator-sound” package in Ubuntu: New Status in “ubuntu-music-app” package in Ubuntu: New Status in “ubuntu-settings-components” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: Not sure what component to file this against-- please reassign as desired. I use my phone to play music on random while I'm driving. This works great except when I want to advance or pause the song, where I have to go through the greeter first to access the player. This can either take my attention away from driving or I need to wait until the next stop light to advance the song. This is less of a concern when the greeter can just be swiped with one gesture, but is a big concern if you enable the passcode lock where you have to add the passcode to access the player. If the music is playing, the greeter should allow rudimentary manipulation of the music, eg, pause/play and forward/back. Other platforms seem to allow for this (eg android). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1260978/+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 1236400] Re: Indicator menu entry shows weekday instead of Upcoming
** Changed in: ubuntu-ux 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/1236400 Title: Indicator menu entry shows weekday instead of Upcoming Status in The Date and Time Indicator: Fix Released Status in Ubuntu UX bugs: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Fix Released Bug description: [Impact] (on the phone) the menu title for the date time indicator displays the current day of the week instead of Upcoming. [Test case] pull down the date time indicator menu from the indicators panel, observe that the menu title text (appears in large text just below the panel) displays the current day of the week. [Regression potential] should be none, this is a simple text replacement. [Other Info] this change is only applicable to Ubuntu touch https://wiki.ubuntu.com/TimeAndDate#phone-menu: The menu header should be 'Upcoming', parallel to 'Incoming' for messages. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1236400/+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 1309063] Re: It's confusing to use the Incoming Call sound for Alarms
** Changed in: ubuntu-ux 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/1309063 Title: It's confusing to use the Incoming Call sound for Alarms Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu UX bugs: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: indicator-datetime is currently playing /usr/share/sounds/ubuntu/stereo/phone-incoming-call.ogg when an alarm goes off. This was chosen because it's the closest conceptual fit from the ubuntu-sounds that are available, but IMO a poor fit. Using the same sound for two unrelated events is confusing; we should have a separate, unique alarm sound. Assigning to Design for feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1309063/+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 824965] Re: Alt-tab - When alt-tab is open, the user should be able to left click with the pointer on a specific app/window in order to select it
@theblackhat-mj29; thanks for taking a look at this issue ;-) Please leave the bug status in project ayatana-design as it - we use this project for tracking the design status of bugs, it is separate from implementation. thanks again! ** Changed in: ayatana-design Assignee: Irfan Fauzan (theblackhat-mj29) = John Lea (johnlea) -- 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/824965 Title: Alt-tab - When alt-tab is open, the user should be able to left click with the pointer on a specific app/window in order to select it Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: 1. Open up several apps (for instance, a web browser, a game, a file manager and a terminal). Don't have the apps maximized. 2. Press Alt+Tab. Hold down the Alt key and click the tab selector so that the game is active. 3. While continuing to hold down Alt, use your mouse to click the terminal tile Expected behavior: Unity should switch to the terminal since the mouse click overrides where the tab happened to end up. Alternate example: 3. While continuing to hold down Alt, change your mind and click to the actual file manager in the background. Expected behavior: Unity should switch to the file manager since the mouse click overrides the Alt+Tab behavior. Other notes: Gnome Shell works the way I expect; it would be nice for Unity to do the Right Thing also. User testing notes: In user testing we found that several users tried to use the pointer to select applications/windows when alt-tab was open. -- Desired solution: - The requested change is to enable the use of the pointer and left click to select a specific app/window. Left clicking on a app/window should close the alt-tab and bring the selected item into focus. - Additionally the mouse scroll wheel should be active and allow the user to change focus in either direction To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/824965/+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 655580] Re: [indicators] Add a quick controls for microphone (mute/unmute)
** Summary changed: - Add a quick controls for microphone (mute/unmute) + [indicators] Add a quick controls for microphone (mute/unmute) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/655580 Title: [indicators] Add a quick controls for microphone (mute/unmute) Status in Sound Menu: Opinion Status in Ubuntu UX bugs: New Status in “indicator-sound” package in Ubuntu: Opinion Bug description: Binary package hint: indicator-sound Right now, the sound indicator allows only to mute/unmute or change the speakers (output) level. It would be great if it could also provide a quick control for the microphone (input). By doing so, users will have a quick feedback regarding the reason why the sound input is not working... in most cases the input level being muted or too low. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/655580/+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 1281058] Re: The system shutdowns when multiple accounts are open
** Description changed: Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost - ProblemType: Bug - DistroRelease: Ubuntu 14.04 - Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 - ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 - Uname: Linux 3.13.0-8-generic x86_64 - ApportVersion: 2.13.2-0ubuntu2 - Architecture: amd64 - CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' - CurrentDesktop: Unity - Date: Mon Feb 17 11:49:48 2014 - InstallationDate: Installed on 2013-06-17 (244 days ago) - InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) - SourcePackage: unity - UpgradeStatus: Upgraded to trusty on 2014-01-20 (27 days ago) + -- + Desired resolution: + + - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 + - The warning message should be Other users are currently logged in to this computer, shutting down now will also close these other sessions ** Changed in: ayatana-design Status: New = Fix Committed ** Changed in: ayatana-design Importance: Undecided = Medium ** Changed in: ayatana-design Assignee: (unassigned) = John Lea (johnlea) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1281058 Title: The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: New Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-greeter” package in Ubuntu: Triaged Bug description: Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be Other users are currently logged in to this computer, shutting down now will also close these other sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+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 783808] Re: suspend/hibernate options have no confirmation dialog
** Also affects: indicator-session Importance: Undecided Status: New ** Also affects: ayatana-design Importance: Undecided Status: New ** Changed in: indicator-session (Ubuntu) Assignee: Matthew Paul Thomas (mpt) = (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/783808 Title: suspend/hibernate options have no confirmation dialog Status in Ayatana Design: New Status in The Session Menu: New Status in “indicator-session” package in Ubuntu: Confirmed Bug description: Binary package hint: indicator-session When I select restart, shutdown, or login from the session indicator, I am prompted to confirm I want to do this. But if I select suspend or hibernate, the action is performed immediately. This is particularly annoying if I have selected an option by accident, and in the case of hibernate, the system crashes so it is the same as doing a restart. From a design point of view, wouldn't it be better to have a confirmation dialog for suspend/hibernate to match the other options? ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: indicator-session 0.2.17-0ubuntu1 Uname: Linux 2.6.39-rc6-generic x86_64 Architecture: amd64 Date: Tue May 17 12:58:28 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/783808/+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 1286784] Re: Inconsistent scrollwheel launcher behavior for window switching.
@asmoore82; thank you for your very detailed analysis and bug report and also for submitting a patch! I agree with your analysis so +1 from design for landing this change. thanks! ** Changed in: ayatana-design Assignee: (unassigned) = John Lea (johnlea) ** Changed in: ayatana-design Importance: Undecided = Medium ** Changed in: ayatana-design Status: New = Fix Committed -- 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/1286784 Title: Inconsistent scrollwheel launcher behavior for window switching. Status in Ayatana Design: Fix Committed Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Background: I believe it first landed in 13.04 that scrolling the mouse wheel over launcher icons would flip through multiple windows of that app or do nothing if that app was not open. IMO, this is exactly what Unity was missing that I couldn't put a finger on for myself and I love it!! This worked exactly as described there for all lauchers regardless of what app was focused. Apparently, working on unfocused apps was unintentional but at this point it has been in use in the wild for a while. This unintended feature has recently been removed in the fix for #1263786 and #1267888. Current Sitution: The recurring theory in this scrollwheel discussion has been that whatever scrolling in one direction does, scrolling in the opposite direction should undo. The primary focus of this bug is just to define where such opposite scrolling needs fixing. But it must also be pointed out that fixing these behaviors resolves some complaints against the aforementioned unintended feature making its removal unnecessary. And a consistent approach to this could also solve some other hotly requested use cases. 1. Single App Use Case 1.1. Steps to Reproduce 1.1.1. Open 4 Terminals. They should naturally position into the 4 corners so let's refer to them as NorthWest, NorthEast, SouthWest, SouthEast (NW, NE, SW, SE). 1.1.2. Click through them all to force a Z order. Of course the Z order will be the opposite of the click order so I click through them intentionally backwards bottom to top and right to left: SE, SW, NE, NW. My Z order is now NW, NE, SW, SE; NW is the focused window. 1.1.3. Mouseover Terminal Launcher and Scrollwheel Down Repeatedly, eventually coming to rest on NW again as the focused window. This proceeds through and loops the Z order as expected: NW, NE, SW, SE, ... NW 1.1.4. Mouseover Terminal Launcher and Scrollwheel Up Repeatedly, eventually coming to rest again on NW. This reverses through and loops the Z order as expected: SE, SW, NE, NW ... NW 1.1.5 Mouseover Terminal Launcher and Scrollwheel Down 1 notch and then Up 1 notch. 1.2. Expected Results: Down Goes from NW to NE and Up goes back from NE to NW. Z order should remain unchanged: NW, NE, SW, SE. 1.3. Actual Results: Down Goes from NW to NE and Up goes from NE to SE. 1.4. Reasoning: The Up abrubtly terminates the Down process causing NE to gain focus and leaving the new Z order NE, NW, SW, SE. Now the new Up process immediately processes from the bottom of the Z order to SE. Presumably if this Up process is completed here and SE gains focus the Z order ends at SE, NE, NW, SW. This can be confirmed by swicthing direction again and scrolling down repeatedly. 1.5. Preferred Fix: Scrollwheel Up and Down should proceed through the Z order but should not be independent. In other words, an App Launcher Scrolling Event on the focused should grab and freeze the Z order of all App windows and scroll through the them, up or down, until all scrolling is done. 1.6. Alternative Fix: If Scrolling were changed to proceed through some sort of spacial relationship instead of Z order it would not matter if they were independent. However, behavior for windows of identical geometry would then be undefined. 1.7. Alternative Fix: If Scrolling were changed to always proceed through the order shown in the Launcher context menu it would not matter. This would also most closely resemble previous mouse wheel behavior on the old Gnome 2 window list panel. Presumably this ordering is defined by window creation order or age. 2. Multitasking Use Case 2.1 Steps to Reproduce 2.1.1. Same as 1.1.1. Open 4 Terminals. 2.1.2. Same as 1.1.2. Force Z Order NW, NE, SW, SE. 2.1.3. Click Other Launcher. Other App (Firefox in my case) is opened/focused. The effects of later steps are easiest to noticed when this other App is maximized. 2.1.4. Click Terminal Launcher. As expected NW Terminal is focused; all other terminals remain below Other App (OA). Z Order is NW, OA. 2.1.5. Scrollweel Down Repeatedly. This is a part of the genius of the whole Scrollwheel feature!! As expected, this cycles through
[Dx-packages] [Bug 1281368] Re: Decorations: windows should have 0px (bottom and side) borders
@Treviño; Just to confirm, am I correct to assume the actual invisible dragable area on each window border that a user can use to resize the window remains unchanged? If this is the case +1 from design for 0px window borders, it looks much better ;-) ** Changed in: ayatana-design Status: New = Fix Committed ** Changed in: ayatana-design Assignee: (unassigned) = John Lea (johnlea) -- 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/1281368 Title: Decorations: windows should have 0px (bottom and side) borders Status in Ayatana Design: Fix Committed Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Back in 11.04 it was decided to go borderless but was reverted mainly because of unity-2d. Since then users that wish this could easily adjust in metacity-1. Now that's gone with the unity-window decorator. Dark windows look bad with the light grey? 1 px. border, particuarly some video players, gnome-terminal ect. (I understand that without a border 2 overlaping terminals may be weird but overall borderless looks better in general use Or at the least somehow color it something less obvious distracting. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Feb 17 20:37:35 2014 InstallationDate: Installed on 2014-02-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140217) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281368/+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 1281368] Re: Decorations: windows should have 0px (bottom and side) borders
@mc3man; could you provide a visual mockup of the proposed change so we can review and make a decision on whether to implement. Thanks! -- 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/1281368 Title: Decorations: windows should have 0px (bottom and side) borders Status in Ayatana Design: New Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Back in 11.04 it was decided to go borderless but was reverted mainly because of unity-2d. Since then users that wish this could easily adjust in metacity-1. Now that's gone with the unity-window decorator. Dark windows look bad with the light grey? 1 px. border, particuarly some video players, gnome-terminal ect. (I understand that without a border 2 overlaping terminals may be weird but overall borderless looks better in general use Or at the least somehow color it something less obvious distracting. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Feb 17 20:37:35 2014 InstallationDate: Installed on 2014-02-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140217) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281368/+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 1281368] Re: Decorations: windows should have 0px (bottom and side) borders
@Treviño; thanks for the screenshot, I'll review with Marcus when he is in the office tomorrow and let you know. -- 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/1281368 Title: Decorations: windows should have 0px (bottom and side) borders Status in Ayatana Design: New Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Back in 11.04 it was decided to go borderless but was reverted mainly because of unity-2d. Since then users that wish this could easily adjust in metacity-1. Now that's gone with the unity-window decorator. Dark windows look bad with the light grey? 1 px. border, particuarly some video players, gnome-terminal ect. (I understand that without a border 2 overlaping terminals may be weird but overall borderless looks better in general use Or at the least somehow color it something less obvious distracting. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Feb 17 20:37:35 2014 InstallationDate: Installed on 2014-02-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140217) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281368/+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 1101037] Re: Rubbish bin (trash) launcher icon should be unlockable
** Changed in: ayatana-design Status: Incomplete = Fix Committed ** Changed in: ayatana-design Importance: Undecided = Low ** Changed in: ayatana-design Assignee: (unassigned) = John Lea (johnlea) -- 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/1101037 Title: Rubbish bin (trash) launcher icon should be unlockable Status in Ayatana Design: Fix Committed Status in Unity: Expired Status in “unity” package in Ubuntu: Confirmed Bug description: At the moment, the Rubbish bin icons is locked to the launcher by default. Some people don't need such access to the rubbish bin. This icon should have the option Unlock from Launcher in its quicklist so people who don't find it useful can make some space in their launcher. As this icon is not really an app, maybe it would be more suitable to be able to enable or disable them from System Settings - Appearance, CCSM or gconf-editor. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jan 18 11:53:14 2013 InstallationDate: Installed on 2012-10-21 (88 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bashSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1101037/+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 1101037] Re: Rubbish bin (trash) launcher icon should be unlockable
@townsend; it is exactly what you need ;-) There are two possible changes here: 1. Allow users to move the Trash to a different location in the Launcher, but users should not be able to remove (un-pin) the trash from the Launcher. This is the easiest version of the change. 2. Allow users to both move the Trash to a different location in the Launcher and also un-pin the trash from the Launcher. At the same time this change lands we would need to add the capability for users to find the trash in the dash so they could re-pin the Trash to the Launcher. I suggest implementing option 1 for now. If anybody is interested in implementing option 2 patches that implement this functionality would be gratefully accepted ;-) -- 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/1101037 Title: Rubbish bin (trash) launcher icon should be unlockable Status in Ayatana Design: Fix Committed Status in Unity: Expired Status in “unity” package in Ubuntu: Confirmed Bug description: At the moment, the Rubbish bin icons is locked to the launcher by default. Some people don't need such access to the rubbish bin. This icon should have the option Unlock from Launcher in its quicklist so people who don't find it useful can make some space in their launcher. As this icon is not really an app, maybe it would be more suitable to be able to enable or disable them from System Settings - Appearance, CCSM or gconf-editor. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jan 18 11:53:14 2013 InstallationDate: Installed on 2012-10-21 (88 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bashSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1101037/+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 1257847] Re: Time is not correct in the indicator
** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity Importance: Undecided = High -- 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/1257847 Title: Time is not correct in the indicator Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: I am using Saucy on my desktop pc, and the indicator does not show the correct time! To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1257847/+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 1189058] Re: Dash: com.canonical.Unity.Lenses should have a key to individually disable online/remote searches per scope id
Marking invalid, because this functionality is already part of Ubuntu 13.10, see comment #5! ** Changed in: ayatana-design Status: Confirmed = Invalid ** Changed in: unity-scope-home Status: Confirmed = Invalid ** Changed in: unity (Ubuntu) Status: Triaged = Invalid -- 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/1189058 Title: Dash: com.canonical.Unity.Lenses should have a key to individually disable online/remote searches per scope id Status in Ayatana Design: Invalid Status in Unity Home Scope: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: As it stands now you only have remote-content-search 'all or 'none' That seems overly permissive or restrictive Users should have the choice to allow some scopes to do remote searches disallow others as they see fit. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.0.0daily13.06.07-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic i686 ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Jun 8 20:58:06 2013 InstallationDate: Installed on 2013-05-29 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130529) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1189058/+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 1204717] Re: Middle-click on title bar causes focus switch
@townsend; could you double check that the newly topmost window is automatically focused when the user performs this action? -- 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/1204717 Title: Middle-click on title bar causes focus switch Status in Ayatana Design: New Status in “unity” package in Ubuntu: Invalid Bug description: When middle-clicking on title bar (maximized or not), focus switches to a different window. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Jul 25 02:21:52 2013 MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1204717/+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 1212586] Re: alt-tab switches workspaces to focus apps, but shouldn't
** Changed in: ayatana-design Status: Fix Committed = Invalid ** Tags removed: udp -- 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/1212586 Title: alt-tab switches workspaces to focus apps, but shouldn't Status in Ayatana Design: Invalid Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: ALT+TAB in 13.10 is broken, a regression. If you have apps open on workspace 1 and workspace 2, then alt-tabbing can take you from workspace 1 to workspace 2, when it shouldn't. Steps to reproduce. On workspace 1, open terminal, multiple browser (chromium in my case) windows, leave terminal focussed On workspace 2 also open a terminal and multiple browser windows. Leave browser focussed Use CTRL+ALT+ARROWS to switch back to workspace 1 Use ALT+TAB to switch to the browser on workspace 1 You end up switching to workspace 2 Expected results (and what happens on previous releases) You stay on workspace 1 and switch to another app/window See video at :- http://www.youtube.com/watch?v=BubHhtqFUlc Note from Design: alt-tab *should not* move the user between workspaces. It should only show the apps/windows open on the current workspace. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130813.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell] Date: Thu Aug 15 09:15:06 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-06-29 (411 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-07-12 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1212586/+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 676457] Re: Launcher - Add 'launching' state to launcher icons
** Changed in: ayatana-design Importance: Critical = Low ** Changed in: unity Importance: Medium = Low ** Changed in: unity-2d Importance: Critical = Low ** Changed in: unity-design Importance: Critical = Low -- 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/676457 Title: Launcher - Add 'launching' state to launcher icons Status in Ayatana Design: Fix Committed Status in The Charlotte project: Fix Released Status in Unity: Confirmed Status in Unity 2D: Fix Released Status in obsolete project, use ayatana-design instead: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-2d” package in Ubuntu: Triaged Bug description: Add 'launching' state to launcher icons Description: 1. As soon as a user clicks on a app in the Dash Application Lens, the Launcher should use the 'startup notification protocol' to *instantly* place a icon for the application in the launcher (in the 'launching' state). As soon as the app has finished launching, the Launcher icon should switch to the 'running' state. 2. As soon as a user clicks on a app in the Launcher that is not running, the Launcher icon should instantaneously switch to the 'launching' state. As soon as the app has finished launching, the Launcher icon should instantly switch to the 'running' state. The following art assets will be attached to this bug: 1. Add 'launching' placeholder Launcher icon to handle the case where we know an app has launched but we don't have it's icon. *important* - this icon should only be used when we know an app has been launched but we don't know its icon. If we can get the application's icon quickly we should use this correct icon instead. https://chinstrap.canonical.com/~sabdfl/11_04/desktop_and_netbook/launcher/unity_desktop_26_01_11_stages_fixed_10.png (note the outer glow shown in this same design is not the correct cursor select state, for the correct cursor select state see https://chinstrap.canonical.com/~sabdfl/11_04/desktop_and_netbook/launcher/select/ ) Notes: - we flash the backlight of the icon during launch - as soon as we have startup notification, we create an item in the launcher, in grayscale, and start flashing its backlight - as soon as we know the desktop file and hence icon, we transition to the icon backlight from grayscale to an appropriate colouring based on the icon Finally we need a instant flash on click. See bug #893140 for a full description of this instant feedback issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/676457/+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 764424] Re: Launcher - dropping a file on a launcher app icon should open that file in the app
** Changed in: ayatana-design Importance: Critical = High -- 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/764424 Title: Launcher - dropping a file on a launcher app icon should open that file in the app Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: If a user drags and drops a file on top of a Launcher app icon, the application should open the file if it is a file type it supports. If the application does not support the file type nothing should happen. Most of the time this interaction does not work. Occasionally it does work but it freezes the desktop requiring a unity restart. Tested using .png files with Firefox and GIMP, and .html files with Firefox and Chrome. Also at the moment many Launcher icons do not highlight when the user starts dragging, even if the application supports opening the file type being dragged. Note the new file should be opened in exactly the same manner as when opening the file with the 'open with [app name]' Nautilus option, e.g. when opening a .txt file by dropping it on to gedit, if there is already one or more gedit window(s) open, the file should open into a tab on the most recently focused gedit window. UPDATE : Compiz screws up the handling when a drop happens at about the same time as the scale timeout goes off. It doesn't freeze so much as grab the mouse forever. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/764424/+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 764424] Re: Launcher - dropping a file on a launcher app icon should open that file in the app
** Description changed: If a user drags and drops a file on top of a Launcher app icon, the application should open the file if it is a file type it supports. If the application does not support the file type nothing should happen. - Most of the time this interaction does not work. Occasionally it does - work but it freezes the desktop requiring a unity restart. Tested using - .png files with Firefox and GIMP, and .html files with Firefox and - Chrome. - Also at the moment many Launcher icons do not highlight when the user starts dragging, even if the application supports opening the file type being dragged. - Note the new file should be opened in exactly the same manner as when - opening the file with the 'open with [app name]' Nautilus option, e.g. - when opening a .txt file by dropping it on to gedit, if there is already - one or more gedit window(s) open, the file should open into a tab on the - most recently focused gedit window. + For example, if the user starts dragging a text file firefox and + libreoffice writer should illuminate in addition to gedit. - UPDATE : Compiz screws up the handling when a drop happens at about the - same time as the scale timeout goes off. It doesn't freeze so much as - grab the mouse forever. + Another example is dragging a tarball; thunderbird should illuminate and + if the tarball is dropped on the thunderbird icon it should open a new + message with it as an attachment. + + + UPDATE : Compiz screws up the handling when a drop happens at about the same time as the scale timeout goes off. It doesn't freeze so much as grab the mouse forever. + + + + - + Desired resolution: + + - create a new desktop key that details all file types that can be + imported into an application. See Robert Carr's comments #1 and #4 for + details. + + - For the following applications, ensure the information about which + file types can be opened by a drag and drop operation is updated: + LibreOffice, Thunderbird, Chormium, Firefox, Gedit, Image viewer, + Shotwell, GIMP, Transmission, Terminal, Brasero Disk Burner, Archive + Manager, Evolution, Rhythembox, VLC ** Changed in: unity Status: Fix Released = Triaged ** Changed in: unity (Ubuntu) Status: Fix Released = Triaged -- 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/764424 Title: Launcher - dropping a file on a launcher app icon should open that file in the app Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: If a user drags and drops a file on top of a Launcher app icon, the application should open the file if it is a file type it supports. If the application does not support the file type nothing should happen. Also at the moment many Launcher icons do not highlight when the user starts dragging, even if the application supports opening the file type being dragged. For example, if the user starts dragging a text file firefox and libreoffice writer should illuminate in addition to gedit. Another example is dragging a tarball; thunderbird should illuminate and if the tarball is dropped on the thunderbird icon it should open a new message with it as an attachment. UPDATE : Compiz screws up the handling when a drop happens at about the same time as the scale timeout goes off. It doesn't freeze so much as grab the mouse forever. - Desired resolution: - create a new desktop key that details all file types that can be imported into an application. See Robert Carr's comments #1 and #4 for details. - For the following applications, ensure the information about which file types can be opened by a drag and drop operation is updated: LibreOffice, Thunderbird, Chormium, Firefox, Gedit, Image viewer, Shotwell, GIMP, Transmission, Terminal, Brasero Disk Burner, Archive Manager, Evolution, Rhythembox, VLC To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/764424/+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 1223037] Re: Switcher mouse bump in detail mode causes selection change
** Changed in: ayatana-design Assignee: (unassigned) = John Lea (johnlea) ** Changed in: ayatana-design Importance: Undecided = High ** Changed in: ayatana-design Status: New = Fix Committed -- 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/1223037 Title: Switcher mouse bump in detail mode causes selection change Status in Ayatana Design: Fix Committed Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Just like this bug 1215630 But for the detail mode :), forgot to do the same for detail mode... To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1223037/+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 1218289] Re: [dialer app] Incoming call (snap decision) not to spec
** Description changed: Current situation: Incoming call appears in snap decision format, but missing: - Current screen becomes inactive, except for incoming call snap decision - Decision buttons not the right visual colours and assets (missing colour and combo button) Desired solution: - As per spec, when receiving an incoming call the snap decision should make the current screen inactive (eg grey out) except for the notification. And the notification buttons and style should be as per design. + - As per spec, when receiving an incoming call the snap decision should make the current screen inactive (eg grey out) except for the notification. And the notification buttons and style should be as per design. + - See Notification and Snap Decision spec for full details of the final signed off design, https://docs.google.com/a/canonical.com/document/d/1puQ9Z0yKqzsQ1VQ1OOBkxgp78iWGnAhAkFXWJFTWIrE/edit -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1218289 Title: [dialer app] Incoming call (snap decision) not to spec Status in Dialer app for Ubuntu Touch: New Status in Notify OSD: New Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: New Status in “dialer-app” package in Ubuntu: New Status in “notify-osd” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: Current situation: Incoming call appears in snap decision format, but missing: - Current screen becomes inactive, except for incoming call snap decision - Decision buttons not the right visual colours and assets (missing colour and combo button) Desired solution: - As per spec, when receiving an incoming call the snap decision should make the current screen inactive (eg grey out) except for the notification. And the notification buttons and style should be as per design. - See Notification and Snap Decision spec for full details of the final signed off design, https://docs.google.com/a/canonical.com/document/d/1puQ9Z0yKqzsQ1VQ1OOBkxgp78iWGnAhAkFXWJFTWIrE/edit To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1218289/+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 1215630] Re: Hover on alt-tab easily bumped
** Description changed: At some point the alt-tab application switcher seems to have gained support for mouse hover. This means if you have the mouse in the middle of the screen and then bump it while doing an alt-tab you can easily select the wrong application. To reproduce: 1. hold alt down 2. press tab 3. Move mouse to the left of the switcher on the edge of an application icon 4. Press tab a few times 5. Move the mouse a little bit across between two icons Expected result: The selected icon doesn't change Observed result: The icon under the mouse is selected This is particularly bad when the icons concertina under the mouse. Then basically any mouse movement will un-concertina them and select the wrong icon. - ProblemType: Bug - DistroRelease: Ubuntu 13.10 - Package: unity 7.1.0+13.10.20130822-0ubuntu1 - ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6 - Uname: Linux 3.11.0-3-generic x86_64 - ApportVersion: 2.12.1-0ubuntu2 - Architecture: amd64 - CheckboxSubmission: e440e09ef58a53bccc45087674ba6b8e - CheckboxSystem: d00f84de8a555815fa1c4660280da308 - CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] - Date: Fri Aug 23 09:11:35 2013 - InstallationDate: Installed on 2011-04-01 (874 days ago) - InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110330) - MarkForUpload: True - SourcePackage: unity - UpgradeStatus: Upgraded to saucy on 2011-07-05 (778 days ago) + --- + Desired resolution: + + - when the alt-tab mode is entered, the pointer should be desensitised so that is no action is taken until the pointer has moved more than a certain distance in any direction + - To start with try using a value that nothing happens until the pointer moves more than 3 pixels in any direction. Then see how this feels, and adjust this value as appropriate to get the best feel. ** Changed in: ayatana-design Assignee: (unassigned) = John Lea (johnlea) ** Changed in: ayatana-design Importance: Undecided = High ** Changed in: unity Importance: Medium = High ** Changed in: ayatana-design Status: New = Fix Committed ** Tags added: udp ** Summary changed: - Hover on alt-tab easily bumped + [Alt-Tab] Hover on alt-tab easily bumped -- 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/1215630 Title: [Alt-Tab] Hover on alt-tab easily bumped Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: At some point the alt-tab application switcher seems to have gained support for mouse hover. This means if you have the mouse in the middle of the screen and then bump it while doing an alt-tab you can easily select the wrong application. To reproduce: 1. hold alt down 2. press tab 3. Move mouse to the left of the switcher on the edge of an application icon 4. Press tab a few times 5. Move the mouse a little bit across between two icons Expected result: The selected icon doesn't change Observed result: The icon under the mouse is selected This is particularly bad when the icons concertina under the mouse. Then basically any mouse movement will un-concertina them and select the wrong icon. --- Desired resolution: - when the alt-tab mode is entered, the pointer should be desensitised so that is no action is taken until the pointer has moved more than a certain distance in any direction - To start with try using a value that nothing happens until the pointer moves more than 3 pixels in any direction. Then see how this feels, and adjust this value as appropriate to get the best feel. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1215630/+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
