[Dx-packages] [Bug 1481093] [NEW] libcolumbus ftbfs in wily

2015-08-03 Thread Matthias Klose
Public bug reported:

see
https://launchpad.net/ubuntu/+source/libcolumbus/1.1.0+14.04.20140325.3-0ubuntu4

** Affects: libcolumbus (Ubuntu)
 Importance: Critical
 Assignee: Ubuntu Touch seeded packages (touch-packages)
 Status: Confirmed

** Changed in: libcolumbus (Ubuntu)
 Assignee: (unassigned) => Ubuntu Touch seeded packages (touch-packages)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libcolumbus in Ubuntu.
https://bugs.launchpad.net/bugs/1481093

Title:
  libcolumbus ftbfs in wily

Status in libcolumbus package in Ubuntu:
  Confirmed

Bug description:
  see
  
https://launchpad.net/ubuntu/+source/libcolumbus/1.1.0+14.04.20140325.3-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcolumbus/+bug/1481093/+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 1430059] Re: LyX menu is not updated by indicator-appmenu in mode unity-all-menus

2015-08-03 Thread Christoph Stich
@Liviu: The package from your PPA you posted installs fine for me and
fixes the Lyx as well as the VLC menus for me on my Vivid system. Thanks
for the port.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1430059

Title:
  LyX menu is not updated by indicator-appmenu in mode unity-all-menus

Status in indicator-appmenu package in Ubuntu:
  Fix Released
Status in indicator-appmenu source package in Vivid:
  Confirmed

Bug description:
  Options greyed out:
  - File menu: "Close" through "Version control", plus "Export" and "Print"
  - Edit menu: all options
  - View menu: all but "Messages pane", "Toolbars" and "Fullscreen"
  - Insert menu: all options
  - Navigate menu: all options
  - Document menu: all options
  - Tools menu:  "Spellchecker" and "Statistics"

  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  lyx:
Installed: 2.1.3-1
Candidate: 2.1.3-1
Version table:
   *** 2.1.3-1 0
  500 http://br.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lyx 2.1.3-1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  9 19:45:01 2015
  ExecutablePath: /usr/bin/lyx
  InstallationDate: Installed on 2015-02-03 (33 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lyx
  UpgradeStatus: Upgraded to vivid on 2015-03-05 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1430059/+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 160311] Re: Resizing windows by grabbing window borders is difficult

2015-08-03 Thread JohnWashington
I don't even accept that it's  adequately fixed in Unity (unless there's
been significant progress since 14.04, for I only use LTS releases).

I teach elderly users with little or no experience of computers.
Naturally many don't have good hand/eye coordination, so they need to be
able to adjust settings easily to make the system fit their needs.  One
would expect this to be found under Settings / Universal Access, but
there is nothing there that addresses this issue.

If you look at Windows XP (I'm not familiar enough with later versions
to speak from memory) you can go into the control panel and set window
borders to whatever width you want.  After adjustment the result may not
be as pretty, but when you're over 70 and unlikely to have a career in
Hollywood, 'pretty' isn't high on your wish list, accessibility IS.

Please consider addressing this.  It would be a boon if you can get it
done before 16.04.

-- 
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/160311

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 160311] Re: Resizing windows by grabbing window borders is difficult

2015-08-03 Thread Colin Law
@Jeremy Huddleston, I see you are right, apologies (except that the fix
appeared only in Unity-3D, it was worse in Unity-2D than it was before
Unity-2D appeared).  Does Xubuntu use Metacity?  If not then my point is
still valid, that it would be best to file a new bug for Xubuntu if the
problem exists there, describing in detail exactly what the problem is.

-- 
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/160311

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 1481032] [NEW] /usr/lib/arm-linux-gnueabihf/indicator-sound/indicator-sound-service:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:tuple_allocate_members:tup

2015-08-03 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding indicator-sound.  This problem was most recently seen with
version 12.10.2+15.04.20150508-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/6b23a85238342ea36ea54a89e914b26f9834978f
contains more details.

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

-- 
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/1481032

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-sound/indicator-sound-
  
service:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:tuple_allocate_members:tuple_info_new

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-sound.  This problem was most recently seen with
  version 12.10.2+15.04.20150508-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6b23a85238342ea36ea54a89e914b26f9834978f
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1481032/+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 160311] Re: Resizing windows by grabbing window borders is difficult

2015-08-03 Thread Jeremy Huddleston
@colin-law no, this bug does not apply to Unity.  This bug was filed
years before Unity even existed.  If it is "fixed" by changing to Unity,
that's great for Unity users, but simply sweeping an issue under the rug
because you changed window systems doesn't change the fact the the bug
continues to exist in the windowing systems that the issue was reported
against.

-- 
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/160311

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 1396700] Re: Needs to be updated to bluez5

2015-08-03 Thread Pat McGowan
resuscitating this

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => ww40-2015

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Summary changed:

- Needs to be updated to bluez5
+ Indicator needs to be updated to bluez5

-- 
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/1396700

Title:
  Indicator needs to be updated to bluez5

Status in Canonical System Image:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  In Progress

Bug description:
  See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for
  details

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1396700/+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 1415480] Re: [indicators]/OSD provide no visual clue that they modify bluetooth device volumes

2015-08-03 Thread Pat McGowan
** Also affects: indicator-bluetooth (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => ww40-2015

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: indicator-bluetooth (Ubuntu)
   Importance: Undecided => High

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-bluetooth (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: canonical-devices-system-image
 Assignee: Charles Kerr (charlesk) => Alejandro J. Cura (alecu)

-- 
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/1415480

Title:
  [indicators]/OSD provide no visual clue that they modify bluetooth
  device volumes

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Connect a bluetooth audio device (headset, speakers) to the ubuntu
  phone.

  Play music/enter into a call, so that you have active audio to the
  device.

  Adjust the volume, using the UI or keys on the ubuntu phone.

  The volume of the bluetooth headset changes (good) but the ui contains
  no clue that this is what the phone is doing (less good). The standard
  volume indicator is shown. This can lead to user confusion if they are
  not currently using the paired bluetooth accessory, and have forgotten
  it is paired. On other devices the volume indicator changes to provide
  visual feedback that the bluetooth device volume is being set.

  --

  Desired resolution:

  Please use this icon to replace the volume icon. The icon is bluetooth
  volume which we had design already.

  https://www.dropbox.com/s/a5r3ro1h0917p0a/audio-speakers-bluetooth-
  symbolic.svg?dl=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415480/+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 694224] Re: Synchronous notifications briefly steal focus

2015-08-03 Thread kevin gunn
** Changed in: notify-osd (Ubuntu)
 Assignee: (unassigned) => Mirco Müller (macslow)

-- 
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/694224

Title:
  Synchronous notifications briefly steal focus

Status in notify-osd package in Ubuntu:
  Confirmed

Bug description:
  It appears synchronous notifications (at least those for volume and
  brightness) briefly steal focus when they appear. This is quite
  problematic for games and some other applications that pause as soon
  as they lose focus. The focus stealing does not happen with normal,
  asynchronous notifications.

  Here's a quick Python program to reproduce this:

  #!/usr/bin/python
  import gtk
  import time
  def cb (wid, ev):
evtime = time.strftime ("%H:%M:%S", time.localtime())
print ("%s: Lost focus!" % evtime)
  win = gtk.Window()
  win.connect ("focus-out-event", cb)
  win.show_all()
  gtk.main()

  
  You could also just start playing Quadrapassel, then adjust your volume :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/694224/+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 1439136] Re: [notifications] Messages readable when phone locked..

2015-08-03 Thread Paty Davila
** Description changed:

  When the phone is in a locked state swiping down you are able to get
  access to the notification tab,
  
  from here you are able to read recent SMS messages -- which is all well
  and good if you want quick access to your text messages but you are also
  able to reply to the text message without unlocking the phone.
  
  in summary;
  
  You are able to read and send SMS messages without unlocking the phone.
  
  UX comment-
  
  We've added in the latest specification for notifications the behaviour
  on the lock screen. Link to the spec:
- 
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#
+ 
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.knlgrccv4svp

-- 
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/1439136

Title:
  [notifications] Messages readable when phone locked..

Status in Ubuntu UX:
  Fix Committed
Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  When the phone is in a locked state swiping down you are able to get
  access to the notification tab,

  from here you are able to read recent SMS messages -- which is all
  well and good if you want quick access to your text messages but you
  are also able to reply to the text message without unlocking the
  phone.

  in summary;

  You are able to read and send SMS messages without unlocking the
  phone.

  UX comment-

  We've added in the latest specification for notifications the
  behaviour on the lock screen. Link to the spec:
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.knlgrccv4svp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1439136/+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 1445106] Re: [Notifications] turn the screen on

2015-08-03 Thread Paty Davila
** Changed in: ubuntu-ux
 Assignee: Paty Davila (dizzypaty) => Andrea Bernabei (faenil)

-- 
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/1445106

Title:
  [Notifications] turn the screen on

Status in Ubuntu UX:
  Triaged
Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  Built: r20

  When getting a notification, such as a text message, the screen will turn on.
  This becomes a problem when the device is kept in a pocket,
  where it may falsely register screen activity and thus stay on for hours.

  
  -UX comment-

  Please refer for the correct behaviour here:
  
https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+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 1365408] Re: Should ship a PNG icon instead of using the theme

2015-08-03 Thread Matthieu James
** 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-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1365408

Title:
  Should ship a PNG icon instead of using the theme

Status in Ubuntu Application Launcher:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in mediaplayer-app package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu:
  Fix Released
Status in sync-monitor package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu RTM:
  Fix Released
Status in mediaplayer-app package in Ubuntu RTM:
  Fix Released
Status in messaging-app package in Ubuntu RTM:
  Fix Released

Bug description:
  By design request, all apps, click or not, should ship their own icon
  as PNG instead of using icons from the theme.

  Please download the respective icon from http://bazaar.launchpad.net
  /~ubuntu-art-pkg/ubuntu-themes/trunk/files/head:/suru-icons/apps/256/
  and include in your packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-app-launch/+bug/1365408/+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 160311] Re: Resizing windows by grabbing window borders is difficult

2015-08-03 Thread Colin Law
@vedavrata this bug applies to Unity, and is effectively closed.  If you
are seeing a problem on Xubuntu then I suggest you file a new bug.

-- 
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/160311

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 1446081] Re: Incorrect scaling of launcher icons

2015-08-03 Thread Matheus
Same issue here. Please Canonical fix this.

** Attachment added: "Icons crashed"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081/+attachment/4438334/+files/Screenshot%20from%202015-06-11%2012-11-02.png

-- 
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/1446081

Title:
  Incorrect scaling of launcher icons

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Launcher icons shown w/o issues only on this sizes of launcher: 16,
  24, 32, 48, 64.

  Screenshot attached. Look at Sublime, Chrome and Skype icons. There
  was no such issue before vivid.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Apr 20 00:26:44 2015
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1446081/+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 1478075] Re: Sound indicator should only indicate ringtone volume

2015-08-03 Thread Stuart Langridge
"It's true that with the current UI you can't change the ringtone volume
while media is playing. But there's still no explanation here of why
that would actually be a problem"

An additional piece of information which may weigh into this discussion
(I propose no solutions here) is that of apps and games which play
sounds but do not play constant music. This may be because they are
capable of playing background music but the user has switched it off, or
that the app is not a game but uses sounds for various events. In such a
situation, it is often very difficult to decrease the sound volume of
the game. If the current foreground app is, for example, a game which
plays sounds for events but does not have background music, then it's
very unclear what using the hardware volume keys is *expected* to do in
this situation. Application sounds obey the media volume setting, not
the ringer volume setting (and I assume for this discussion that they
will continue to do so, although see below). If the hardware volume keys
are used when such a game is the current app, should they adjust the
media volume? The phone is not currently playing any media, and there is
no obvious direct feedback to be heard when the media volume adjusts
(unlike, for example, the music app, where a media volume change is
immediately apparent). But if the hardware volume keys adjust the ringer
volume when there is no media *playing*, then it becomes effectively
impossible to decrease the volume of the game's event sounds. Android
and iOS both suffer from this issue, and it is I think at least
partially because there are at least two independent volume settings
(media and ringer) but they are presented as one context-dependent
setting. Maybe separating out the two settings and making them
independently adjustable would help alleviate this confusion (at the
cost of additional complexity)?

-- 
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/1478075

Title:
  Sound indicator should only indicate ringtone volume

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Incomplete

Bug description:
  On the phone, the volume indicator follows the current active stream
  volume (music, alarm etc.) to show and control via slider and/or
  volume buttons.

  The indicator icon and slider should only ever follow the ringtone
  volume. I'm not sure whether volume buttons should work for alarms.

  This is somewhat related to bug #1291458.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150508-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '', 
[<{'running': , 'state': <'Paused'>}>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (true, '', [<{'running': , 
'state': <'Paused'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Paused'>]), 'volume': (true, 'i', [<0.7414398193359375>]), 
'next.mediaplayer-app.desktop': (true, '', []), 'indicator-shown': (true, '', 
[]), 'root': (true, '', [<{'title': <'Dźwięk'>, 'accessible-desc': 
<'Głośność (74%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'silent-mode': (true, '', []), 'previous.mediaplayer-app.desktop': 
(true, '', [])},)
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: armhf
  Date: Fri Jul 24 18:07:15 2015
  InstallationDate: Installed on 2015-07-23 (1 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20150723-020304)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478075/+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 1478075] Re: Sound indicator should only indicate ringtone volume

2015-08-03 Thread Stuart Langridge
(Additional: perhaps app event sounds should obey the ringer volume, not
the media volume? This is unlikely to be a good approach and carries
with it its own confusion; it becomes impossible to silence a game
without also silencing the ringer, which is not good.)

-- 
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/1478075

Title:
  Sound indicator should only indicate ringtone volume

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Incomplete

Bug description:
  On the phone, the volume indicator follows the current active stream
  volume (music, alarm etc.) to show and control via slider and/or
  volume buttons.

  The indicator icon and slider should only ever follow the ringtone
  volume. I'm not sure whether volume buttons should work for alarms.

  This is somewhat related to bug #1291458.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150508-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '', 
[<{'running': , 'state': <'Paused'>}>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (true, '', [<{'running': , 
'state': <'Paused'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Paused'>]), 'volume': (true, 'i', [<0.7414398193359375>]), 
'next.mediaplayer-app.desktop': (true, '', []), 'indicator-shown': (true, '', 
[]), 'root': (true, '', [<{'title': <'Dźwięk'>, 'accessible-desc': 
<'Głośność (74%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'silent-mode': (true, '', []), 'previous.mediaplayer-app.desktop': 
(true, '', [])},)
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: armhf
  Date: Fri Jul 24 18:07:15 2015
  InstallationDate: Installed on 2015-07-23 (1 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20150723-020304)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478075/+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 160311] Re: Resizing windows by grabbing window borders is difficult

2015-08-03 Thread vedavata
On XUbuntu (XFCE Ubuntu) 14.10 and 15.04 this bug is still has place.
:-(

-- 
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/160311

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 1378618] Re: volume notification looks bad when an indicator is open

2015-08-03 Thread Paty Davila
** 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-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1378618

Title:
  volume notification looks bad when an indicator is open

Status in Ubuntu UX:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  Fix Released

Bug description:
  I found this while testing silo 11 with krilling #88.

  Steps to reproduce:
  Open an indicator.
  Press a volume button.

  (see the attached screenshot)

  You will see that the notification appears, but it's the same color as
  the header. It has no borders, so you can't tell it's a popup. It
  looks like the header changed to something that's no properly aligned.

  phablet@ubuntu-phablet:~$ apt-cache policy indicator-sound
  indicator-sound:
    Instalados: 12.10.2+14.10.20141007-0ubuntu1
    Candidato: 12.10.2+14.10.20141007-0ubuntu1
    Tabla de versión:
   *** 12.10.2+14.10.20141007-0ubuntu1 0
  500 
http://ppa.launchpad.net/ci-train-ppa-service/landing-011/ubuntu-rtm/ 
14.09/main armhf Packages
  100 /var/lib/dpkg/status

  
  UX comment-

  When feedback bubbles ('volume notification') appear on top of a dark
  background (e.g.: notification centre, other indicator menus) we
  should use a light theme. Link to the spec:
  
https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.j3eco8r9od3s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1378618/+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 1349376] Re: vector graphic thumbnails blurry in dash on high-dpi screen

2015-08-03 Thread Sebastien Bacher
** Changed in: unity
   Importance: Undecided => Low

** Changed in: unity (Ubuntu)
   Importance: Undecided => 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/1349376

Title:
  vector graphic thumbnails blurry in dash on high-dpi screen

Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Thumbnails used in the dash are blurry for small svg images. In
  contrast to that the previews in the dash are specifically rendered
  for the dash and show in correct resolution.

  Nautilus is setup to display icons in 100% zoom level (default). In
  Nautilus or on the desktop, svg thumbnails of 24×24px svg images are
  smaller than the maximum available thumbnail area and are displayed in
  screen pixels (which is very tiny, could also be a bug).

  It appears the Unity dash looks up if a thumbnail exists for a specific file 
in ~/.cache/thumbnails/normal, chooses that thumbnail and stretches it to the 
maximum available thumbnail area in the dash.
  This makes vector graphics appear like they where raster graphics and look 
very blurry.

  Ubuntu: 14.04
  unity:  7.2.2+14.04. amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1349376/+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 1480138] Re: The background image becomes titled for a while during the logout process.

2015-08-03 Thread Sebastien Bacher
That's likely not due to unity but the way the session works, the
background is displayed by nautilus which is an application, and
nautilus is closed before the session, also the scaling xsettings is set
by unity-settings-daemon, which also exit before the setting close which
might lead to the scaling factor to be unset and things to change on
screen. Unsure it's easy to fix in the current session design...

-- 
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/1480138

Title:
  The background image becomes titled for a while during the logout
  process.

Status in unity package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04.2

  Reproducible Steps:

  1. Login Unity desktop environment.
  2. Change the scale factor to 2 in Displays of Settings.
  3. Logout

  Expected Result:

  * There is no tiled background.

  Actual Result:

  * There is a tiled background.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1480138/+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)

2015-08-03 Thread Matthew Paul Thomas
-> Medium since this is no longer requested by a customer.

** Changed in: indicator-sound (Ubuntu)
   Importance: High => Medium

** Description changed:

  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.
+ 
+ : "Starting from the
+ trailing end: * system menu * clock menu * sound menu * microphone menu
+ * network menu..."
+ 
+ : "At the bottom left corner
+ of the System Settings “Sound” panel should be “Show in the menu bar:”
+ checkboxes, “Sound volume” and “Microphone”. By default in a new user’s
+ account, “Sound volume” should be checked and “Microphone” should be
+ unchecked."
+ 
+ : "Whenever “Show in the
+ menu bar: Microphone” is checked, a microphone menu should be present in
+ the system status area..."

-- 
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 indicator-sound package in Ubuntu:
  Triaged

Bug description:
  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.

  : "Starting from the
  trailing end: * system menu * clock menu * sound menu * microphone
  menu * network menu..."

  : "At the bottom left
  corner of the System Settings “Sound” panel should be “Show in the
  menu bar:” checkboxes, “Sound volume” and “Microphone”. By default in
  a new user’s account, “Sound volume” should be checked and
  “Microphone” should be unchecked."

  : "Whenever “Show in
  the menu bar: Microphone” is checked, a microphone menu should be
  present in the system status area..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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 655580] Re: [indicators] Add a quick controls for microphone (mute/unmute)

2015-08-03 Thread Matthew Paul Thomas
Menu bar specification updated.


Sound specification updated.


** Changed in: indicator-sound (Ubuntu)
   Status: In Progress => Triaged

** Changed in: indicator-sound (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-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 indicator-sound package in Ubuntu:
  Triaged

Bug description:
  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.

  : "Starting from the
  trailing end: * system menu * clock menu * sound menu * microphone
  menu * network menu..."

  : "At the bottom left
  corner of the System Settings “Sound” panel should be “Show in the
  menu bar:” checkboxes, “Sound volume” and “Microphone”. By default in
  a new user’s account, “Sound volume” should be checked and
  “Microphone” should be unchecked."

  : "Whenever “Show in
  the menu bar: Microphone” is checked, a microphone menu should be
  present in the system status area..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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 1308037] Re: No results from application scope

2015-08-03 Thread Iain Lane
** Tags added: rls-w-incoming

-- 
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/1308037

Title:
  No results from application scope

Status in libunity:
  Confirmed
Status in Unity:
  Confirmed
Status in unity-lens-applications:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity is in a state where I don't get any results from the
  applications lens. This sometimes happens for one search but either
  re-entering the search or toggling the lens has always fixed it in the
  past for me. This time neither of these steps work.

  I'm attaching a bustle log of the problem in case that's helpful. I
  searched for "spotify", which I've got installed, and got 0 results.

  The only way to fix the issue is to log out and back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 13:29:40 2014
  InstallationDate: Installed on 2012-10-07 (554 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1308037/+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 1295908] Re: Sometimes applications stop showing up in the Dash

2015-08-03 Thread TomasHnyk
Hm, I cannot reproduce it now on 15.10 even though it used to happen
always. (I always do a clean isntall but my ~ directory is about ten
yours old).

-- 
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/1295908

Title:
  Sometimes applications stop showing up in the Dash

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
   1. Open Dash
   2. Type a name of an application installed on your system, like "calculator"
   3. press escape

  What happens: Application scope stops giving results

  What should happen: Application scope should still give results

  How to fix it once it happens:
  A)type something and either hit escape or delete what you have typed.
  B)Check "application" in filters in the Dash (it gets unchecked)

  From the comments, it seems this might have something to do with
  people having online searches disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Mar 21 19:12:19 2014
  InstallationDate: Installed on 2013-10-05 (167 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-12-10 (101 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1295908/+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 1295908] Re: Sometimes applications stop showing up in the Dash

2015-08-03 Thread Iain Lane
Forgive me that I'm re-explaining the bug, but I just want it to be
clear. When I see this (I agree it is certainly not #1308037 - when that
happens [haven't seen it for a long time though], *no* searches ever
give a result until Unity is restarted - this is about some searches not
working & retrying being okay), it's like this.

  - Open dash, search for something.
  - Usually it works but sometimes I get "Sorry, there is nothing that matches 
your search." wrongly.
  - When that happens, I can open "Filter results" and select "Applications" to 
see the results.
  - It's easy to reproduce - just hit ctrl-backspace and type the same search 
term a few times. Soon it'll not work.

I can only get this to happen on one of my two machines. Perhaps the
interesting difference is that the one which reproduces it has been
installed for a long time and the other one is quite new.

** Tags added: rls-w-incoming

-- 
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/1295908

Title:
  Sometimes applications stop showing up in the Dash

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
   1. Open Dash
   2. Type a name of an application installed on your system, like "calculator"
   3. press escape

  What happens: Application scope stops giving results

  What should happen: Application scope should still give results

  How to fix it once it happens:
  A)type something and either hit escape or delete what you have typed.
  B)Check "application" in filters in the Dash (it gets unchecked)

  From the comments, it seems this might have something to do with
  people having online searches disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Mar 21 19:12:19 2014
  InstallationDate: Installed on 2013-10-05 (167 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-12-10 (101 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1295908/+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)

2015-08-03 Thread Matthew Paul Thomas
Per spec, the sound menu already contains a microphone slider whenever a
VoIP or sound recording stream is active. That shouldn't be the case
whenever the microphone indicator is present instead.

-- 
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 indicator-sound package in Ubuntu:
  In Progress

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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 1352604] Re: [messaging-menu] clear option is painful to use if you get a lot of notifications

2015-08-03 Thread Paty Davila
** Changed in: ubuntu-ux
 Assignee: Paty Davila (dizzypaty) => Grazina (boroskograzina)

-- 
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/1352604

Title:
  [messaging-menu] clear option is painful to use if you get a lot of
  notifications

Status in Ubuntu UX:
  Fix Committed
Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  This bug is exacerbated by bug 1352602

  To reproduce:-

  1. In ubuntu system settings -> accounts, add a google or twitter account
  2. Once created, enable the "Notifications" option in the account
  3. Wait (also rebooting the phone can trigger this)
  4. Tweets / email notifications are shown as notifications

  Expected behaviour

  * Pull down the messaging indicator and find lots of notifications to clear
  * Find a button easily to clear the notifications

  Actual behaviour

  * Pull down the messaging indicator and find lots of notifications to clear
  * Have to scroll many many times to get to the bottom of a gigantic list of 
notifications before finding the [Clear all] button.

  In my opinion "clear" should be easier to find and hit

  UX comment-

  All notification list items can disappear at once by tapping on the
  fixed  Clear all button, positioned on the right hand side of the
  header. All items progressively fade away. If the notification centre
  is empty, the 'Clear all' button is not displayed. Link to the spec:
  
https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.86zuyxm7m0bp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1352604/+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 1421192] Re: [oobe] Initial boot wizard does not include timezone

2015-08-03 Thread Andreea Pirvu
The new OOBE design has Timezone included.
Please see the spec at 
https://docs.google.com/a/canonical.com/document/d/1pZ-Ro--2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s/edit?usp=sharing
 

** Changed in: ubuntu-ux
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1421192

Title:
  [oobe] Initial boot wizard does not include timezone

Status in Ubuntu UX:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  During the initial boot the Ubuntu phone asks information regarding
  various things like language, passcode etc. Timezone or date/time is
  not asked, it always defaults to UTC+0.

  This confirmed with Ubuntu 14.10(r16) and 15.04(r01)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1421192/+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 694224] Re: Synchronous notifications briefly steal focus

2015-08-03 Thread Olivier Tilloy
This causes webbrowser-app to exit fullscreen mode when adjusting volume
with media keys (see bug #1477308). Pretty annoying when watching a
fullscreen video.

** Changed in: notify-osd (Ubuntu)
   Importance: Undecided => High

-- 
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/694224

Title:
  Synchronous notifications briefly steal focus

Status in notify-osd package in Ubuntu:
  Confirmed

Bug description:
  It appears synchronous notifications (at least those for volume and
  brightness) briefly steal focus when they appear. This is quite
  problematic for games and some other applications that pause as soon
  as they lose focus. The focus stealing does not happen with normal,
  asynchronous notifications.

  Here's a quick Python program to reproduce this:

  #!/usr/bin/python
  import gtk
  import time
  def cb (wid, ev):
evtime = time.strftime ("%H:%M:%S", time.localtime())
print ("%s: Lost focus!" % evtime)
  win = gtk.Window()
  win.connect ("focus-out-event", cb)
  win.show_all()
  gtk.main()

  
  You could also just start playing Quadrapassel, then adjust your volume :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/694224/+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 793279] Re: Notifications shouldn't steal/take focus

2015-08-03 Thread Olivier Tilloy
*** This bug is a duplicate of bug 694224 ***
https://bugs.launchpad.net/bugs/694224

** This bug has been marked a duplicate of bug 694224
   Synchronous notifications briefly steal focus

-- 
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/793279

Title:
  Notifications shouldn't steal/take focus

Status in notify-osd package in Ubuntu:
  Confirmed

Bug description:
  That can be annoying because some other applications use focus. For
  example guake, it has an option to close when it loses the focus, and
  when a notification takes  it, it gets closed. Not nice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/793279/+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 1436405] Re: Duplicate menu (both unity and in-app) for Qt apps

2015-08-03 Thread Albert Astals Cid
** Also affects: appmenu-qt5 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1436405

Title:
  Duplicate menu (both unity and in-app) for Qt apps

Status in One Hundred Papercuts:
  Confirmed
Status in appmenu-qt5 package in Ubuntu:
  New
Status in libdbusmenu-qt package in Ubuntu:
  Confirmed

Bug description:
  At least konsole and khelpcenter suffers from this bug:

  Start the app inside the default Unity environment (not under KDE).
  Notice that the app's menubar appears twice.  Once in the upper row of
  the whole desktop, as expected and as it is for every Gnome app.  And
  also inside the application's window, wasting precious screen real
  estate.

  In Utopic, at least for konsole, I'm quite sure that the menu wasn't
  duplicated inside the app, it only appeared on the desktop's top Unity
  bar.

  (I'm not sure I guessed the component right; please reassign as
  appropriate.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 25 16:33:14 2015
  InstallationDate: Installed on 2012-05-30 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1436405/+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)

2015-08-03 Thread Matthew Paul Thomas
** Changed in: indicator-sound (Ubuntu)
   Status: Triaged => In Progress

-- 
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 indicator-sound package in Ubuntu:
  In Progress

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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 1387691] Re: Media Player should not be visible in the app scope and launcher

2015-08-03 Thread James Mulholland
** Description changed:

  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

-- 
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:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  Fix Released
Status in mediaplayer-app package in Ubuntu RTM:
  Fix Released
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 655580] Re: [indicators] Add a quick controls for microphone (mute/unmute)

2015-08-03 Thread Matthew Paul Thomas
** Description changed:

  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.
- 
- (This is desired for an OEM by March 2015; see private bug 1417012 for
- details.)

-- 
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 indicator-sound package in Ubuntu:
  Triaged

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.

2015-08-03 Thread Alex Milazzo
** Changed in: ubuntu-ux
   Status: Fix Released => Fix Committed

-- 
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:
  Fix Committed
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."

  
  --

  Desired resolution: Once the sound is muted icon should change but not the 
colour. We have an icon for muted 
https://www.dropbox.com/s/ciawzsrobdlk3fn/audio-output-none-panel.png?dl=0
  The behaviour has already been illustrated by MPT

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 1396986] Re: System Settings > Sound > Ringer volume - only changes ringer volume when no other sounds playing

2015-08-03 Thread Matthew Paul Thomas
** Description changed:

  Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r169 krillin
  
  System Settings > Sound > Ringer volume  is always active and always
  labelled ringer, however it only changes the ringer volume if no other
  sound is currently playing on the system.
  
- Controlling the currently active audio function is as designed for
- normal volume keys etc. but if the slider is going to have a particular
- function labelled then made it should only change the level for that
- audio function.
+ : "The “Silent Mode” switch
+ should be followed by a slider for adjusting the volume of the active
+ output role through the primary sound output. It should be labelled
+ according to the primary sound output: “Speaker:”, “Headset:”,
+ “Earpiece:”, etc."

** Changed in: ubuntu-ux
   Status: Triaged => Fix Committed

-- 
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/1396986

Title:
  System Settings > Sound > Ringer volume - only changes ringer volume
  when no other sounds playing

Status in The Avila project:
  Invalid
Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-sound package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r169 krillin

  System Settings > Sound > Ringer volume  is always active and always
  labelled ringer, however it only changes the ringer volume if no other
  sound is currently playing on the system.

  : "The “Silent Mode” switch
  should be followed by a slider for adjusting the volume of the active
  output role through the primary sound output. It should be labelled
  according to the primary sound output: “Speaker:”, “Headset:”,
  “Earpiece:”, etc."

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1396986/+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.

2015-08-03 Thread Alex Milazzo
Desired resolution updated in the description. Icon needs to change but
not the colour.

** Description changed:

  - "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."
+ 
+ 
+ --
+ 
+ Desired resolution: Once the sound is muted icon should change but not the 
colour. We have an icon for muted 
https://www.dropbox.com/s/ciawzsrobdlk3fn/audio-output-none-panel.png?dl=0
+ The behaviour has already been illustrated by MPT

** Changed in: ubuntu-ux
   Status: Triaged => Fix Released

-- 
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:
  Fix Committed
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."

  
  --

  Desired resolution: Once the sound is muted icon should change but not the 
colour. We have an icon for muted 
https://www.dropbox.com/s/ciawzsrobdlk3fn/audio-output-none-panel.png?dl=0
  The behaviour has already been illustrated by MPT

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 1378350] Re: Need to allow multiple apps to handle the same url patterns

2015-08-03 Thread Femma
** Changed in: ubuntu-ux
 Assignee: Femma (femma) => Matthew Paul Thomas (mpt)

** Changed in: ubuntu-ux
 Assignee: Matthew Paul Thomas (mpt) => Femma (femma)

** Description changed:

  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 ;)
  
  Design resolution _
  
  Case 1: If no email client is installed and a user clicks on a 'mail to'
- link, the user should be re-directed to the Ubuntu store and prompted to
- download the Dekko app.
+ link, the user should be prompted to download the Dekko app.
  
  Case 2: If the user has Dekko installed, then clicking on the 'mail to'
  link should open the Dekko client --> compose mail screen to the 'mail
  to' address.
  
  Case 3: If the user has Dekko and Gmail installed, the 'mail to' link by
  default should open in the Dekko client. However, the user can change
  their mail client preferences in system settings.
  
  Case 4: If the user has Gmail and another mail client installed, the
  'mail to' link should default to the first client that was installed on
  their device (which would be the default mail client preference in
  system settings -  this can be changed by the user via system settings).
  
  Notes:
- 1. Wherever the user has not actively changed a mail client preference and 
Dekko is installed on their device, the default 'mail to' client should be 
Dekko. 
+ 1. Wherever the user has not actively changed a mail client preference and 
Dekko is installed on their device, the default 'mail to' client should be 
Dekko.
  2. When clicking on a 'mail to' link, the user's expectation is to have this 
link open in a relevant client (unless it is case 1), therefore this should be 
the case and any mail preference choices the user can perform via system 
settings rather than being presented with multiple choice options of which 
client to open the URL in.

** Changed in: ubuntu-ux
 Assignee: Femma (femma) => Matthew Paul Thomas (mpt)

-- 
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:
  Need to allow multiple apps to handle the same url patterns

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  In Progress
Status in content-hub package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  New
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 ;)

  Design resolution _

  Case 1: If no email client is installed and a user clicks on a 'mail
  to' link, the user should be prompted to download the Dekko app.

  Case 2: If the user has Dekko installed, then clicking on the 'mail
  to' link should open the Dekko client --> compose mail screen to the
  'mail to' address.

  Case 3: If the user has Dekko and Gmail installed, the 'mail to' link
  by default should open in the Dekko client. However, the user can
  change their mail client preferences in system settings.

  Case 4: If the user has Gmail and another mail client installed, the
  'mail to' link should default to the first client that was installed
  on their device (which would be the default mail client preference in
  system settings -  this can be changed by the user via system
  settings).

  Notes:
  1. Wherever the user has not actively changed a mail client preference and 
Dekko is installed on their device, the default 'mail to' client should be 
Dekko.
  2. When clicking on a 'mail to' link, the user's expectation is to have this 
link open in a relevant client (unless it is case 1), therefore this should be 
the case and any mail preference choices the user can perform via system 
settings rather than being presented with multiple choice options of which 
client to open the URL in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+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 1378350] Re: Need to allow multiple apps to handle the same url patterns

2015-08-03 Thread Femma
** Changed in: ubuntu-ux
   Status: Fix Committed => In Progress

-- 
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:
  Need to allow multiple apps to handle the same url patterns

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  In Progress
Status in content-hub package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  New
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 ;)

  Design resolution _

  Case 1: If no email client is installed and a user clicks on a 'mail
  to' link, the user should be re-directed to the Ubuntu store and
  prompted to download the Dekko app.

  Case 2: If the user has Dekko installed, then clicking on the 'mail
  to' link should open the Dekko client --> compose mail screen to the
  'mail to' address.

  Case 3: If the user has Dekko and Gmail installed, the 'mail to' link
  by default should open in the Dekko client. However, the user can
  change their mail client preferences in system settings.

  Case 4: If the user has Gmail and another mail client installed, the
  'mail to' link should default to the first client that was installed
  on their device (which would be the default mail client preference in
  system settings -  this can be changed by the user via system
  settings).

  Notes:
  1. Wherever the user has not actively changed a mail client preference and 
Dekko is installed on their device, the default 'mail to' client should be 
Dekko. 
  2. When clicking on a 'mail to' link, the user's expectation is to have this 
link open in a relevant client (unless it is case 1), therefore this should be 
the case and any mail preference choices the user can perform via system 
settings rather than being presented with multiple choice options of which 
client to open the URL in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+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 1378350] Re: Need to allow multiple apps to handle the same url patterns

2015-08-03 Thread Femma
>From a UX and design point of view Dekko should be the Ubuntu phone eco-
system's client of choice. We are currently working on making this
happen from the conversations I have had.

The system settings UI would need to be updated to reflect this.

By default mail to including imap should translate to default mail
client, unless specified by user in system settings.

I hope this helps.

** Changed in: ubuntu-ux
   Status: Confirmed => Fix Committed

-- 
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:
  Need to allow multiple apps to handle the same url patterns

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in content-hub package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  New
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 ;)

  Design resolution _

  Case 1: If no email client is installed and a user clicks on a 'mail
  to' link, the user should be re-directed to the Ubuntu store and
  prompted to download the Dekko app.

  Case 2: If the user has Dekko installed, then clicking on the 'mail
  to' link should open the Dekko client --> compose mail screen to the
  'mail to' address.

  Case 3: If the user has Dekko and Gmail installed, the 'mail to' link
  by default should open in the Dekko client. However, the user can
  change their mail client preferences in system settings.

  Case 4: If the user has Gmail and another mail client installed, the
  'mail to' link should default to the first client that was installed
  on their device (which would be the default mail client preference in
  system settings -  this can be changed by the user via system
  settings).

  Notes:
  1. Wherever the user has not actively changed a mail client preference and 
Dekko is installed on their device, the default 'mail to' client should be 
Dekko. 
  2. When clicking on a 'mail to' link, the user's expectation is to have this 
link open in a relevant client (unless it is case 1), therefore this should be 
the case and any mail preference choices the user can perform via system 
settings rather than being presented with multiple choice options of which 
client to open the URL in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+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 1378350] Re: Need to allow multiple apps to handle the same url patterns

2015-08-03 Thread Femma
We may have to create a new project from this.

-- 
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:
  Need to allow multiple apps to handle the same url patterns

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in content-hub package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  New
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 ;)

  Design resolution _

  Case 1: If no email client is installed and a user clicks on a 'mail
  to' link, the user should be re-directed to the Ubuntu store and
  prompted to download the Dekko app.

  Case 2: If the user has Dekko installed, then clicking on the 'mail
  to' link should open the Dekko client --> compose mail screen to the
  'mail to' address.

  Case 3: If the user has Dekko and Gmail installed, the 'mail to' link
  by default should open in the Dekko client. However, the user can
  change their mail client preferences in system settings.

  Case 4: If the user has Gmail and another mail client installed, the
  'mail to' link should default to the first client that was installed
  on their device (which would be the default mail client preference in
  system settings -  this can be changed by the user via system
  settings).

  Notes:
  1. Wherever the user has not actively changed a mail client preference and 
Dekko is installed on their device, the default 'mail to' client should be 
Dekko. 
  2. When clicking on a 'mail to' link, the user's expectation is to have this 
link open in a relevant client (unless it is case 1), therefore this should be 
the case and any mail preference choices the user can perform via system 
settings rather than being presented with multiple choice options of which 
client to open the URL in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+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 1420758] Re: [Indicators] The indicator envelop icon should not change colour to green and only be present when there are new notifications.

2015-08-03 Thread Paty Davila
This bug is conflicting with bug #1450894, and that last one has changed
the status to fix released. Therefore this bug is not longer valid.

** Changed in: ubuntu-ux
   Status: Fix Committed => Won't Fix

-- 
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:
  Won't Fix
Status in indicator-messages package in Ubuntu:
  Confirmed

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 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message

2015-08-03 Thread Paty Davila
** 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-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 Canonical System Image:
  Fix Released
Status in Ubuntu theme:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

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.

  --DESIGN RESOLUTION---

  Please use the current ubuntu theme green to indicate that there is a
  new message - #3FB24F, the same green as we use for the battery icon
  in indicators.

  Change the LED light to green as well.

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 993161] Re: Order of month and day of month are reversed

2015-08-03 Thread Anne
Fix released in Ubuntu 14.04 Trusty Tahr (see attachment).

https://translations.launchpad.net/ubuntu/trusty/+source/indicator-
datetime/+pots/indicator-datetime/fr/5/+translate

** Attachment added: "fix.png"
   
https://bugs.launchpad.net/ubuntu-translations/+bug/993161/+attachment/4438129/+files/fix.png

** Changed in: ubuntu-translations
   Status: Triaged => 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/993161

Title:
  Order of month and day of month are reversed

Status in Indicator Date and Time:
  Invalid
Status in Ubuntu Translations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Invalid

Bug description:
  mer. mai 2 12:04
  Should be : mer. 2 mai 12:04

  Impossible to modify.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/993161/+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