[Ubuntu-translations-coordinators] [Bug 1159787] Re: Right clicking on launcher says Empty Trash... when should be Rubbish Bin in UK translation

2013-04-02 Thread Greg Auger
** Changed in: unity (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: ubuntu-translations
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1159787

Title:
  Right clicking on launcher says Empty Trash... when should be
  Rubbish Bin in UK translation

Status in Ubuntu Translations:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  These sort of translation bugs seem to be a recurring issue each
  release (but at the moment in Raring elsewhere in Unity/Nautilus  the
  correct Rubbish Bin is being used).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.03.20-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: 346c69198d9a34d2dea85736f0dd6571
  CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,place,compiztoolbox,session,resize,gnomecompat,imgpng,move,regex,grid,vpswitch,unitymtgrabhandles,animation,obs,wall,workarounds,wobbly,fade,scale,expo,ezoom,unityshell]
  Date: Mon Mar 25 13:24:30 2013
  InstallationDate: Installed on 2012-07-14 (253 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-03-21 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1159787/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-translations-coordinators] [Bug 1138285] Re: [Incorrect Translation] 'Colors Gradients' should be 'Colours Gradients' in English (UK)

2013-03-05 Thread Greg Auger
This is a regression since 12.10

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1138285

Title:
  [Incorrect Translation] 'Colors  Gradients' should be 'Colours 
  Gradients' in English (UK)

Status in Ubuntu Translations:
  New
Status in “language-pack-gnome-en” package in Ubuntu:
  New

Bug description:
  In System Settings  Appearances  Background  Drop Down  Colors 
  Gradients

  
  'Colors  Gradients' should be 'Colours  Gradients' in English (UK)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
  Uname: Linux 3.8.0-8-generic x86_64
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  Date: Fri Mar  1 18:10:00 2013
  InstallationDate: Installed on 2013-02-11 (18 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1138285/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-translations-coordinators] [Bug 950136] Re: multimonitor, launcher: Provide an option to display either a single launcher or a launcher on each display in a multi-monitor environment

2012-03-24 Thread Greg Auger
Unfortunately, I think that fixing this has caused another the Displays
setting to be confusing:  Bug #963731

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
https://bugs.launchpad.net/bugs/950136

Title:
  multimonitor, launcher: Provide an option to display either a single
  launcher or a launcher on each display in a multi-monitor environment

Status in Ayatana Design:
  Triaged
Status in Ubuntu Translations:
  New
Status in Unity:
  Fix Released
Status in Unity 2D:
  Fix Released
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “ubuntu-docs” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-2d” package in Ubuntu:
  Fix Released

Bug description:
  Provide an option to display either a single launcher or a launcher on
  each display in a multi-monitor environment.

  Add the option 'Launcher placement' to the Displays panel.
  A drop-down list provides the following options:
  Display name 1
  Display name 2
  ...
  All displays

  By default, the primary display will be selected, to display just a
  single Launcher on the primary display.

  A fallback solution is proposed where proprietary drivers report a single 
display in the Displays panel (where multiple displays are connected). The 
drop-down list options revert to:
  Primary display
  All displays

  Please see addendum to System Settings specification:
  
https://docs.google.com/a/canonical.com/document/d/1b3CwE3Wemr347fTxNcu7ixEQBK4YD8JF2pyv5pxiY0U/edit

  This addendum also provides a solution proposal for bug 946104:
  'multimonitor: Please give me a way to turn off sticky monitor edges':
  https://bugs.launchpad.net/ayatana-design/+bug/946104

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/950136/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-translations-coordinators] [Bug 824099] Re: Max GL texture size can break multi-head

2012-03-14 Thread greg
I think it's unlikely this bug will ever be solved, the warning is
good enough. While it's possible to work around maximum texture size
limitations, this does not come without overhead, and that's on old GPUs
with limited performance to start with. All modern and most not-that-
modern GPUs support at least 4096x4096 textures.

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/824099

Title:
  Max GL texture size can break multi-head

Status in Unity:
  Triaged
Status in Unity Distro Priority:
  Fix Committed
Status in “compiz” package in Ubuntu:
  Invalid
Status in “gnome-desktop3” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Triaged
Status in “compiz” source package in Oneiric:
  Won't Fix
Status in “gnome-desktop3” source package in Oneiric:
  Fix Released
Status in “unity” source package in Oneiric:
  Won't Fix
Status in “compiz” source package in Precise:
  Triaged
Status in “gnome-desktop3” source package in Precise:
  Fix Released
Status in “unity” source package in Precise:
  Triaged

Bug description:
  There's a longstanding issue (see the duplicate bug #555641) with
  Compiz and multi-monitor setups with any combined dimension larger
  than the maximum GL texture size.  It used to be the case that this
  would simply crash compiz, but mesa now has code to fallback to
  software rendering for those cases.  Unfortunately, this rendering is
  unacceptably slow (on the order of 10s of seconds per frame),
  particularly since the only hardware that will realistically hit this
  limit is netbook hardware with the associated anaemic CPU.  It also
  appears to be broken in some cases (see bug #830949), although I can't
  reproduce that myself.

  The Compiz Copy to Texture plugin can break textures up into = max
  texture size chunks, allowing hardware rendering to work with these
  large framebuffers.  This is insufficient for Unity, though, which
  also needs a way to break up its FBOs.

  For Oneiric we should patch g-s-d's xrandr plugin to disallow setting
  a multi-monitor configuration with any dimension = max texture size
  when Unity is running.  Additionally, the display capplet should not
  allow a resolution to be explicitly set that will break Unity.  For P
  this should be dropped in favour of enabling Compiz's Copy to
  Texture plugin and fixing Unity.

  String Freeze Exception Request:
  This patch adds a new failure mode and explanatory error message to 
gnome-desktop's randr handling.  This new message is required to explain to the 
user why their multi-head setup request has been rejected, and what can be done 
about it.

  Original report:
  THIS IS A MASTER BUG OF FOUR DIFFERENT BUGS:

  [nVidia] https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/830955
  [Intel N10] https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/830949
  [Intel Arrandale, Mobile 4 Series] 
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/830952
  [ATI] https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/830953

  Oneiric Alpha 3 installed on this system.  Under testing, one test is
  to plug in an external monitor and ensure that external video
  functions properly.  On this EeePC, it does not.  (See photo attached
  to this bug).

  Once the external montior is plugged in, both the primary display and
  the external display are horribly garbled.  The only thing that exists
  on the screen that's remotely readable is the panel at the top.  The
  rest of the desktop area is just a mess.

  Affected systems and GPUs:

  Dell Vostro 1014 (Intel Mobile 4 Series)
  Dell Vostro 1015 (Intel Mobile 4 Series)
  Lenovo Thinkpad Edge 11 (Intel Arrandale)
  Lenovo Thinkpad Edge 14 (M92 [Mobility Radeon HD 4500/5100 Series])
  Lenovo Thinkpad Edge 15 (Intel Arrandale)
  Lenovo Thinkpad SL410 (Intel Mobile 4 Series)
  Lenovo Thinkpad Edge 15 (ATI Technologies Inc M880G [Mobility Radeon HD 4200])
  Lenovo Thinkpad L412 (Intel Arrandale)
  Lenovo Thinkpad Edge 11 (ATI Technologies Inc: M880G [Mobility Radeon HD 
4200])
  Lenovo Thinkpad X220 (Intel Arrandale)
  Dell Vostro 1520 (Intel Mobile 4 Series)
  Dell Vostro 1720 (Intel Mobile 4 Series)
  Dell Studio XPS 1340 (nVidia Corporation: GT218 [GeForce G210M])
  Dell Inspiron 1545 (Intel Mobile 4 Series)
  Dell Studio XPS 1340 (nVidia Corporation: G98 [GeForce 9200M GS])
  Dell Vostro 3300 (Intel Arrandale)
  Dell Vostro 3500 (Intel Arrandale)
  Dell Vostro 3700 (Intel Arrandale)
  Dell Precision M4500 (nVidia Corporation: GT215 [Quadro FX 1800M])
  Dell Latitude E6410 (nVidia Corporation: GT218 [NVS 3100M])
  Toshiba Tecra A11/M11 (Intel Arrendale)
  Toshiba Tecra S11/M11 (nVidia Corporation: GT218 [NVS 2100M])
  Dell Latitude 2110 (Intel Corporation: N10 Family Integrated Graphics 
Controller)
  Dell Latitude 13 (Intel Mobile 4 Series)
  Dell Vostro 3400 (Intel Arrandale)
  Dell Vostro V13 (Intel Mobile 4 Series)