[Touch-packages] [Bug 1324104] Re: Ctrl + Super + D hides windows but still resizable when cursor over border

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1324104

Title:
  Ctrl + Super + D hides windows but still resizable when cursor over
  border

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  If You Press Ctrl + Super + D Shortcut To minimize all windows
  it works but when you move the cursor you will see it change
  to an arrow for resizing the hidden windows when the cursor
  is in the location of the border of the hidden windows

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  a new crash of lockup.

  This particular change could possibly introduce a regression in which
  no windows are re-sizable.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use with no sign of regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1324104/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1373695] Re: Not resizable windows can be moved by dragging them on every edge

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1373695

Title:
  Not resizable windows can be moved by dragging them on every edge

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  1. Open a non resizable window such as Calculator or Unity Control Center
  2. Move the mouse to the edge of the window, outside the window itself
     but in the area that is close at least 10 px.
  3. Press the mouse and start to drag

  Expected behavior:
  4. nothing happens

  Actual behavior
  5. the hand cursor is shown and window can be dragged around
  As side effect, if LIMs are enabled, moving the mouse over a window edge 
makes the menus to show.

   [ Test Case ]

  See above.

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introduce new
  crashed or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1373695/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1384958] Re: Ubuntu Desktop title is moved right as if the window buttons were there

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1384958

Title:
  Ubuntu Desktop title is moved right as if the window buttons were
  there

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  1. Open a maximized window
  2. Hit Super+s
  3. The Ubuntu Desktop title is moved some pixels to the right, as shown in 
the attached screenshot.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been included in the Ubuntu Vivid Vervet dev
  release for some time without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1384958/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1385285] Re: Clicking in panel elements when the expo is active, performs to the maximized windows

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1385285

Title:
  Clicking in panel elements when the expo is active, performs to the
  maximized windows

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  1. Open a maximized window (it must be focused when using global menus, not 
with LIMs)
  2. Hit Super+s to enter in expo mode
  3. Click in the panel, in different areas and you'll get:
     - top-left corner buttons will work (although when not visible)
     - grab area will make possible to grab and focus (when in LIM mode) a 
window

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been in the Ubuntu Vivid Vervet dev release form
  several weeks without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1385285/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1308540] Re: [lockscreen] the password entry is not shared between screens

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1308540

Title:
  [lockscreen] the password entry is not shared between screens

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Using the Unity lockscreen on a multiple-screen session results in the
  password field being cleared every time different screen is focused.

  [Test Case]

  Using trusty candidate on a dual monitor config
  - log into unity
  - lock screen
  - start typing your password on one screen
  - move the pointer on the other screen

  - the entry is displayed empty

  Ideally the same entry would be move so you can keep typing even if
  you happened to have move the focus, that's what lightdm/unity-greeter
  is doing

  [Regression Potential]

  Any modification to the password dialogs could result in the inability
  to unlock the screen or make passwords available in cleartext.  Care
  has been take to avoind introducing such situations with this change.

  [Other info]

  The Ubuntu 14.04 LTS SRU fix has been cherry-picked from the Ubuntu
  14.10 release, where it has been in production use for a few months.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308540/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1198502] Re: compiz crashed with SIGSEGV in operator[]()

2015-02-11 Thread Stephen M. Webb
Stack trace show a signal raised on an invalid object, but unfortunately
there is just not enough additional information to perform an effective
analysis of this problem.  Closing bug since further investigation and
resolution is no longer possible.

** Changed in: unity (Ubuntu)
   Status: New = Invalid

** Changed in: unity
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1198502

Title:
  compiz crashed with SIGSEGV in operator[]()

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I was typing in the search box of Ubuntu's Dash Home, the main
  ubuntu finder search box.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unity 5.18.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Jul  6 10:45:01 2013
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f679534c57e:mov0x8(%rsi),%rax
   PC (0x7f679534c57e) ok
   source 0x8(%rsi) (0x1000a) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/compiz/libunityshell.so
   ?? () from /usr/lib/compiz/libunityshell.so
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout floppy fuse lpadmin netdev plugdev 
powerdev sambashare scanner tomcat6 video

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1198502/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1237132] Re: Change Show Desktop icon option label when this option is in the state where it will reverse the prior show desktop action.

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1237132

Title:
  Change Show Desktop icon option label when this option is in the
  state where it will reverse the prior show desktop action.

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  The label on the show desktop / show windows icon in the Unity
  Switcher does not change even when the function of the button has
  changed.  This can be just a little bit confusing.

  [ Test Case ]

  (1) Open several applications with windows.
  (2) Using Alt-Tab, bring up the Switcher and keeping the Alt key depressed 
and using the Tab key, navigate to the leftmost icon, which should be labeled 
Show Desktop.  Release all keys.  Only the desktop should be displayed.
  (3) Again using Alt-Tab, navigate back to the leftmost icon.  Its label 
should have changed to Restore Windows to indicate its changed function.

  [ Regression Potential ]

  About the worst that could happen is the incorrect label is applied to
  the icon in the Switcher.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU has been cherry-picked from the Ubuntu 14.04
  release where it has shown to be stable.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1066971] Re: Launcher count overflows when displaying 5+ digits

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1066971

Title:
  Launcher count overflows when displaying 5+ digits

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  What happens:

  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3. The count becomes an unreadable mess.

  What should happen:

  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3a. The count stretches, allowing for up to 8-9 digits to be displayed.
  3b. The count is truncated, still showing the most important parts of the 
number.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any software change in the Unity desktop shell has the potential to
  introduce desktop shell crashes or lockups.

  [ Other Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time with apparent
  regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1066971/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1361751] Re: Launcher Icon shortcut labels don't honor text scaling

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1361751

Title:
  Launcher Icon shortcut labels don't honor text scaling

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  Text scaling value is ignored by icons overlay text.

   - From u-c-c → accessibility → enable Big Text option

  Icons overlay text should honor that setting.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for several weeks without
  apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1361751/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1350331] Re: Dash doesn't close when Drag and dropping from it to another window

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1350331

Title:
  Dash doesn't close when Drag and dropping from it to another window

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

   1. Open one nautilus window and another window, so that nautilus is not 
focused
   2. Open the dash File lens (Super+F)
   3. Start dragging a file from that to the nautilus launcher icon
   4. Wait some delay

  Expected Result:
   4. The dash is closed and nautilus window is focused

  Actual result:
   4. The nautilus window is focused, but the dash is not closed

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change in Unity has the potential to introduce crashes in
  Unity.

  This particular fix has the potential to not close the dash after a
  drag-and-drop operation, which could conceivably result in a desktop
  lock-up requiring a restart.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU fix was cherry-picked from Ubuntu 14.10 where
  it has been in production use for some time without apparent
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1350331/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1361713] Re: Launcher icon count does not honour the text scaling

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1361713

Title:
  Launcher icon count does not honour the text scaling

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  Text scaling value is ignored by icon count (emblem).

   - From u-c-c → accessibility → enable Big Text option

  Icon count text should be bigger.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any modification to Unity desktop shell sources has the potential to
  introduce desktop shell crashes or lockups.

  [ Addition Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time with no apparent
  regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1361713/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1299741] Re: Shadows shouldn't wrap around to other workspaces/monitors

2015-02-11 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1299741

Title:
  Shadows shouldn't wrap around to other workspaces/monitors

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in compiz package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Fix Released
Status in compiz source package in Trusty:
  Invalid
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  Window shadows can be seen on adjacent workspaces.

  [ Test Case ]

  To reproduce, launch a whole bunch (10, 20, a lot) of windows on
  workspace 2, and position them on or near the right edge.  Then switch
  to workspace 1, and observe the massive black blob on the left of the
  screen.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  a new crash or lockup.

  [ Other Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time without apparent
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1299741/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1423687] Re: compiz crashed with SIGSEGV in unity::MultiActionList::Initiate()

2015-02-19 Thread Stephen M. Webb
** Also affects: unity
   Importance: Undecided
   Status: New

** Changed in: unity
   Importance: Undecided = Medium

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1423687

Title:
  compiz crashed with SIGSEGV in unity::MultiActionList::Initiate()

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Disable Animations and enable them after restart of PC affect this.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150205-0ubuntu1
  Uname: Linux 3.18.3-031803-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 19 21:31:22 2015
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-10-16 (125 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141016)
  ProcCmdline: compiz
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, 
std::allocatorCompOption  const, int) const () from 
/usr/lib/compiz/libunityshell.so
   unity::MultiActionList::InitiateAll(std::vectorCompOption, 
std::allocatorCompOption  const, int) const () from 
/usr/lib/compiz/libunityshell.so
   unity::PluginAdapter::InitiateScale(std::string const, int) () from 
/usr/lib/compiz/libunityshell.so
   unity::PluginAdapter::ScaleWindowGroup(std::vectorunsigned long, 
std::allocatorunsigned long  const, int, bool) () from 
/usr/lib/compiz/libunityshell.so
   unity::launcher::ApplicationLauncherIcon::Spread(bool, int, bool) () from 
/usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in unity::MultiActionList::Initiate()
  UpgradeStatus: Upgraded to vivid on 2015-01-23 (27 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1423687/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1423855] Re: Unity can't show the global menu item for some gnome apps

2015-02-20 Thread Stephen M. Webb
** Also affects: unity
   Importance: Undecided
   Status: New

** Changed in: unity
   Status: New = Triaged

** Changed in: unity (Ubuntu)
   Status: New = Triaged

** Changed in: unity
   Importance: Undecided = High

** Changed in: unity (Ubuntu)
   Importance: Undecided = High

** Changed in: unity
 Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity
Milestone: None = 7.3.2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1423855

Title:
  Unity can't show the global menu item for some gnome apps

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

Bug description:
  Unity can't show the global menu item for some gnome apps.

  For example, the 'terminal' menu for gnome-terminal, or the
  'calculator' menu for gnome-calculator cannot be opened.  Other menus
  can be displayed (file, edit,...)

  This is a recent regression I think.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Feb 20 21:14:01 2015
  InstallationDate: Installed on 2015-01-31 (20 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1423855/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 973932] Re: Disabling 'below' display does not reposition windows properly

2015-01-30 Thread Stephen M. Webb
** Changed in: unity
   Status: Expired = Triaged

** Changed in: unity (Ubuntu)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu)
   Status: Expired = Triaged

** Changed in: unity
   Importance: Undecided = Medium

** Changed in: unity
Milestone: None = 7.3.2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/973932

Title:
  Disabling 'below' display does not reposition windows properly

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

Bug description:
  [Problem]
  In a multihead config with one monitor above the other, if the lower monitor 
is disabled the windows on that screen aren't moved to the still-active display.

  [Test Case]
  0.  Attach laptop (LVDS1) to an external display (VGA1).
  1.  In the GNOME display properties applet, set the LVDS1 beneath VGA1.
  2.  Move to the lower left desktop (ctrl+alt+down)
  3.  Open one gnome terminal window on each monitor.
  4.  In the upper (VGA1) gnome terminal window type:
  xrandr --output LVDS1 --off
     (Alternatively, bring up the gnome display properties applet and shut the 
laptop display off there)
  5.  With the LVDS turned off, count the number of gnome terminal windows 
visible on VGA1
  6. Using either xrandr or gnome, re-enable LVDS1 to the above/below 
arrangement
  7.  With the LVDS re-enabled, count the number of gnome terminals visible on 
VGA1 and LVDS1

  Expected:  2, then 1/1
  Actual:
     Gnome Classic (No Effects):  2, then 1/1
     Gnome Classic (With Effects): 2, then 1/1
 Unity2D: 2, then 1/1
     Unity:  1, then 1/1

  Other findings...
  A.  On Unity, with LVDS1 off the missing gnome terminal window is 
inaccessible.  It can be recovered in various ways, but it's fairly confusing.

  B.  If step #2 is skipped and the test performed in the upper left
  desktop, Unity will place the lower windows into the lower left
  desktop.

  C.  On Unity, repeated testing of this seems to scramble the window
  positions to some extent.  The same effect does not appear to occur
  with metacity; windows generally get placed back where they'd been
  before.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic i686
  ApportVersion: 2.0-0ubuntu4
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
  Date: Thu Apr  5 05:27:33 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110921.2)
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2011-11-22 (135 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/973932/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1414230] Re: v14.04 screen garbled upon restart with external monitor

2015-01-24 Thread Stephen M. Webb
Sounds like it may be a video driver bug.  Let's start by collecting
information on your system.  If you would, please open a terminal
application and type the command apport-collect 1414230.  This will
(hopefully) gather information on your system hardware and software
configuration and attach it to this bug for further analysis.

** Changed in: unity (Ubuntu)
   Status: New = Incomplete

** Changed in: unity (Ubuntu)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1414230

Title:
  v14.04 screen garbled upon restart with external monitor

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  I have installed Ubuntu 14.04 on a Acer Aspire One 722. Everything
  works fine on the laptop by itself. But if I connect the laptop to an
  external monitor (a HDTV in this instance) via a HDMI cable, the
  display on the laptop screen and on the external monitor work fine:

  1)  until I close the screen of the laptop while the laptp is still
  on, let it go to sleep, and then open the screen and restart. At that
  point the laptop and external montor screens are black with some
  garbled characters. There is no way to recover the laptop but shut it
  down and perform a cold boot.

  2) and continue to do so if I use the suspend command (from the drop
  down menu from the top right corner of the screen). The laptop and the
  external monitor go dark when the computer suspends. Upon waking both
  the laptop screen and the external monitor work fine. Needless to say
  closing the lid after using the suspend command makes no difference.

  Any clues on what could be happening when I close the lid of the
  laptop to suspend the laptop?

  Ubuntu information: 64 bit version
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION=Ubuntu 14.04.1 LTS

  viswa@netbook:~$ uname -r
  3.11.0-18-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1414230/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1404730] Re: Dash: some icons are scaled incorrectly

2015-01-06 Thread Stephen M. Webb
** Changed in: unity
Milestone: None = 7.3.2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1404730

Title:
  Dash: some icons are scaled incorrectly

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

Bug description:
  Please see the enclosed screenshot - the software updater icon is
  oversized compared to others displayed in Dash

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20141216-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Dec 21 21:13:29 2014
  InstallationDate: Installed on 2014-11-27 (24 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141123)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1404730/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1059275] Re: reset now deprecated, man page not updated

2015-01-05 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Branch unlinked: lp:~unity-team/unity/trusty-1059275

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1059275/+attachment/4292432/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

** Description changed:

- Run unity --reset as recommended by the man page:-
+ [ Impact ]
  
- ERROR: the reset option is now deprecated
+ The manpage for the unity command reflects the actual available
+ options.
  
- Man page says:-
+ [ Test Case ]
  
---reset   This option allows the user to reset profile
- parameters in compiz and restart the Unity shell with default settings.
+ Run man unity.  It should not say --reset is a valid command-line
+ switch (option).
+ 
+ [ Regression Potential ]
+ 
+ This is a change to the man page.  I suppose it might be a regression if
+ the man page still does not match the option available in the 'unity'
+ command.  Not terribly serious.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1059275

Title:
  reset now deprecated, man page not updated

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  The manpage for the unity command reflects the actual available
  options.

  [ Test Case ]

  Run man unity.  It should not say --reset is a valid command-line
  switch (option).

  [ Regression Potential ]

  This is a change to the man page.  I suppose it might be a regression
  if the man page still does not match the option available in the
  'unity' command.  Not terribly serious.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1059275/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1407708] Re: Additionally Installed scopes disappear on reboot

2015-01-05 Thread Stephen M. Webb
** Package changed: unity (Ubuntu) = unity8 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1407708

Title:
  Additionally Installed scopes disappear on reboot

Status in unity8 package in Ubuntu:
  New

Bug description:
  On krillin #184 ubuntu-touch/ubuntu-rtm/14.09-proposed

  Steps to reproduce.

  1. Visit store
  2. Install many scopes, examples:- Cinema, Discerning Duck, GMail Scope, 
Mixcloud Scope, Nearby, Places, RSS Feeds, Stellar, Swiss Public Transport 
Information, Your Shot
  (I installed all of them to review them for a contest)
  3. Favorite all of them so you can easily switch between them
  Note they all work
  4. Reboot phone

  Result

  All the above installed scopes all disappear from the scopes overview
  screen and are no longer favorited.

  Expected result

  Scopes still show up and are favorited as they were before reboot

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity (not installed)
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Mon Jan  5 15:03:17 2015
  InstallationDate: Installed on 2014-12-18 (17 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1407708/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1353070] Re: Launcher icon emblems (count) do not scale to match DPI settings

2015-01-05 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

- The launcher icons count bubble is not properly scaled to match current
- monitor DPI
+ [ Impact ]
+ The launcher icons count bubble is not properly scaled to match current 
monitor DPI
+ 
+ [ Test Case ]
+ 
+ (1) Adjust the monitor scaling factor to 1.88 using the System Settings.
+ (2) observe the scaling of an emblem (eg. unread-email count in your email 
client)
+ 
+ [ Regression Potential ]
+ 
+ Any code change in Unity has the potential to cause a crash or other
+ instability in the desktop shell.
+ 
+ This specific change has the potential to render the emblems unreadable,
+ or or to introduce visible artifacts such as blurry edges to the text.
+ 
+ [ Other Info ]
+ 
+ The Ubuntu 14.04 LTS SRU fix was cherry-picked from Ubuntu 14.10 where
+ it has been in production use for some time without any regressions.

** Branch unlinked: lp:~unity-team/unity/trusty-1066971

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/unity/+bug/1353070/+attachment/4292502/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1353070

Title:
  Launcher icon emblems (count) do not scale to match DPI settings

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]
  The launcher icons count bubble is not properly scaled to match current 
monitor DPI

  [ Test Case ]

  (1) Adjust the monitor scaling factor to 1.88 using the System Settings.
  (2) observe the scaling of an emblem (eg. unread-email count in your email 
client)

  [ Regression Potential ]

  Any code change in Unity has the potential to cause a crash or other
  instability in the desktop shell.

  This specific change has the potential to render the emblems
  unreadable, or or to introduce visible artifacts such as blurry edges
  to the text.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU fix was cherry-picked from Ubuntu 14.10 where
  it has been in production use for some time without any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1353070/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1361713] Re: Launcher icon count does not honour the text scaling

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Branch unlinked: lp:~unity-team/unity/trusty-1066971

** Description changed:

+ [ Impact ]
+ 
  Text scaling value is ignored by icon count (emblem).
  
-  - From u-c-c → accessibility → enable Big Text option
+  - From u-c-c → accessibility → enable Big Text option
  
  Icon count text should be bigger.
+ 
+ [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any modification to Unity desktop shell sources has the potential to
+ introduce desktop shell crashes or lockups.
+ 
+ [ Addition Info ]
+ 
+ The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
+ where it has been in production use for some time with no apparent
+ regressions.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1361713/+attachment/4292935/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1361713

Title:
  Launcher icon count does not honour the text scaling

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Text scaling value is ignored by icon count (emblem).

   - From u-c-c → accessibility → enable Big Text option

  Icon count text should be bigger.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any modification to Unity desktop shell sources has the potential to
  introduce desktop shell crashes or lockups.

  [ Addition Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time with no apparent
  regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1361713/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1276177] Re: Applications using client-side decorations are not resizable in Unity

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1276177

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1276177

Title:
  Applications using client-side decorations are not resizable in Unity

Status in Themes for Ubuntu:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Debian:
  Confirmed

Bug description:
  [ Impact ]

  GNOME applications that use client-side decorations can't be resized
  on Unity. I think it's because the frame extents hint is not
  supported.

  gnome-clocks and gnome-tweak-tool are two apps in the archive that
  have this problem.

  [ Test Case ]

  Run one of the abovementioned applications.  Their windows should be
  resizable.

  [ Regression Potential ]

  Any modifications to the Unity desktop shell could potentially
  introduce new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity, where it has been in production use in Ubuntu Vivid Vervet
  dev release for some time without apparent regression.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1066971] Re: Launcher count overflows when displaying 5+ digits

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

+ [ Impact ]
+ 
  What happens:
  
  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3. The count becomes an unreadable mess.
  
- What shoul happen:
+ What should happen:
  
  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3a. The count stretches, allowing for up to 8-9 digits to be displayed.
  3b. The count is truncated, still showing the most important parts of the 
number.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 12.10
- Package: unity 6.8.0-0ubuntu2
- ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
- Uname: Linux 3.5.0-17-generic x86_64
- ApportVersion: 2.6.1-0ubuntu3
- Architecture: amd64
- CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
- Date: Mon Oct 15 18:47:19 2012
- EcryptfsInUse: Yes
- InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121014)
- ProcEnviron:
-  LANGUAGE=en_US:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- SourcePackage: unity
- UpgradeStatus: No upgrade log present (probably fresh install)
+ [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any software change in the Unity desktop shell has the potential to
+ introduce desktop shell crashes or lockups.
+ 
+ [ Other Info ]
+ 
+ The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
+ where it has been in production use for some time with apparent
+ regressions.

** Branch unlinked: lp:~unity-team/unity/trusty-1066971

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1066971/+attachment/4292934/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1066971

Title:
  Launcher count overflows when displaying 5+ digits

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  What happens:

  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3. The count becomes an unreadable mess.

  What should happen:

  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3a. The count stretches, allowing for up to 8-9 digits to be displayed.
  3b. The count is truncated, still showing the most important parts of the 
number.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any software change in the Unity desktop shell has the potential to
  introduce desktop shell crashes or lockups.

  [ Other Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time with apparent
  regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1066971/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1276177] Re: Applications using client-side decorations are not resizable in Unity

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

+ [ Impact ]
+ 
  GNOME applications that use client-side decorations can't be resized on
  Unity. I think it's because the frame extents hint is not supported.
  
  gnome-clocks and gnome-tweak-tool are two apps in the archive that have
  this problem.
+ 
+ [ Test Case ]
+ 
+ Run one of the abovementioned applications.  Their windows should be
+ resizable.
+ 
+ [ Regression Potential ]
+ 
+ Any modifications to the Unity desktop shell could potentially introduce
+ new crashes or lockups.
+ 
+ [ Other Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
+ Unity, where it has been in production use in Ubuntu Vivid Vervet dev
+ release for some time without apparent regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1276177/+attachment/4292938/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1276177

Title:
  Applications using client-side decorations are not resizable in Unity

Status in Themes for Ubuntu:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Debian:
  Confirmed

Bug description:
  [ Impact ]

  GNOME applications that use client-side decorations can't be resized
  on Unity. I think it's because the frame extents hint is not
  supported.

  gnome-clocks and gnome-tweak-tool are two apps in the archive that
  have this problem.

  [ Test Case ]

  Run one of the abovementioned applications.  Their windows should be
  resizable.

  [ Regression Potential ]

  Any modifications to the Unity desktop shell could potentially
  introduce new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity, where it has been in production use in Ubuntu Vivid Vervet
  dev release for some time without apparent regression.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1299741] Re: Shadows shouldn't wrap around to other workspaces/monitors

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1276177

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1299741

Title:
  Shadows shouldn't wrap around to other workspaces/monitors

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in compiz package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Window shadows can be seen on adjacent workspaces.

  [ Test Case ]

  To reproduce, launch a whole bunch (10, 20, a lot) of windows on
  workspace 2, and position them on or near the right edge.  Then switch
  to workspace 1, and observe the massive black blob on the left of the
  screen.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  a new crash or lockup.

  [ Other Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time without apparent
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1299741/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1373695] Re: Not resizable windows can be moved by dragging them on every edge

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1276177

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1373695

Title:
  Not resizable windows can be moved by dragging them on every edge

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  1. Open a non resizable window such as Calculator or Unity Control Center
  2. Move the mouse to the edge of the window, outside the window itself
 but in the area that is close at least 10 px.
  3. Press the mouse and start to drag

  Expected behavior: 
  4. nothing happens

  Actual behavior
  5. the hand cursor is shown and window can be dragged around
  As side effect, if LIMs are enabled, moving the mouse over a window edge 
makes the menus to show.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1373695/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1364225] Re: Shadow applied inconsistently to windows that use XShape

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1276177

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1364225

Title:
  Shadow applied inconsistently to windows that use XShape

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  When using the XShape APIs*, windows that have a rectangular shape are
  treated like normal windows (they get a title bar and shadow) even if
  the rectangular region is much smaller than the window.

  When a non-rectangular window changes its shape to be rectangular, it
  gains a shadow that remains even after changing its shape back to be
  non-rectangular.

  Ideally there would always be a shadow that matches the shape of the
  window.

  In the mean time, the correct behavior might be to remove the shadow
  whenever a shape is applied. If the application wishes to remove an
  applied shape, they could do something like:

XShapeCombineMask(d, w, ShapeBounding, 0, 0, None, ShapeSet);

  Please let me know if you need any more details, or if I'm missing
  something. (Unfortunately, the ubuntu-bug tool wouldn't work when
  filing this bug).

  * http://www.x.org/releases/current/doc/xextproto/shape.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1364225/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1292218] Re: Lockscreen prompt missing hi dpi

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

+ [ Impact ]
+ 
  The lockscreen has correct Panel HiDPI support, but the prompt doesn't
  scale right now.
+ 
+ [ Test Case ]
+ 
+ (1) Using the System Settings, adjust the scaling for your monitor to, say, 
1.88
+ (2) Invoke the screen lock by, say, pressing Super-L
+ (3) hit the shift key to bring up the lockscreen, observe the scaling of the 
password prompt: it should be appropriately scaled.
+ 
+ [ Regression Potential ]
+ 
+ Any change to the Unity desktop shell could potentially introduce a new
+ crash or lockup:  in this case, a crash could be a security violation.
+ 
+ [ Additional Info ]
+ 
+ The SRU for for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
+ where it has been in production use for some time without apparent
+ regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/unity/+bug/1292218/+attachment/4292964/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1292218

Title:
  Lockscreen prompt missing hi dpi

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  The lockscreen has correct Panel HiDPI support, but the prompt doesn't
  scale right now.

  [ Test Case ]

  (1) Using the System Settings, adjust the scaling for your monitor to, say, 
1.88
  (2) Invoke the screen lock by, say, pressing Super-L
  (3) hit the shift key to bring up the lockscreen, observe the scaling of the 
password prompt: it should be appropriately scaled.

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introduce a
  new crash or lockup:  in this case, a crash could be a security
  violation.

  [ Additional Info ]

  The SRU for for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time without apparent
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1292218/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1332947] Re: HDPI: unity randomly turns on large text in universal access

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1332947

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1332947

Title:
  HDPI: unity randomly turns on large text in universal access

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every
  couple of reboots, the 'large text' option in Universal Access gets
  switched on upon login. It happens in roughly 1 out of 5 reboots for 1
  or more users on the computer.

  It appears to happen to people with small HighDPI screens. In my case, it's 
13 inch at 2560x1600.
  Another example is 13 inch at 1080p -  
http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0

  unity:
Installed: 7.2.1+14.04.20140513-0ubuntu2
Candidate: 7.2.1+14.04.20140513-0ubuntu2
Version table:
   *** 7.2.1+14.04.20140513-0ubuntu2 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  unity-control-center:
Installed: 14.04.3+14.04.20140410-0ubuntu1
Candidate: 14.04.3+14.04.20140410-0ubuntu1
Version table:
   *** 14.04.3+14.04.20140410-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  intel iris pro graphics (lspci -vvv):

  00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) 
(prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device 011a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 66
Region 0: Memory at b000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at a000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 1000 [size=64]
Expansion ROM at unassigned [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1332947/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1384910] Re: Switching maximized windows using the spread might lead to wrong title and positioning

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1316265

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1384910

Title:
  Switching maximized windows using the spread might lead to wrong title
  and positioning

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  1. Open at least two maximized windows
  2. Select one of the windows (last opened seems better)
  3. Hit Super + W
  4. Start writing to select the other(s) window opened
  5. Select it, hitting enter.

  The title will be wrong (the one of the previous title) while the
  window buttons will be in the wrong position (see attached sreenshot,
  in LIM mode, or empty panel otherwise).

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introducer a
  new crash or lockup.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been included in the Ubuntu Vivid Vervet dev
  release for some time without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1384910/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1385285] Re: Clicking in panel elements when the expo is active, performs to the maximized windows

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1316265

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1385285

Title:
  Clicking in panel elements when the expo is active, performs to the
  maximized windows

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  1. Open a maximized window (it must be focused when using global menus, not 
with LIMs)
  2. Hit Super+s to enter in expo mode
  3. Click in the panel, in different areas and you'll get:
 - top-left corner buttons will work (although when not visible)
 - grab area will make possible to grab and focus (when in LIM mode) a 
window

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1385285/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1384958] Re: Ubuntu Desktop title is moved right as the window buttons were there

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1316265

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1384958

Title:
  Ubuntu Desktop title is moved right as if the window buttons were
  there

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  1. Open a maximized window
  2. Hit Super+s
  3. The Ubuntu Desktop title is moved some pixels to the right, as shown in 
the attached screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1384958/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1159249] Re: HUD does not show up over fullscreen window

2015-01-06 Thread Stephen M. Webb
** Changed in: unity (Ubuntu)
   Importance: Undecided = Medium

** Changed in: unity/7.2
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1159249

Title:
  HUD does not show up over fullscreen window

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  In Progress

Bug description:
  Step to reproduce:

  1. Open some site in firefox

  2. Go to fullscreen mode (F11)

  3. Press Alt once.

  The HUD will not appear, but actually it will start and grab the
  keyboard, You will not be able to use F11 again to exit the fullscreen
  mode. You will be able to interact with HUD blindely.

  4. Exit the fullscreen mode using mouse and you will see the HUD
  active and ready.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.03.20-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  Date: Sun Mar 24 02:01:54 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-01 (81 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac 
(20121017.3)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-03-18 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1159249/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1385285] Re: Clicking in panel elements when the expo is active, performs to the maximized windows

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

+ [ Impact ]
+ 
  1. Open a maximized window (it must be focused when using global menus, not 
with LIMs)
  2. Hit Super+s to enter in expo mode
  3. Click in the panel, in different areas and you'll get:
-- top-left corner buttons will work (although when not visible)
-- grab area will make possible to grab and focus (when in LIM mode) a 
window
+    - top-left corner buttons will work (although when not visible)
+    - grab area will make possible to grab and focus (when in LIM mode) a 
window
+ 
+ [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any code change to the Unity desktop shell could potentially introduce
+ new crashes or lockups.
+ 
+ [ Other Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
+ Unity where it has been in the Ubuntu Vivid Vervet dev release form
+ several weeks without apparent regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/unity/+bug/1385285/+attachment/4292979/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1385285

Title:
  Clicking in panel elements when the expo is active, performs to the
  maximized windows

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  1. Open a maximized window (it must be focused when using global menus, not 
with LIMs)
  2. Hit Super+s to enter in expo mode
  3. Click in the panel, in different areas and you'll get:
     - top-left corner buttons will work (although when not visible)
     - grab area will make possible to grab and focus (when in LIM mode) a 
window

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been in the Ubuntu Vivid Vervet dev release form
  several weeks without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1385285/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1299741] Re: Shadows shouldn't wrap around to other workspaces/monitors

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

- I suppose this could be seen as a matter of design opinion but, in my
- opinion, it's incredibly ugly.  To reproduce, launch a whole bunch (10,
- 20, a lot) of windows on workspace 2, and position them on or near the
- right edge.  Then switch to workspace 1, and observe the massive black
- blob on the left of the screen.  This really doesn't make a whole lot of
- sense visually, and it's pretty ugly, IMO.
+ [ Impact ]
+ 
+ Window shadows can be seen on adjacent workspaces.
+ 
+ [ Test Case ]
+ 
+ To reproduce, launch a whole bunch (10, 20, a lot) of windows on
+ workspace 2, and position them on or near the right edge.  Then switch
+ to workspace 1, and observe the massive black blob on the left of the
+ screen.
+ 
+ [ Regression Potential ]
+ 
+ Any code change to the Unity desktop shell could potentially introduce a
+ new crash or lockup.
+ 
+ [ Other Info ]
+ 
+ The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
+ where it has been in production use for some time without apparent
+ regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1299741/+attachment/4292939/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1299741

Title:
  Shadows shouldn't wrap around to other workspaces/monitors

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in compiz package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Window shadows can be seen on adjacent workspaces.

  [ Test Case ]

  To reproduce, launch a whole bunch (10, 20, a lot) of windows on
  workspace 2, and position them on or near the right edge.  Then switch
  to workspace 1, and observe the massive black blob on the left of the
  screen.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  a new crash or lockup.

  [ Other Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time without apparent
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1299741/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1292218] Re: Lockscreen prompt missing hi dpi

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1292218

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1292218

Title:
  Lockscreen prompt missing hi dpi

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  The lockscreen has correct Panel HiDPI support, but the prompt doesn't
  scale right now.

  [ Test Case ]

  (1) Using the System Settings, adjust the scaling for your monitor to, say, 
1.88
  (2) Invoke the screen lock by, say, pressing Super-L
  (3) hit the shift key to bring up the lockscreen, observe the scaling of the 
password prompt: it should be appropriately scaled.

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introduce a
  new crash or lockup:  in this case, a crash could be a security
  violation.

  [ Additional Info ]

  The SRU for for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time without apparent
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1292218/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1301776] Re: Update manager is really small and not resizeable

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1276177

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1301776

Title:
  Update manager is really small and not resizeable

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in compiz package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Fix Released
Status in compiz source package in Trusty:
  Triaged
Status in unity source package in Trusty:
  Triaged

Bug description:
  update-manager 1:0.196.9, Ubuntu Trusty

  Update manager's window, and especially its fields inside the window, are way 
too small and also it's not resizeable, making it almost useless at least on my 
HiDPI screen (3200 x 1800).
  https://launchpadlibrarian.net/171657786/update-manager-is-small.png

  https://wiki.ubuntu.com/SoftwareUpdates#expanded: The Updates
  Available window should be manually resizable only when it is in this
  expanded state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1301776/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1324104] Re: Ctrl + Super + D hides windows but still resizable when cursor over border

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1276177

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1324104

Title:
  Ctrl + Super + D hides windows but still resizable when cursor over
  border

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  If You Press Ctrl + Super + D Shortcut To minimize all windows
  it works but when you move the cursor you will see it change 
  to an arrow for resizing the hidden windows when the cursor
  is in the location of the border of the hidden windows

  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  unity:
Installed: 7.2.0+14.04.20140423-0ubuntu1.2
Candidate: 7.2.0+14.04.20140423-0ubuntu1.2
Version table:
   *** 7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://lb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  500 http://lb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1324104/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1373695] Re: Not resizable windows can be moved by dragging them on every edge

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

+ [ Impact ]
+ 
  1. Open a non resizable window such as Calculator or Unity Control Center
  2. Move the mouse to the edge of the window, outside the window itself
-but in the area that is close at least 10 px.
+    but in the area that is close at least 10 px.
  3. Press the mouse and start to drag
  
- Expected behavior: 
+ Expected behavior:
  4. nothing happens
  
  Actual behavior
  5. the hand cursor is shown and window can be dragged around
  As side effect, if LIMs are enabled, moving the mouse over a window edge 
makes the menus to show.
+ 
+  [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any change to the Unity desktop shell could potentially introduce new
+ crashed or lockups.
+ 
+ [ Other Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
+ 14.10 where it has been in production use for some time without apparent
+ regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/unity/+bug/1373695/+attachment/4292965/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1373695

Title:
  Not resizable windows can be moved by dragging them on every edge

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  1. Open a non resizable window such as Calculator or Unity Control Center
  2. Move the mouse to the edge of the window, outside the window itself
     but in the area that is close at least 10 px.
  3. Press the mouse and start to drag

  Expected behavior:
  4. nothing happens

  Actual behavior
  5. the hand cursor is shown and window can be dragged around
  As side effect, if LIMs are enabled, moving the mouse over a window edge 
makes the menus to show.

   [ Test Case ]

  See above.

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introduce new
  crashed or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1373695/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1316265

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1316265

Title:
  Maximized Window's Title Bar Does Not Merge into Menu Bar after
  Performing Super+W (window spread) filtering

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  A maximized application's title bar does not merge into the menu bar
  once a user has performed Super + W (window slide). Note that if one
  does not do Super+E, then the bars to merge together. However, once
  Super+E has been performed, this bug persists for the lifetime of the
  windowed application. If the application is restarted after doing
  Super+E, then the bug is gone. Thus, it seems like Super+E introduces
  this bug for the lifetime of the windowed application.

  Expected behavior: Maximized window's title bar is merged into menu bar.
  Observed: Does not occur after Super+W is performed.

  Try this out using Terminal.

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon May  5 14:48:01 2014
  InstallationDate: Installed on 2013-09-08 (239 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 
(20130424)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1316265/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1384958] Re: Ubuntu Desktop title is moved right as if the window buttons were there

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Summary changed:

- Ubuntu Desktop title is moved right as the window buttons were there
+ Ubuntu Desktop title is moved right as if the window buttons were there

** Description changed:

+ [ Impact ]
+ 
  1. Open a maximized window
  2. Hit Super+s
- 3. The Ubuntu Desktop title is moved some pixels to the right, as shown in 
the attached screenshot
+ 3. The Ubuntu Desktop title is moved some pixels to the right, as shown in 
the attached screenshot.
+ 
+ [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any code change to the Unity desktop shell has the potential to
+ introduce new crashes or lockups.
+ 
+ [ Additional Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
+ Unity where it has been included in the Ubuntu Vivid Vervet dev
+ release for some time without apparent regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/unity/+bug/1384958/+attachment/4292972/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1384958

Title:
  Ubuntu Desktop title is moved right as if the window buttons were
  there

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  1. Open a maximized window
  2. Hit Super+s
  3. The Ubuntu Desktop title is moved some pixels to the right, as shown in 
the attached screenshot.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been included in the Ubuntu Vivid Vervet dev
  release for some time without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1384958/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1107818] Re: Annotate plugin + unityshell: Flickering during rectangle and ellipse drawing, no flickering without unityshell

2015-01-12 Thread Stephen M. Webb
** Tags added: plugin-annotate

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1107818

Title:
  Annotate plugin + unityshell: Flickering during rectangle and ellipse
  drawing, no flickering without unityshell

Status in Compiz:
  New
Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  [How to reproduce]

  1. Initiate Annotate in Rectangle or Ellipse draw mode, construct one
  and hold the mousebutton

  [What you would expect to happen]

  A preview of your rectangle or ellipse should be rendered without
  flickering inside( the filling).

  [What actually happens]

  A preview of your rectangle or ellipse is rendered, but it is
  flickering inside (the filling).

  Note:
  This bug only happens if unityshell is enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1107818/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2015-01-09 Thread Stephen M. Webb
Yeah, I'm going to go ahead and suggest folks try adding the PPA at
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-004
to their sources and update to the Unity found there.  It contains a
whole slew of bugfixes currently in the SRU landing pattern, including a
bunch of the me too bugs getting reported here.

The release in the PPA should land in trusty-updates real soon (due
diligence and all), but in the mean time should help a lot of these
lockscreen authentication problems.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1311316

Title:
  After locking screen there is no input field to type password for
  unlock

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  *** IMPORTANT **

  *** The fix is not included in TRUSTY. Will be included with next SRU.
  ***

  If you can reproduce this bug please be sure to provide the following info:
  1. Do you use a multi-head setup? If yes, using just one monitor fixes the 
issue?
  2. Can you reproduce all the time?
  3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see 
comment #115) can you still reproduce that?
  4. Please consider posting /var/log/auth.log (at least part of it, should not 
contain sensitive information)
  5. Please specify the unity version
  *** END IMPORTANT **

  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1324104] Re: Ctrl + Super + D hides windows but still resizable when cursor over border

2015-01-06 Thread Stephen M. Webb
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1354498

** Description changed:

+ [ Impact ]
+ 
  If You Press Ctrl + Super + D Shortcut To minimize all windows
- it works but when you move the cursor you will see it change 
+ it works but when you move the cursor you will see it change
  to an arrow for resizing the hidden windows when the cursor
  is in the location of the border of the hidden windows
  
- Description:  Ubuntu 14.04 LTS
- Release:  14.04
+ [ Test Case ]
  
- unity:
-   Installed: 7.2.0+14.04.20140423-0ubuntu1.2
-   Candidate: 7.2.0+14.04.20140423-0ubuntu1.2
-   Version table:
-  *** 7.2.0+14.04.20140423-0ubuntu1.2 0
- 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
- 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
- 500 http://lb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  7.2.0+14.04.20140416-0ubuntu1 0
- 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
- 500 http://lb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any code change to the Unity desktop shell could potentially introduce a
+ new crash of lockup.
+ 
+ This particular change could possibly introduce a regression in which no
+ windows are re-sizable.
+ 
+ [ Additional Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
+ 14.10 where it has been in production use with no sign of regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1324104/+attachment/4293135/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1324104

Title:
  Ctrl + Super + D hides windows but still resizable when cursor over
  border

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  If You Press Ctrl + Super + D Shortcut To minimize all windows
  it works but when you move the cursor you will see it change
  to an arrow for resizing the hidden windows when the cursor
  is in the location of the border of the hidden windows

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  a new crash of lockup.

  This particular change could possibly introduce a regression in which
  no windows are re-sizable.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use with no sign of regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1324104/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1364225] Re: Shadow applied inconsistently to windows that use XShape

2015-01-06 Thread Stephen M. Webb
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1354498

** Description changed:

- When using the XShape APIs*, windows that have a rectangular shape are
- treated like normal windows (they get a title bar and shadow) even if
- the rectangular region is much smaller than the window.
+ [ Impact ]
  
- When a non-rectangular window changes its shape to be rectangular, it
- gains a shadow that remains even after changing its shape back to be
- non-rectangular.
+ Non-standard windows of a non-rectangular shape end up with rectangular
+ shadows drawn behind them by Unity.
  
- Ideally there would always be a shadow that matches the shape of the
- window.
+ It is better to have no shadow at all for these windows rather than an
+ incorrect rectangular shadow.
  
- In the mean time, the correct behavior might be to remove the shadow
- whenever a shape is applied. If the application wishes to remove an
- applied shape, they could do something like:
+ [ Test Case ]
  
-   XShapeCombineMask(d, w, ShapeBounding, 0, 0, None, ShapeSet);
+ C code for a test case is attached to this bug.  It needs to be compiled
+ and run to demonstrate the problem and solution.
  
- Please let me know if you need any more details, or if I'm missing
- something. (Unfortunately, the ubuntu-bug tool wouldn't work when filing
- this bug).
+ [ Regression Potential ]
  
- * http://www.x.org/releases/current/doc/xextproto/shape.html
+ Any code change to the Unity desktop shell could introduce a new crash
+ or hang.
+ 
+ A possible regression in this particular fix is a lack of shadows when
+ expected, or a non-standard non-rectangular window still having a shadow
+ as before.
+ 
+ [ Additional Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
+ 14.10 where it has been in production use for some time without
+ regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1364225/+attachment/4293139/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1364225

Title:
  Shadow applied inconsistently to windows that use XShape

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Non-standard windows of a non-rectangular shape end up with
  rectangular shadows drawn behind them by Unity.

  It is better to have no shadow at all for these windows rather than an
  incorrect rectangular shadow.

  [ Test Case ]

  C code for a test case is attached to this bug.  It needs to be
  compiled and run to demonstrate the problem and solution.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could introduce a new crash
  or hang.

  A possible regression in this particular fix is a lack of shadows when
  expected, or a non-standard non-rectangular window still having a
  shadow as before.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1364225/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering

2015-01-06 Thread Stephen M. Webb
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1354498

** Description changed:

+ [ Impact ]
+ 
  A maximized application's title bar does not merge into the menu bar
  once a user has performed Super + W (window slide). Note that if one
  does not do Super+E, then the bars to merge together. However, once
  Super+E has been performed, this bug persists for the lifetime of the
  windowed application. If the application is restarted after doing
  Super+E, then the bug is gone. Thus, it seems like Super+E introduces
  this bug for the lifetime of the windowed application.
  
  Expected behavior: Maximized window's title bar is merged into menu bar.
  Observed: Does not occur after Super+W is performed.
  
- Try this out using Terminal.
+ [ Test Case ]
  
- ProblemType: BugDistroRelease: Ubuntu 14.04
- Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
- ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
- Uname: Linux 3.13.0-24-generic x86_64
- ApportVersion: 2.14.1-0ubuntu3
- Architecture: amd64
- CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
- CurrentDesktop: Unity
- Date: Mon May  5 14:48:01 2014
- InstallationDate: Installed on 2013-09-08 (239 days ago)
- InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 
(20130424)SourcePackage: unity
- UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago)
+ (1) Open one or more Terminals, place one in maximized mode (eg. by using 
control-super-up or clicking the embiggen button).
+ (2) use super-W to enter the spread mode
+ (3) select the maximized terminal window
+ (4) lookee lookee, separate title bars without the fix!
+ 
+ [ Regression Potential ]
+ 
+ Any change to the Unity desktop shell could potentially introduce a new
+ crash or hangup.
+ 
+ [ Additional Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
+ Unity where it has been a part of the Ubuntu Vivid Vervet dev release
+ for some time now and has demonstrated no regressions.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1316265/+attachment/4293178/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1316265

Title:
  Maximized Window's Title Bar Does Not Merge into Menu Bar after
  Performing Super+W (window spread) filtering

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  A maximized application's title bar does not merge into the menu bar
  once a user has performed Super + W (window slide). Note that if one
  does not do Super+E, then the bars to merge together. However, once
  Super+E has been performed, this bug persists for the lifetime of the
  windowed application. If the application is restarted after doing
  Super+E, then the bug is gone. Thus, it seems like Super+E introduces
  this bug for the lifetime of the windowed application.

  Expected behavior: Maximized window's title bar is merged into menu bar.
  Observed: Does not occur after Super+W is performed.

  [ Test Case ]

  (1) Open one or more Terminals, place one in maximized mode (eg. by using 
control-super-up or clicking the embiggen button).
  (2) use super-W to enter the spread mode
  (3) select the maximized terminal window
  (4) lookee lookee, separate title bars without the fix!

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introduce a
  new crash or hangup.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been a part of the Ubuntu Vivid Vervet dev
  release for some time now and has demonstrated no regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1316265/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1354498] Re: Switcher Icons emblem (count) is too small

2015-01-06 Thread Stephen M. Webb
** Summary changed:

- Switcher Icons emblem (count) it's too small
+ Switcher Icons emblem (count) is too small

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1354498

Title:
  Switcher Icons emblem (count) is too small

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  It should have a count emblem with a size proprtional on the icon size
  itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1354498/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1301776] Re: Update manager is really small and not resizeable

2015-01-06 Thread Stephen M. Webb
https://bugs.launchpad.net/unity/+bug/1404730

** Description changed:

+ [ Impact ]
  update-manager 1:0.196.9, Ubuntu Trusty
  
  Update manager's window, and especially its fields inside the window, are way 
too small and also it's not resizeable, making it almost useless at least on my 
HiDPI screen (3200 x 1800).
  https://launchpadlibrarian.net/171657786/update-manager-is-small.png
  
  https://wiki.ubuntu.com/SoftwareUpdates#expanded: The Updates
  Available window should be manually resizable only when it is in this
  expanded state.
+ 
+ [ Test Case ]
+ 
+ Run the Ubuntu update manager and attempt to resize the window.  See
+ above.
+ 
+ [ Regression Potential ]
+ 
+ Any code change to the Unity desktop shell has the potential to
+ introduce new crashes or lockups.
+ 
+ [ Additional Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
+ 14.10 where it has been in production use for some time without apparent
+ regressions.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301776/+attachment/4293132/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1301776

Title:
  Update manager is really small and not resizeable

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in compiz package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Fix Released
Status in compiz source package in Trusty:
  Triaged
Status in unity source package in Trusty:
  Triaged

Bug description:
  [ Impact ]
  update-manager 1:0.196.9, Ubuntu Trusty

  Update manager's window, and especially its fields inside the window, are way 
too small and also it's not resizeable, making it almost useless at least on my 
HiDPI screen (3200 x 1800).
  https://launchpadlibrarian.net/171657786/update-manager-is-small.png

  https://wiki.ubuntu.com/SoftwareUpdates#expanded: The Updates
  Available window should be manually resizable only when it is in this
  expanded state.

  [ Test Case ]

  Run the Ubuntu update manager and attempt to resize the window.  See
  above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  apparent regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1301776/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 796527] Re: Launcher - Count indicator should change size depending on the number of digits

2015-01-06 Thread Stephen M. Webb
** Description changed:

+ [ Impact ]
+ 
  The count indicator currently stays the same size irrespective of
  whether it is displaying one or two digits.
  
  Desired solution:
  If the count indicator only displays one digit it should be a circle e.g (7)
  If the count indicator displays two digits it should be a lozenge shape e.g. 
two half circles joined by two straight lines e.g. (27)
  If the count indicator displays three digits it should be a lozenge shape 
e.g. two half circles joined by two straight lines e.g (527)
+ 
+ [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any code change to the Unity desktop shell has the potential to unleash
+ a new crash or lockup in the desktop.
+ 
+ [ Other Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
+ 14.10 where it has been in production use for some months now without
+ apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/796527

Title:
  Launcher - Count indicator should change size depending on the number
  of digits

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  The count indicator currently stays the same size irrespective of
  whether it is displaying one or two digits.

  Desired solution:
  If the count indicator only displays one digit it should be a circle e.g (7)
  If the count indicator displays two digits it should be a lozenge shape e.g. 
two half circles joined by two straight lines e.g. (27)
  If the count indicator displays three digits it should be a lozenge shape 
e.g. two half circles joined by two straight lines e.g (527)

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  unleash a new crash or lockup in the desktop.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some months now without
  apparent regression.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1332947] Re: HDPI: unity randomly turns on large text in universal access

2015-01-06 Thread Stephen M. Webb
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1354498

** Description changed:

- I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every
- couple of reboots, the 'large text' option in Universal Access gets
- switched on upon login. It happens in roughly 1 out of 5 reboots for 1
- or more users on the computer.
+ [ Impact ]
  
- It appears to happen to people with small HighDPI screens. In my case, it's 
13 inch at 2560x1600.
- Another example is 13 inch at 1080p -  
http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0
+ Using a display scaling factor of  1.0 the 'large text' setting is
+ sometimes enabled automatically on session start, doubling the scaling
+ factor.
  
- unity:
-   Installed: 7.2.1+14.04.20140513-0ubuntu2
-   Candidate: 7.2.1+14.04.20140513-0ubuntu2
-   Version table:
-  *** 7.2.1+14.04.20140513-0ubuntu2 0
- 500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  7.2.0+14.04.20140423-0ubuntu1.2 0
- 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
-  7.2.0+14.04.20140416-0ubuntu1 0
- 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
+ [ Test Case ]
  
- unity-control-center:
-   Installed: 14.04.3+14.04.20140410-0ubuntu1
-   Candidate: 14.04.3+14.04.20140410-0ubuntu1
-   Version table:
-  *** 14.04.3+14.04.20140410-0ubuntu1 0
- 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
- 100 /var/lib/dpkg/status
+ (1) Using the System Settings  Displays  Scale for menu and title bars 
slider, set the scaling to a value  1 (for example, 1.88).
+ (2) Log out and in several times.
  
+ Since this problem occurs as a result of a race condition somewhere, it
+ is not reliably reproducable.
  
- intel iris pro graphics (lspci -vvv):
+ [ Regression Potential ]
  
- 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) 
(prog-if 00 [VGA controller])
-   Subsystem: Apple Inc. Device 011a
-   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
-   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
-   Latency: 0
-   Interrupt: pin A routed to IRQ 66
-   Region 0: Memory at b000 (64-bit, non-prefetchable) [size=4M]
-   Region 2: Memory at a000 (64-bit, prefetchable) [size=256M]
-   Region 4: I/O ports at 1000 [size=64]
-   Expansion ROM at unassigned [disabled]
-   Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
-   Address: fee00018  Data: 
-   Capabilities: [d0] Power Management version 2
-   Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
-   Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
-   Capabilities: [a4] PCI Advanced Features
-   AFCap: TP+ FLR+
-   AFCtrl: FLR-
-   AFStatus: TP-
-   Kernel driver in use: i915
+ Any code change to the Unity desktop shell could introduce a new crash
+ or lockup.
+ 
+ [ Other Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
+ 14.10 where it has been in production use for some time without
+ demonstrating regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1332947/+attachment/4293179/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1332947

Title:
  HDPI: unity randomly turns on large text in universal access

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [ Impact ]

  Using a display scaling factor of  1.0 the 'large text' setting is
  sometimes enabled automatically on session start, doubling the scaling
  factor.

  [ Test Case ]

  (1) Using the System Settings  Displays  Scale for menu and title bars 
slider, set the scaling to a value  1 (for example, 1.88).
  (2) Log out and in several times.

  Since this problem occurs as a result of a race condition somewhere,
  it is not reliably reproducable.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could introduce a new crash
  or lockup.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  demonstrating regression.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1354498] Re: Switcher Icons emblem (count) is too small

2015-01-06 Thread Stephen M. Webb
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1354498

** Description changed:

- It should have a count emblem with a size proprtional on the icon size
- itself.
+ [ Impact]
+ 
+ The emblem size does not change as the icon size is adjusted.
+ 
+ [ Test Case ]
+ 
+ (1) Use the System Settings  Displays  Scale for menus and title bars
+ slider to adjust the Swicther icon size.
+ 
+ (2) Observe the size of the badge.  It should scale with the icon size.
+ 
+ [ Regression Potential
+ 
+ Any code change to the Unity desktop shell has the potential to
+ introduce new crashers or lockers.
+ 
+ [ Other Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
+ 14.10 where it has been in production use for some time with no apparent
+ regressions.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1354498/+attachment/4293180/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1354498

Title:
  Switcher Icons emblem (count) is too small

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact]

  The emblem size does not change as the icon size is adjusted.

  [ Test Case ]

  (1) Use the System Settings  Displays  Scale for menus and title
  bars slider to adjust the Swicther icon size.

  (2) Observe the size of the badge.  It should scale with the icon
  size.

  [ Regression Potential

  Any code change to the Unity desktop shell has the potential to
  introduce new crashers or lockers.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time with no
  apparent regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1354498/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1347638] Re: Launch1 button doesn't work on shortcuts

2015-01-13 Thread Stephen M. Webb
There is a fix in the SRU queue for #1302885 (it looks like this bug is
a duplicate of that one).  Please try adding the PPA at
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-004
to your sources and see if it fixes this problem.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1347638

Title:
  Launch1 button doesn't work on shortcuts

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

Bug description:
  Hardware: Thinkpad X230, but seemingly all Thinkpads.

  (Apologies if this is mis-characterized as a Unity bug - not sure
  where to put it)

  The special Thinkpad button, often called ThinkVantage button, used
  to work fine for keyboard shortcuts in 12.04, as configured in the
  keyboard settings panel.

  In 14.04 it is possible to assign it to a shortcut in the keyboard
  settings dialog, where it shows up as Launch1, but it doesn't work -
  they shortcut is not activated by hitting that key.

  The key appears to get through to the desktop and apps, because if I
  hit it while Emacs has focus it complains that nothing is assigned to
  XF86Launch1 (in 12.04 the key didn't get through to Emacs and there
  was no problem)

  Discussion of this, including some other's outputs, is here:
  http://ubuntuforums.org/showthread.php?t=890

  -

  xev gives this on keypress/release:

  MappingNotify event, serial 37, synthetic NO, window 0x0,
  request MappingKeyboard, first_keycode 8, count 248

  KeyPress event, serial 37, synthetic NO, window 0x401,
  root 0xa2, subw 0x0, time 2883009, (-1684,706), root:(610,758),
  state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x401,
  root 0xa2, subw 0x0, time 2883009, (-1684,706), root:(610,758),
  state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

  -

  acpi_listen gives:
  button/prog1 PROG1 0080  K

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale]
  CurrentDesktop: Unity
  Date: Wed Jul 23 08:11:18 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-11 (11 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1347638/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1347638] Re: Launch1 button doesn't work on shortcuts

2015-02-11 Thread Stephen M. Webb
The fix for #1302885 is now available in trusty-updates.  The above PPA
no longer holds any Unity packages, so there's no point in testing it.

The bug should now be fixed in Ubuntu 14.04 LTS and in the Vivid Vervet
development release.  If this problem continues to occur in one of those
Ubuntu environments please update this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1347638

Title:
  Launch1 button doesn't work on shortcuts

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

Bug description:
  Hardware: Thinkpad X230, but seemingly all Thinkpads.

  (Apologies if this is mis-characterized as a Unity bug - not sure
  where to put it)

  The special Thinkpad button, often called ThinkVantage button, used
  to work fine for keyboard shortcuts in 12.04, as configured in the
  keyboard settings panel.

  In 14.04 it is possible to assign it to a shortcut in the keyboard
  settings dialog, where it shows up as Launch1, but it doesn't work -
  they shortcut is not activated by hitting that key.

  The key appears to get through to the desktop and apps, because if I
  hit it while Emacs has focus it complains that nothing is assigned to
  XF86Launch1 (in 12.04 the key didn't get through to Emacs and there
  was no problem)

  Discussion of this, including some other's outputs, is here:
  http://ubuntuforums.org/showthread.php?t=890

  -

  xev gives this on keypress/release:

  MappingNotify event, serial 37, synthetic NO, window 0x0,
  request MappingKeyboard, first_keycode 8, count 248

  KeyPress event, serial 37, synthetic NO, window 0x401,
  root 0xa2, subw 0x0, time 2883009, (-1684,706), root:(610,758),
  state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x401,
  root 0xa2, subw 0x0, time 2883009, (-1684,706), root:(610,758),
  state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

  -

  acpi_listen gives:
  button/prog1 PROG1 0080  K

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale]
  CurrentDesktop: Unity
  Date: Wed Jul 23 08:11:18 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-11 (11 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1347638/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1407523] Re: Unity in lockscreen mode does not allow password entry

2015-01-04 Thread Stephen M. Webb
Please try the version of Unity from https://launchpad.net/~ci-train-
ppa-service/+archive/ubuntu/landing-004 -- this is the current Ubuntu
14.04 LTS update in the process of landing, and I believe it contains a
fix for this problem.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1407523

Title:
  Unity in lockscreen mode does not allow password entry

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Sometimes, when I come back to my computer after locking it, the
  password field is not displayed. This means I cannot enter the
  password, and I have to do an ungraceful shutdown of my X session.

  It only happens when the workstation has been running for a while
  (usually a few weeks) which leads me to suspect a memory leak, or
  similar.

  The unlock dialog box appears, but the password field is not rendered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1407523/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 796527] Re: Launcher - Count indicator should change size depending on the number of digits

2015-01-05 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Branch unlinked: lp:~unity-team/unity/trusty-1066971

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/796527/+attachment/4292522/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/796527

Title:
  Launcher - Count indicator should change size depending on the number
  of digits

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  The count indicator currently stays the same size irrespective of
  whether it is displaying one or two digits.

  Desired solution:
  If the count indicator only displays one digit it should be a circle e.g (7)
  If the count indicator displays two digits it should be a lozenge shape e.g. 
two half circles joined by two straight lines e.g. (27)
  If the count indicator displays three digits it should be a lozenge shape 
e.g. two half circles joined by two straight lines e.g (527)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1383468] Re: Windows in non-focused workspaces have not decorations in expo

2015-01-05 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

+ [ Impact ]
+ 
  1. Open multiple windows and put them in different workspaces
  2. Hit Super+S to open the expo
  3. Notice that windows that are not in the focused workspaces have no 
decorations
+ 
+ [ Test Case ]
+ 
+ See above: decorations should be present with fix.
+ 
+ [ Regression Potential ]
+ 
+ Decorations in the Spread could be drawn incorrectly.
+ 
+ [ Other Info ]
+ 
+ Fix for Ubuntu 14.01 LTS was cherry-picked from upstream Unity where it
+ has been in production testing in Ubuntu Vivid Vervet dev release for
+ a few months with no regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/unity/+bug/1383468/+attachment/4292463/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1383468

Title:
  Windows in non-focused workspaces have not decorations in expo

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  New
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  1. Open multiple windows and put them in different workspaces
  2. Hit Super+S to open the expo
  3. Notice that windows that are not in the focused workspaces have no 
decorations

  [ Test Case ]

  See above: decorations should be present with fix.

  [ Regression Potential ]

  Decorations in the Spread could be drawn incorrectly.

  [ Other Info ]

  Fix for Ubuntu 14.01 LTS was cherry-picked from upstream Unity where
  it has been in production testing in Ubuntu Vivid Vervet dev release
  for a few months with no regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1383468/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1361679] Re: Switcher Icons does not show progress emblem

2015-01-05 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Branch unlinked: lp:~unity-team/unity/trusty-1361679

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/unity/+bug/1361679/+attachment/4292467/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

** Description changed:

+ [ Impact ]
+ 
  - Open an application that shows progress information on its icon (i.e. 
nautilus or Hello Unity)
  - Open Alt-Tab switcher
  
  Expected behavior:
  - The icon should show the progress bar overlay
  
  Actual behavior:
  - No progress bar is shown.
+ 
+ [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any change to Switcher rendering has the potential to mess up drawing
+ icons in the Switcher or crashing Unity.
+ 
+ [ Other Info ]
+ 
+ The Ubuntu 14.04 LTS SRU was cherry-picked from the Ubuntu 14.10 release
+ where it has been in production use for some time without apparent
+ regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1361679

Title:
  Switcher Icons does not show progress emblem

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  - Open an application that shows progress information on its icon (i.e. 
nautilus or Hello Unity)
  - Open Alt-Tab switcher

  Expected behavior:
  - The icon should show the progress bar overlay

  Actual behavior:
  - No progress bar is shown.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any change to Switcher rendering has the potential to mess up drawing
  icons in the Switcher or crashing Unity.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU was cherry-picked from the Ubuntu 14.10
  release where it has been in production use for some time without
  apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1361679/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1371764] Re: Screen does not lock when an unity indicator is open

2015-01-05 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

+ [ Impact ]
+ 
+ Screen does not lock when a Unity indicator is open.
+ 
+ [ Test Case ]
+ 
  1. Open an unity Indicator
  2. Close the laptop lid¹
  
  Expected behavior:
  3. The indicator menu should be closed and the screen is locked
  
  Actual behavior:
  3. The screen is not locked with the menu visible, it gets locked
  as soon as the menu is closed.
  
  [1] instead of this action, you can also run the script below just before 
opening an indicator:
    sleep 3  gdbus call --session --dest com.canonical.Unity \
     --object-path /com/canonical/Unity/Session \
     --method com.canonical.Unity.Session.Lock
  
- PS: This is a special case of bug #49579, although this applies only to
- the unity indicators.
+ [ Regression Potential ]
+ 
+ Worst case is the lock screen still does not come up if an indicator is
+ open, which could be a potential security problem.
+ 
+ [ Other Info ]
+ 
+ The fix for Ubuntu 14.04 LTS is cherry-picked from Ubuntu 14.10 where it
+ has been in production use for some time without apparent regression.
+ 
+ This is a special case of bug #49579, although this applies only to the
+ unity indicators.

** Branch unlinked: lp:~unity-team/unity/trusty-1368427

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/unity/+bug/1371764/+attachment/4292466/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1371764

Title:
  Screen does not lock when an unity indicator is open

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Screen does not lock when a Unity indicator is open.

  [ Test Case ]

  1. Open an unity Indicator
  2. Close the laptop lid¹

  Expected behavior:
  3. The indicator menu should be closed and the screen is locked

  Actual behavior:
  3. The screen is not locked with the menu visible, it gets locked
  as soon as the menu is closed.

  [1] instead of this action, you can also run the script below just before 
opening an indicator:
    sleep 3  gdbus call --session --dest com.canonical.Unity \
     --object-path /com/canonical/Unity/Session \
     --method com.canonical.Unity.Session.Lock

  [ Regression Potential ]

  Worst case is the lock screen still does not come up if an indicator
  is open, which could be a potential security problem.

  [ Other Info ]

  The fix for Ubuntu 14.04 LTS is cherry-picked from Ubuntu 14.10 where
  it has been in production use for some time without apparent
  regression.

  This is a special case of bug #49579, although this applies only to
  the unity indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1371764/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1350331] Re: Dash doesn't close when Drag and dropping from it to another window

2015-01-05 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

+ [ Impact ]
+ 
   1. Open one nautilus window and another window, so that nautilus is not 
focused
-  2. Open the dash File lens (Super+F)
-  3. Start dragging a file from that to the nautilus launcher icon
-  4. Wait some delay
+  2. Open the dash File lens (Super+F)
+  3. Start dragging a file from that to the nautilus launcher icon
+  4. Wait some delay
  
  Expected Result:
-  4. The dash is closed and nautilus window is focused
+  4. The dash is closed and nautilus window is focused
  
  Actual result:
-  4. The nautilus window is focused, but the dash is not closed
+  4. The nautilus window is focused, but the dash is not closed
+ 
+ [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any code change in Unity has the potential to introduce crashes in
+ Unity.
+ 
+ This particular fix has the potential to not close the dash after a
+ drag-and-drop operation, which could conceivably result in a desktop
+ lock-up requiring a restart.
+ 
+ [ Other Info ]
+ 
+ The Ubuntu 14.04 LTS SRU fix was cherry-picked from Ubuntu 14.10 where
+ it has been in production use for some time without apparent regression.

** Branch unlinked: lp:~unity-team/unity/trusty-1350331

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/unity/+bug/1350331/+attachment/4292470/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1350331

Title:
  Dash doesn't close when Drag and dropping from it to another window

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   1. Open one nautilus window and another window, so that nautilus is not 
focused
   2. Open the dash File lens (Super+F)
   3. Start dragging a file from that to the nautilus launcher icon
   4. Wait some delay

  Expected Result:
   4. The dash is closed and nautilus window is focused

  Actual result:
   4. The nautilus window is focused, but the dash is not closed

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change in Unity has the potential to introduce crashes in
  Unity.

  This particular fix has the potential to not close the dash after a
  drag-and-drop operation, which could conceivably result in a desktop
  lock-up requiring a restart.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU fix was cherry-picked from Ubuntu 14.10 where
  it has been in production use for some time without apparent
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1350331/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1362162] Re: Dash buttons do not honour the text scaling

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Branch unlinked: lp:~unity-team/unity/trusty-1332947

** Description changed:

+ [ Impact ]
+ 
  Text scaling value is ignored by dash buttons (filters and preview
  actions).
  
-  - From u-c-c → accessibility → enable Big Text option
+  - From u-c-c → accessibility → enable Big Text option
  
  Filters and preview action buttons should match this option.
+ 
+ [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any code change in the Unity desktop shell has the potential to
+ introduce new crashes or lockups.
+ 
+ [ Other Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
+ 14.10 where it has been in production use for some time without apparent
+ regression.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1362162/+attachment/4292982/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1362162

Title:
  Dash buttons do not honour the text scaling

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Text scaling value is ignored by dash buttons (filters and preview
  actions).

   - From u-c-c → accessibility → enable Big Text option

  Filters and preview action buttons should match this option.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change in the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1362162/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1354498] Re: Switcher Icons emblem (count) it's too small

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1066971

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1354498

Title:
  Switcher Icons emblem (count) it's too small

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  It should have a count emblem with a size proprtional on the icon size
  itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1354498/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1361751] Re: Launcher Icon shortcut labels don't honor text scaling

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Branch unlinked: lp:~unity-team/unity/trusty-1332947

** Description changed:

+ [ Impact ]
+ 
  Text scaling value is ignored by icons overlay text.
  
-  - From u-c-c → accessibility → enable Big Text option
+  - From u-c-c → accessibility → enable Big Text option
  
  Icons overlay text should honor that setting.
+ 
+ [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any code change to the Unity desktop shell has the potential to
+ introduce new crashes or lockups.
+ 
+ [ Other Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
+ 14.10 where it has been in production use for several weeks without
+ apparent regression.

** Patch added: debdiff between 1:0.9.11.2+14.04.20140714-0ubuntu1 and 
proposed fix
   
https://bugs.launchpad.net/unity/+bug/1361751/+attachment/4292981/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1361751

Title:
  Launcher Icon shortcut labels don't honor text scaling

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Text scaling value is ignored by icons overlay text.

   - From u-c-c → accessibility → enable Big Text option

  Icons overlay text should honor that setting.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for several weeks without
  apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1361751/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1362346] Re: Dash/Hud/Spread search bar text doesn't honour the font scaling settings

2015-01-06 Thread Stephen M. Webb
** Branch unlinked: lp:~unity-team/unity/trusty-1332947

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1362346

Title:
  Dash/Hud/Spread search bar text doesn't honour the font scaling
  settings

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Text scaling value is ignored by the dash search bar and the spread
  filter bar.

   - From u-c-c → accessibility → enable Big Text option

  Text should size should be increased in both search bar hint and
  content.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1362346/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1362346] Re: Dash/Hud/Spread search bar text doesn't honour the font scaling settings

2015-01-06 Thread Stephen M. Webb
Attached debdiff between trusty-updates and SRU.

** Description changed:

+ [ Impact ]
+ 
  Text scaling value is ignored by the dash search bar and the spread
  filter bar.
  
-  - From u-c-c → accessibility → enable Big Text option
+  - From u-c-c → accessibility → enable Big Text option
  
  Text should size should be increased in both search bar hint and
  content.
+ 
+ [ Test Case ]
+ 
+ See above.
+ 
+ [ Regression Potential ]
+ 
+ Any code change to the Unity desktop shell has the potential to
+ introduce new crashes or lockups.
+ 
+ [ Other Info ]
+ 
+ The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
+ 14.10 where it has been in production use for some time without apparent
+ regressions.

** Patch added: debdiff between unity_7.2.3+14.04.20140826-0ubuntu1 and 
unity_7.2.4+14.04.20141217-0ubuntu1
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1362346/+attachment/4292983/+files/unity_7.2.4%2B14.04.20141217-0ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1362346

Title:
  Dash/Hud/Spread search bar text doesn't honour the font scaling
  settings

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Text scaling value is ignored by the dash search bar and the spread
  filter bar.

   - From u-c-c → accessibility → enable Big Text option

  Text should size should be increased in both search bar hint and
  content.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  apparent regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1362346/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1423394] Re: Unity Desktop Crashes when using Google Chrome Browser

2015-02-18 Thread Stephen M. Webb
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:

  apport-collect 1423394

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: unity (Ubuntu)
   Status: New = Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1423394

Title:
  Unity Desktop Crashes when using Google Chrome Browser

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1.) Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2.) google-chrome-stable:
Installed: 40.0.2214.111-1
Candidate: 40.0.2214.111-1
Version table:
   *** 40.0.2214.111-1 0
  500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
  100 /var/lib/dpkg/status

  3.) Expect to see video play and no crashing.

  4.) When using Google Chrome (current version 40.0.2214.111 (64-bit))
  and attempting to watch any Youtube video, the Unity Desktop
  experiences a crash and the Unity Desktop (unity start/search and task
  bar) disappear. I am unable to launch a terminal window. All Window
  menus disappear (i.e. Minimize, Maximize, Close) including those that
  are related to the top right shutdown/restart/logoff menu. Desktop
  background remains viewable and Desktop icons are also viewable.
  Keyboard input starts to malfunction in window sections.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1423394/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1417615] Re: [regression][vivid] Menus don't have shadows any more

2015-03-18 Thread Stephen M. Webb
I hardly think this has anything to do with Unity 8, it's an artifact of
the new GTK+ extents handling and requires changes in Compiz to support
that under Unity 7.

** Package changed: unity8 (Ubuntu) = unity (Ubuntu)

** Changed in: unity (Ubuntu)
   Status: New = Triaged

** Changed in: unity (Ubuntu)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1417615

Title:
  [regression][vivid] Menus don't have shadows any more

Status in Compiz:
  Invalid
Status in Themes for Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  On vivid, no menus have shadows any more. Not dropdowns, not popups.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: compiz 1:0.9.12.0+15.04.20150202-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Feb  3 15:40:45 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21fa]
  InstallationDate: Installed on 2015-01-27 (7 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150127)
  MachineType: LENOVO 2325MN1
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic.efi.signed 
root=UUID=0aebf517-a645-434f-94d1-56ad3c6bb2a0 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325MN1
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2325MN1:pvrThinkPadX230:rvnLENOVO:rn2325MN1:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325MN1
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.0+15.04.20150202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Feb  3 09:45:19 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.16.2.901-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1417615/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1432484] Re: ctrl+alt+t hot key doesn't open terminal

2015-03-16 Thread Stephen M. Webb
Testing on a fully up-to-date (as of 2015-03-06) Vivid Vervet session
fails to reproduce this problem.

Please open a terminal (using eg. alt-f2 and typing x-terminal-emulator)
and enter the following command.

  gsettings get org.gnome.settings-daemon.plugins.media-keys terminal

and paste the result into this bug report.

** Changed in: unity (Ubuntu)
   Status: New = Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1432484

Title:
  ctrl+alt+t hot key doesn't open terminal

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1) Description:   Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) unity:
Installed: 7.3.1+15.04.20150227-0ubuntu1
Candidate: 7.3.1+15.04.20150227-0ubuntu1
Version table:
   *** 7.3.1+15.04.20150227-0ubuntu1 0
  500 http://mirrors.accretive-networks.net/ubuntu/ vivid/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) ctrl+alt+t should open terminal
  4) nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150227-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar 15 21:55:08 2015
  DistUpgraded: 2015-03-15 19:32:57,918 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-9-generic, x86_64: installed
   nvidia-346-updates, 346.47, 3.19.0-9-generic, x86_64: installed
   nvidia-346-updates-uvm, 346.47, 3.19.0-9-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:3662]
  InstallationDate: Installed on 2014-04-21 (329 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=d43fa8fe-98d7-4cbc-9f5a-845fe940823f ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-03-16 (0 days ago)
  dmi.bios.date: 05/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1605
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1605:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59+git20150310.fcff9e21-0ubuntu0ricotz~utopic
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Mar 15 21:49:49 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft IntelliMouse® Optical MOUSE, id 8
   inputDarfon Wireless Keyboard  Mouse KEYBOARD, id 9
   inputDarfon Wireless Keyboard  Mouse KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   Output   DVI-0   DisplayPort-0  
HDMI-0 
   product id9896 
   vendor HWP
  xserver.version: 2:1.17.1-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1432484/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner

2015-03-15 Thread Stephen M. Webb
This is a largely misleading bug, at least as far as Unity is concerned.

The default set up is to rotate all user-session logs once every hour,
with 7 previous logs saved compressed.  With a normally operating
desktop session, this should be more than good enough.

Where things go awry is if you get something like Xorg or an X11 client
spamming the logs with messages.  All application messages from programs
running in the desktop session get logged to the desktop session log,
generally called gnome-session-Unity.log or unity7.log, depending on the
release of Ubuntu, or unity-panel-service.log for indicators.  The
misleading bit is that the vast majority of these spam messages are not
in fact coming from Unity (which is relatively quiet) but from some
application program you have chosen to run by clicking on a desktop icon
or indicator you have installed.

In short, there is nothing Unity can do to reduce the amount of garbage
being logged from third-party application programs.  Unity has no
control over what an arbitrary program outputs and does not have any
access to the output streams from applications that it launches so it
could add filters.

The only way to get bugs in arbitrary applications fixed is to file bugs
against the broken applications explicitly.  Filing a bug against the
desktop shell that launches the applications will not bring much joy.

I'm marking this as invalid for Unity, since the problem does not
originate in Unity nor is it possible to provide a fix in Unity for
problems elsewhere.  Bugs need to be filed against the individual
applications causing the problem.

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1240848

Title:
  ~/.cache/upstart takes up around 70GB of space due to unity and
  mediascanner

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

Bug description:
  I just noticed that ~/.cache/upstart/ folder on my computer is taking
  up 69GB of space. Upon further investigation, I found out that
  mediascanner.log and unity-panel-service.log take 12GB and 54GB of
  space respectively.

  I'm not entirely sure if this is related to upstart as I had removed
  logrotate package because of a conflict.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1432484] Re: ctrl+alt+t hot key doesn't open terminal

2015-03-16 Thread Stephen M. Webb
Also, please paste the output of update-alternatives --display x
-terminal-emulator

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1432484

Title:
  ctrl+alt+t hot key doesn't open terminal

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1) Description:   Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) unity:
Installed: 7.3.1+15.04.20150227-0ubuntu1
Candidate: 7.3.1+15.04.20150227-0ubuntu1
Version table:
   *** 7.3.1+15.04.20150227-0ubuntu1 0
  500 http://mirrors.accretive-networks.net/ubuntu/ vivid/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) ctrl+alt+t should open terminal
  4) nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150227-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar 15 21:55:08 2015
  DistUpgraded: 2015-03-15 19:32:57,918 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-9-generic, x86_64: installed
   nvidia-346-updates, 346.47, 3.19.0-9-generic, x86_64: installed
   nvidia-346-updates-uvm, 346.47, 3.19.0-9-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:3662]
  InstallationDate: Installed on 2014-04-21 (329 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=d43fa8fe-98d7-4cbc-9f5a-845fe940823f ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-03-16 (0 days ago)
  dmi.bios.date: 05/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1605
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1605:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59+git20150310.fcff9e21-0ubuntu0ricotz~utopic
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Mar 15 21:49:49 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft IntelliMouse® Optical MOUSE, id 8
   inputDarfon Wireless Keyboard  Mouse KEYBOARD, id 9
   inputDarfon Wireless Keyboard  Mouse KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   Output   DVI-0   DisplayPort-0  
HDMI-0 
   product id9896 
   vendor HWP
  xserver.version: 2:1.17.1-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1432484/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1432484] Re: ctrl+alt+t hot key doesn't open terminal

2015-03-16 Thread Stephen M. Webb
Also, please attach $HOME/.cache/upstart/unity-settings-daemon.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1432484

Title:
  ctrl+alt+t hot key doesn't open terminal

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1) Description:   Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) unity:
Installed: 7.3.1+15.04.20150227-0ubuntu1
Candidate: 7.3.1+15.04.20150227-0ubuntu1
Version table:
   *** 7.3.1+15.04.20150227-0ubuntu1 0
  500 http://mirrors.accretive-networks.net/ubuntu/ vivid/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) ctrl+alt+t should open terminal
  4) nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150227-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar 15 21:55:08 2015
  DistUpgraded: 2015-03-15 19:32:57,918 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-9-generic, x86_64: installed
   nvidia-346-updates, 346.47, 3.19.0-9-generic, x86_64: installed
   nvidia-346-updates-uvm, 346.47, 3.19.0-9-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:3662]
  InstallationDate: Installed on 2014-04-21 (329 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=d43fa8fe-98d7-4cbc-9f5a-845fe940823f ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-03-16 (0 days ago)
  dmi.bios.date: 05/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1605
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1605:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59+git20150310.fcff9e21-0ubuntu0ricotz~utopic
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Mar 15 21:49:49 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft IntelliMouse® Optical MOUSE, id 8
   inputDarfon Wireless Keyboard  Mouse KEYBOARD, id 9
   inputDarfon Wireless Keyboard  Mouse KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   Output   DVI-0   DisplayPort-0  
HDMI-0 
   product id9896 
   vendor HWP
  xserver.version: 2:1.17.1-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1432484/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1398287] Re: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen

2015-03-17 Thread Stephen M. Webb
** Description changed:

+ [Impact]
+ 
  When the power button is pressed, the shutdown dialog will be displayed.
- Then clicks the 'Lock' button on the HUD and it sometimes takes about
- 30~60s to lock screen. This happens on many Intel-only platforms.
+ Then clicks the 'Lock' button in the shutdown dialog and it sometimes
+ takes about 30~60s to lock screen. This happens on many Intel-only
+ platforms.
  
  PS: If user moves the cursor out of the dialog window after clicking the
  'Lock' button, it will switch to lock screen immediately.
+ 
+ [Test Case]
+ 
+ See description under Impact' above.
+ 
+ [Regression Potential]
+ 
+ The fix for this problem involves releasing the grab on the input
+ devices earlier in the sequence, allowing the animation sequence to
+ begin immediately without a grab-release timeout.  It is unlikely that
+ this could introduce any regressions.
+ 
+ [Other Info]
+ 
+ This fix  was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivid
+ Vervet dev release where it has been in test for some time without
+ incident.

** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1398287

Title:
  Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  When the power button is pressed, the shutdown dialog will be
  displayed. Then clicks the 'Lock' button in the shutdown dialog and it
  sometimes takes about 30~60s to lock screen. This happens on many
  Intel-only platforms.

  PS: If user moves the cursor out of the dialog window after clicking
  the 'Lock' button, it will switch to lock screen immediately.

  [Test Case]

  See description under Impact' above.

  [Regression Potential]

  The fix for this problem involves releasing the grab on the input
  devices earlier in the sequence, allowing the animation sequence to
  begin immediately without a grab-release timeout.  It is unlikely that
  this could introduce any regressions.

  [Other Info]

  This fix  was cherry picked for Ubuntu 14.04 LTS from the Ubuntu
  Vivid Vervet dev release where it has been in test for some time
  without incident.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1398287/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1363534] Re: Wrong keyboard shortcuts for Workspaces in Dash overlay

2015-03-17 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Triaged = In Progress

** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu)
   Importance: Undecided = Low

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Low

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1363534

Title:
  Wrong keyboard shortcuts for Workspaces in Dash overlay

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  The Shortcuts displays the wrong key sequence for switching
  workspaces.

  [Test Case]

  (1) Enable workspaces (System Settings  Appearance  Behavior  Enable 
Workspaces).
  (2) Hold down the Super key until the Shortcuts window appears.
  (3) Under Workspaces it should display Shift + Ctrl + Alt + Arrow Keys and 
not Shift + Ctrl + Alt + Left + Arrow Keys.

  [Regression Potential]

  Unlikely.

  [Other Info]

  This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivi
  Vervet dev release where it has been in production use for some time
  without regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1363534/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1413411] Re: underscore in mounted drive name mishandled in menu

2015-03-17 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Description changed:

+ [Impact]
+ 
  If you have a mounted drive with an underscore in it's name (e.g.
  host_S), then, when you right-click on the drive icon in the sidebar,
  the menu interprets the underscore as a keyboard-shortcut indicator, so
  shows the name as hostS (with S underlined). Hovering over the drive
  results in the correct host_S name; the bug is only in the right-click
  menu. Note that right-clicking on the Files icon will show a menu that
  includes the correct mounted disk names. It is only right-clicking on
  the drive-icons themselves that shows the incorrect name.
  
- Ubuntu 14.10
+ [Test Case]
  
- ProblemType: Bug
- DistroRelease: Ubuntu 14.10
- Package: unity 7.3.1+14.10.20141016-0ubuntu1
- ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
- Uname: Linux 3.16.0-23-generic x86_64
- ApportVersion: 2.14.7-0ubuntu8
- Architecture: amd64
- CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
- CurrentDesktop: Unity
- Date: Thu Jan 22 11:51:46 2015
- InstallationDate: Installed on 2015-01-21 (0 days ago)
- InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
- SourcePackage: unity
- UpgradeStatus: No upgrade log present (probably fresh install)
+ (1) Create a mountable device with an underscore in its volume name (eg. 
host_S).
+ (2) Right click on the icon for tha drive in the Launcher.  It should display 
the underscore character correctly as a part of the drive name, and not as an 
underline.
+ 
+ [Regression Potential]
+ 
+ None.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in production use for some time
+ without apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1413411

Title:
  underscore in mounted drive name mishandled in menu

Status in One Hundred Papercuts:
  In Progress
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  If you have a mounted drive with an underscore in it's name (e.g.
  host_S), then, when you right-click on the drive icon in the sidebar,
  the menu interprets the underscore as a keyboard-shortcut indicator,
  so shows the name as hostS (with S underlined). Hovering over the
  drive results in the correct host_S name; the bug is only in the
  right-click menu. Note that right-clicking on the Files icon will
  show a menu that includes the correct mounted disk names. It is only
  right-clicking on the drive-icons themselves that shows the incorrect
  name.

  [Test Case]

  (1) Create a mountable device with an underscore in its volume name (eg. 
host_S).
  (2) Right click on the icon for tha drive in the Launcher.  It should display 
the underscore character correctly as a part of the drive name, and not as an 
underline.

  [Regression Potential]

  None.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time
  without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1413411/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 860970] Re: Dash called with super key above fullscreen app is not interactive or does not show up at all.

2015-03-17 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = High

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Description changed:

- Steps to reproduce :
- - launch an application in fullscreen (Firefox, Totem…)
- - hit the Super key to call the dash
+ [IMPACT]
  
- - Unity 5.x: The dash is displayed, but it is click through…
- - Unity 6.x: The dash is not displayed at all.
+ The Dash was rendered underneath fullscreen windows so it was invisible,
+ although it grabs keyboard input.
  
- In both cases, the cause of this bug is because the Unity Nux windows
- are not being stacked above the fullscreen window.
+ [TEST CASE]
  
- -
- Desired resolution:
+ - Launch an application in fullscreen (Firefox, Totem).
+ - Hit the Super key to call the dash.
+ - The Dash should appear.
+ - Keyboard input should be directed to the Dash.
+ - Clicking anywhere on the full screen application should close the Dash.
  
- - If a window is fullscreen and the Dash is invoked, the Dash should be
- displayed on top of the full screen window.
+ [REGRESSION POTENTIAL]
  
- - Apps should remain full screen when the dash is opened
+ No known regression potential.
  
- - Any actions the user performs on top of the Dash area should be sent
- to the Dash, not the full screen application.
+ [OTHER INFO]
  
- - Clicking anywhere on the full screen application should close the Dash
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in production use for some time
+ without apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/860970

Title:
  Dash called with super key above fullscreen app is not interactive or
  does not show up at all.

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Triaged
Status in Unity 6.0 series:
  Won't Fix
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Precise:
  Triaged
Status in unity source package in Trusty:
  In Progress

Bug description:
  [IMPACT]

  The Dash was rendered underneath fullscreen windows so it was
  invisible, although it grabs keyboard input.

  [TEST CASE]

  - Launch an application in fullscreen (Firefox, Totem).
  - Hit the Super key to call the dash.
  - The Dash should appear.
  - Keyboard input should be directed to the Dash.
  - Clicking anywhere on the full screen application should close the Dash.

  [REGRESSION POTENTIAL]

  No known regression potential.

  [OTHER INFO]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time
  without apparent regression.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1159249] Re: HUD does not show up over fullscreen window

2015-03-17 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1159249

Title:
  HUD does not show up over fullscreen window

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  The HUD was not being rendered above fullscreen windows although it
  would grab the keyboard.

  [TEST CASE]

  1. Open some site in firefox

  2. Go to fullscreen mode (F11)

  3. Press Alt once.

  4  The HUD should appear and you should be able to interact with it.

  [REGRESSION POTENTIAL]

  No known regression potential.

  [OTHER INFO]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time
  without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1159249/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1159249] Re: HUD does not show up over fullscreen window

2015-03-17 Thread Stephen M. Webb
** Description changed:

- Step to reproduce:
+ [Impact]
+ 
+ The HUD was not being rendered above fullscreen windows although it
+ would grab the keyboard.
+ 
+ [TEST CASE]
  
  1. Open some site in firefox
  
  2. Go to fullscreen mode (F11)
  
  3. Press Alt once.
  
- The HUD will not appear, but actually it will start and grab the
- keyboard, You will not be able to use F11 again to exit the fullscreen
- mode. You will be able to interact with HUD blindely.
+ 4  The HUD should appear and you should be able to interact with it.
  
- 4. Exit the fullscreen mode using mouse and you will see the HUD active
- and ready.
+ [REGRESSION POTENTIAL]
  
- ProblemType: Bug
- DistroRelease: Ubuntu 13.04
- Package: unity 6.12.0daily13.03.20-0ubuntu1
- ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
- Uname: Linux 3.8.0-13-generic x86_64
- ApportVersion: 2.9.2-0ubuntu2
- Architecture: amd64
- CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
- Date: Sun Mar 24 02:01:54 2013
- EcryptfsInUse: Yes
- InstallationDate: Installed on 2013-01-01 (81 days ago)
- InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac 
(20121017.3)
- MarkForUpload: True
- ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
- SourcePackage: unity
- UpgradeStatus: Upgraded to raring on 2013-03-18 (4 days ago)
+ No known regression potential.
+ 
+ [OTHER INFO]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in production use for some time
+ without apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1159249

Title:
  HUD does not show up over fullscreen window

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  The HUD was not being rendered above fullscreen windows although it
  would grab the keyboard.

  [TEST CASE]

  1. Open some site in firefox

  2. Go to fullscreen mode (F11)

  3. Press Alt once.

  4  The HUD should appear and you should be able to interact with it.

  [REGRESSION POTENTIAL]

  No known regression potential.

  [OTHER INFO]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time
  without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1159249/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1413790] Re: It's possible to bypasss lockscreen if user is in nopasswdlogin group.

2015-03-17 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Description changed:

- Lightdm should not emit logind unlock signal when the user is not
- prompted for a password. This can lead to a security issue:
+ [IMPACT]
+ A user is presented with a password dialog even if a member of the 
nopasswdlogin group (and may not have a password).
  
- # Log-in (unity session).
- # Add the current user to nopasswdlogin group.
- # Lock the sessions.
- # Session indicator-Switch account...
- # Login in again.
+ [TEST CASE]
  
- Expected behavior:
- The lockscreen is still active.
+ (1) Create a test user.
+ (2) Add the test user to the nopasswdlogin group.
+ (3) Log in to a Unity session using that acocunt.
+ (4) Lock the screen.
+ (5) Attempt to unlock the screen:  no password prompt should be presented.
  
- Current behavior:
- The session in unlocked.
+ [REGRESSION POTENTIAL]
  
- We could workaround the issue directly in unity, but IMHO would be
- cleaner to avoid that lightdm is emitting the logind signal.
+ Conceivably allowing a login with no authentication could present
+ unexpected vulnerabilities in which unforseen code paths also exercise
+ this function.  Care has been taken by the developer to avoid such
+ cases.
+ 
+ [OTHER INFO]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in production use for some time
+ without apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1413790

Title:
  It's possible to bypasss lockscreen if user is in nopasswdlogin group.

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [IMPACT]
  A user is presented with a password dialog even if a member of the 
nopasswdlogin group (and may not have a password).

  [TEST CASE]

  (1) Create a test user.
  (2) Add the test user to the nopasswdlogin group.
  (3) Log in to a Unity session using that acocunt.
  (4) Lock the screen.
  (5) Attempt to unlock the screen:  no password prompt should be presented.

  [REGRESSION POTENTIAL]

  Conceivably allowing a login with no authentication could present
  unexpected vulnerabilities in which unforseen code paths also exercise
  this function.  Care has been taken by the developer to avoid such
  cases.

  [OTHER INFO]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time
  without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1413790/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1241757] Re: Unity Launcher always assumes default background is active for a couple of seconds

2015-03-17 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Low

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Description changed:

- This happened for the first time after upgrading to Ubuntu 13.10 (64-bit) and 
it won't just go...
- Every time the computer boots and autologins to my desktop, I see the default 
background only behind the Unity Launcher for a couple of seconds, and then it 
is replaced with the current wallpaper.
+ [IMPACT]
+ 
+ Every time the computer boots and autologins to my desktop, I see the
+ default background only behind the Unity Launcher for a couple of
+ seconds, and then it is replaced with the current wallpaper.
+ 
+ [TEST CASE]
+ 
+ (1) Configure the desktop to use a non-default wallpaper.
+ (2) Log in to a Unity session and observe the area behind the Launcher.
+ 
+ [REGRESSION POTENTIAL]
+ 
+ The solution to this problem was to eliminate the animation of the BFB
+ icon on initial startup.  Potentially this could cause the animation to
+ not run at other times, although even if this did occur, it is unlikely
+ to be noticed.
+ 
+ [OTHER INFO]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in production use for some time
+ without apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241757

Title:
  Unity Launcher always assumes default background is active for a
  couple of seconds

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [IMPACT]

  Every time the computer boots and autologins to my desktop, I see the
  default background only behind the Unity Launcher for a couple of
  seconds, and then it is replaced with the current wallpaper.

  [TEST CASE]

  (1) Configure the desktop to use a non-default wallpaper.
  (2) Log in to a Unity session and observe the area behind the Launcher.

  [REGRESSION POTENTIAL]

  The solution to this problem was to eliminate the animation of the BFB
  icon on initial startup.  Potentially this could cause the animation
  to not run at other times, although even if this did occur, it is
  unlikely to be noticed.

  [OTHER INFO]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time
  without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1241757/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1413773] Re: [Regressions] Dash dnd icons rendered behind dash.

2015-03-17 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Description changed:

- In Ubuntu 15.04 dragged icons are rendered behind dash.
+ [IMPACT]
+ 
+ Dragged icons are rendered behind dash.
+ 
+ [REGRESSION POTENTIAL]
+ 
+ No known regression potential.
+ 
+ [OTHER INFO]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in production use for some time
+ without apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1413773

Title:
  [Regressions] Dash dnd icons rendered behind dash.

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [IMPACT]

  Dragged icons are rendered behind dash.

  [REGRESSION POTENTIAL]

  No known regression potential.

  [OTHER INFO]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time
  without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1413773/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1404486] Re: Session dialog does not show up over fullscreen windows.

2015-03-17 Thread Stephen M. Webb
** Changed in: unity
   Status: Fix Released = Triaged

** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Description changed:

+ [IMPACT]
+ 
  Unity session dialog does not show up over a fullscreen window if you
  press the hardware button.
+ 
+ [TEST CASE]
+ 
+ (1) open an application (eg. Firefix) and make it fullscreen (F11)
+ (2) press the power button or choose Shut Down... from the Session indicator 
menu.
+ (3) The Session (shutdown/restart) dialog should appear and be interactive.
+ 
+ [REGRESSION POTENTIAL]
+ 
+ No known regression potential.
+ 
+ [OTHER INFO]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in production use for some time
+ without apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1404486

Title:
  Session dialog does not show up over fullscreen windows.

Status in Unity:
  Triaged
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [IMPACT]

  Unity session dialog does not show up over a fullscreen window if you
  press the hardware button.

  [TEST CASE]

  (1) open an application (eg. Firefix) and make it fullscreen (F11)
  (2) press the power button or choose Shut Down... from the Session indicator 
menu.
  (3) The Session (shutdown/restart) dialog should appear and be interactive.

  [REGRESSION POTENTIAL]

  No known regression potential.

  [OTHER INFO]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time
  without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1404486/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.

2015-03-17 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu)
   Importance: Undecided = Critical

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Critical

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Description changed:

- I have a user reporting an incidence that trusty unity desktop got
- unlocked on its own:
+ [Impact]
  
- In the morning, after coming to my desk, I just pressed the space bar
- on my desktop to get the monitors woken up. The monitors came up with
- the locked screen and then after a while it got unlocked to my
- surprise!
+ Certain code paths may cause the Unity lockscreen to crash, which can
+ allow the screen to be unlocked without a password entry.
  
-    There was compiz crash file on his system at that time. However, I
- don't have the right debug symbols to which file (or function) it
- crashed into. Here is the top part of the stack trace when I ran apport-
- retrace -s  on his crash file:
+ [Test Case]
  
- 
---
- --- stack trace ---
- #0  0x7ff17ed06608 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
- No symbol table info available.
- #1  0x7ff17ed06cf3 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
- No symbol table info available.
- #2  0x7ff17ed04e2d in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
- No symbol table info available.
- #3  0x7ff17f3fdd02 in g_settings_backend_read (backend=optimized out, 
key=key@entry=0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen, 
expected_type=0x7ff1877135a0 g_variant_type_info_basic_chars, 
default_value=default_value@entry=0) at 
/build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
- value = optimized out
- #4  0x7ff17f401c7b in g_settings_read_from_backend 
(settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920, 
user_value_only=user_value_only@entry=0, default_value=default_value@entry=0) 
at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
- value = optimized out
- fixup = optimized out
- path = 0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen
- #5  0x7ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570, 
key=0x2087618 disable-lock-screen) at 
/build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
- skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c 
disable-lock-screen, is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length 
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 
g_variant_type_info_basic_chars, minimum = 0x0, maximum = 0x0, default_value 
= 0xb9c5b30, ref_count = 0}
- value = optimized out
- __FUNCTION__ = g_settings_get_value
- 
-
+ Unfortunately this bug only appears under certain race conditions and is
+ not reliably reproduce able.
  
-    The top part of the trash file when viewed in TextEdit has the information 
:
- -
- ProblemType: Crash
- Architecture: amd64
- CrashCounter: 1
- CurrentDesktop: Unity
- Date: Fri Dec 12 10:16:52 2014
- DistroRelease: Ubuntu 14.04
- ExecutablePath: /usr/bin/compiz
- ExecutableTimestamp: 1405349348
- ProcCmdline: compiz
- --
+ [Regression Potential]
  
-    His system is Ubuntu trusty 14.04.1 LTS. Unity installed
- 7.2.3+14.04.20140826-0ubuntu1.0.1 .
+ The change in the code simply assumes that if a screen is already
+ locked, then it is lockable this avoiding certain operations that are
+ inherently racy.  It is possible that this fix does not avoid all
+ possible crash conditions in the lockscreen and there may still be
+ unaccounted-for crashes in the lockscreen.
+ 
+ [Other Info]
+ 
+ This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivid
+ Vervet dev release where it has been in testing for some time.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582

Title:
  [Trusty / Unity] Desktop got unlocked on its own.

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  Certain code paths may cause the Unity lockscreen to crash, which can
  allow the screen to be unlocked without a password entry.

  [Test Case]

  Unfortunately this bug only appears under certain race conditions and
  is not reliably reproduce able.

  [Regression Potential]

  The change in the code simply assumes that if a screen is already
  locked, then it is lockable this avoiding

[Touch-packages] [Bug 1401911] Re: When the screen is locked edge barriers should be deactivated.

2015-03-17 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu)
   Importance: Undecided = Low

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Low

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Description changed:

+ [Impact]
+ 
  If the screen is locked, launcher/panel edge barriers at the moment are
  active.
+ 
+ [Test Case]
+ 
+ In a multi-monitor environment, lock the screen and move the mouse
+ between monitors.  There should be no sticky edge between the
+ monitors.
+ 
+ [Regression Potential]
+ 
+ Code in the paths that handle the edge barriers was changed.
+ Potentially this could impact the reveal of a hidden Launcher if there
+ were errors introduced in these code paths.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in production use for some time.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1401911

Title:
  When the screen is locked edge barriers should be deactivated.

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  If the screen is locked, launcher/panel edge barriers at the moment
  are active.

  [Test Case]

  In a multi-monitor environment, lock the screen and move the mouse
  between monitors.  There should be no sticky edge between the
  monitors.

  [Regression Potential]

  Code in the paths that handle the edge barriers was changed.
  Potentially this could impact the reveal of a hidden Launcher if there
  were errors introduced in these code paths.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1401911/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1363534] Re: Wrong keyboard shortcuts for Workspaces in Dash overlay

2015-03-17 Thread Stephen M. Webb
** Description changed:

- When you hold the Super key and the overlay with the keyboard shortcut
- opens:
+ [Impact]
  
- Under Workspaces it says:
+ The Shortcuts displays the wrong key sequence for switching workspaces.
  
- Ctrl + Alt + Left + Arrow Keys: Switches Workspaces
- Shift + Ctrl + Alt + Left + Arrow Keys: Moves focused window to another 
workspace
+ [Test Case]
  
+ (1) Enable workspaces (System Settings  Appearance  Behavior  Enable 
Workspaces).
+ (2) Hold down the Super key until the Shortcuts window appears.
+ (3) Under Workspaces it should display Shift + Ctrl + Alt + Arrow Keys and 
not Shift + Ctrl + Alt + Left + Arrow Keys.
  
- The shortcuts are wrong, the + Left makes no sense. Is this supposed to be 
Left Alt? But on the other hand all other shortcuts do not say Left Alt but 
just Alt, so that's probably not it.
+ [Regression Potential]
  
- Anyway, the correct shortcuts are:
+ Unlikely.
  
- Ctrl + Alt + Arrow Keys: Switches Workspaces
- Shift + Ctrl + Alt + Arrow Keys: Moves focused window to another workspace
+ [Other Info]
  
- This is also what it says on the official help:
- https://help.ubuntu.com/14.04/ubuntu-help/shell-keyboard-shortcuts.html
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 14.04
- Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
- ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
- Uname: Linux 3.13.0-34-generic x86_64
- NonfreeKernelModules: nvidia wl
- ApportVersion: 2.14.1-0ubuntu3.3
- Architecture: amd64
- CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,ezoom,unityshell,expo,scale]
- CurrentDesktop: Unity
- Date: Sun Aug 31 01:58:00 2014
- EcryptfsInUse: Yes
- InstallationDate: Installed on 2012-09-15 (714 days ago)
- InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
- SourcePackage: unity
- UpgradeStatus: Upgraded to trusty on 2014-03-29 (154 days ago)
+ This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivi
+ Vervet dev release where it has been in production use for some time
+ without regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1363534

Title:
  Wrong keyboard shortcuts for Workspaces in Dash overlay

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  The Shortcuts displays the wrong key sequence for switching
  workspaces.

  [Test Case]

  (1) Enable workspaces (System Settings  Appearance  Behavior  Enable 
Workspaces).
  (2) Hold down the Super key until the Shortcuts window appears.
  (3) Under Workspaces it should display Shift + Ctrl + Alt + Arrow Keys and 
not Shift + Ctrl + Alt + Left + Arrow Keys.

  [Regression Potential]

  Unlikely.

  [Other Info]

  This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivi
  Vervet dev release where it has been in production use for some time
  without regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1363534/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1061792] Re: Memory Leak in Unity (Compiz)

2015-03-17 Thread Stephen M. Webb
Just a note:  gtk-window-decorator is incompatible with Unity (they can
not be run at the same time)  and it's unlikely that a leak in gtk-
window-decorator is relaed to a problem in Unity.  If there is a problem
with gtk-window-decorator it needs to be reported against the Compiz
project not as a comment against a bug in the Unity project.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1061792

Title:
  Memory Leak in Unity (Compiz)

Status in Unity:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  There seems to be a memory leak in Unity that comes with use (not
  age).

  Hardware: ThinkPad W510 (nVidia Quadro FX 880M, driver 304.51), Core2
  -Duo-based desktop with nVidia 560Ti (same driver)

  Software: Quantal Beta, up-to-the-moment updates, both 64- and 32-bit
  (one of each).

  *Note: I can *not* test with nouveau.  Not only is it completely
  unsuitable for laptops due to terrible power management, but neither
  computer will boot with it - I get the PFIFO stuff, even though the
  -16 kernel was supposed to fix that.

  Steps to reproduce:

  1) Log into Unity and launch System Monitor (gnome-system-monitor).
  Set to view all processes and organize by the memory column.  Take
  note of the amount of RAM taken by the Compiz and Xorg processes.

  2) Open a bunch of programs.  I use: Nautilus, Gnome-Terminal, Chrome,
  Banshee, EasyTag, EasyMP3Gain, Empathy, Eclipse, and Rhythmbox.

  3) Close all of the programs except gnome-system-monitor.  Note the
  increase in RAM the Compiz and Xorg processes take.

  4) Repeat steps 3-4.  Memory on each process steadily rises.

  It isn't by a lot, but it creates an environment wherein the longer
  one uses one's Unity session, the less free RAM one has to work with
  (as neither process ever seems to give up any of its RAM, ever, not
  even after 10 hours of use).

  I don't seem to have any stability or performance issues stemming from
  this.

  ALSO: Opening the dash at all raises the RAM usage by a LOT, and
  subsequent openings of the dash (poking around, clicking on new
  buttons that reveal icons I haven't seen before, etc) also grows the
  process's RAM.  By a LOT on the first run, but by a noticeable amount
  on later runs.

  *I* think this is a pretty high-priority issue, but as the RAM use and
  growth isn't all THAT large (~0.5/1 MiB every time steps 2-3 are
  repeated), I could understand if it weren't marked critical... but I
  think any leak is critical, so there's my bias.

  STEALTH EDIT: I want to point out that just leaving the system logged
  in does not cause Unity *or* Xorg to use more RAM over time.  Not even
  with the indicator-multiload running.

  STEALTH EDIT #2: All lenses and scopes except the Application lens have been 
uninstalled, and do not factor into this.  So I'm pretty sure we don't have a 
runaway call in any indexer or anything like it.
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DistroRelease: Ubuntu 12.10
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926)
  NonfreeKernelModules: nvidia
  Package: unity 6.8.0-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5
  Tags: quantal third-party-packages
  Uname: Linux 3.5.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1061792/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1433074] Re: unity pointer vertically off where click occurs on login

2015-03-17 Thread Stephen M. Webb
** Package changed: unity (Ubuntu) = unity8 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1433074

Title:
  unity pointer vertically off where click occurs on login

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Attempted to log in via unity ( unity8-desktop-session-mir
  1.0.12+15.04.2 ) option via lightdm, and was presented with a Welcome
  to your new phone (odd since this isn't a phone - it's a laptop, but
  whatever) menu asking to select a language -- but the screen was off
  center on my monitor, and (worse) attempts to click on the menu
  resulted in clicks happening maybe 20-30 pixels below where the
  pointer was located.  This rendered that particular menu unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150227-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Tue Mar 17 08:46:33 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0689]
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0689]
  InstallationDate: Installed on 2014-07-09 (250 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140708)
  MachineType: Acer TravelMate P273-MG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA70_HC
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate P273-MG
  dmi.product.version: V2.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Tue Mar 17 08:45:09 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1433074/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1133051] Re: Can't name new directory in unity

2015-03-17 Thread Stephen M. Webb
** Also affects: nautilus (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1133051

Title:
  Can't name new directory in unity

Status in Nautilus:
  New
Status in Unity:
  New
Status in nautilus package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  When i right click and select create new folder, i got new folder
  with name untitled folder and cursor on that name for edit it.

  i type new name, and then press enter for submit new name, and all work 
fine.
  But, if i change keyboard layout when type new name, untitled folder 
submitted as though i press enter. And then, i must press f2 and edit name 
again.

  P.S. I switch keyboard layout by pressing left Alt+Shift.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.18.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic-pae 3.2.35
  Uname: Linux 3.2.0-37-generic-pae i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  295.40  Thu Apr  5 21:28:09 PDT 
2012
   GCC version:  gcc версия 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Tue Feb 26 11:18:58 2013
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current, 295.40, 3.2.0-36-generic-pae, i686: installed
   nvidia-current, 295.40, 3.2.0-37-generic-pae, i686: installed
  GraphicsCard:
   NVIDIA Corporation GT200b [GeForce GTX 285] [10de:05e3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:065b]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  JockeyStatus:
   xorg:nvidia_current - Драйвер ускоренной графики NVIDIA (Проприетарные, 
Активирован, Используется)
   xorg:nvidia_current_updates - Драйвер для графических карт на базе NVIDIA 
(плановые обновления) (Проприетарные, Выключен, Не используется)
   xorg:nvidia_experimental_304 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Проприетарные, Выключен, Не используется)
   xorg:nvidia_experimental_310 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Проприетарные, Выключен, Не используется)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic-pae 
root=UUID=6aa28a00-f43c-46ba-897b-79a07feac445 ro quiet splash ipv6.disable=1 
vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section Device
Identifier  Default Device
Option  NoLogoTrue
   EndSection
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.7.12-0ubuntu1
  version.libdrm2: libdrm2 2.4.39-0ubuntu0.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.11
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1133051/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1374942] Re: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog

2015-03-18 Thread Stephen M. Webb
Attaching the test script to use to reproduce the problem or test the
solution.

** Description changed:

- Unkown cause.
+ [Impact]
  
- ProblemType: Crash
- DistroRelease: Ubuntu 14.10
- Package: unity 7.3.1+14.10.20140915-0ubuntu1
- ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
- Uname: Linux 3.16.0-18-generic x86_64
- ApportVersion: 2.14.7-0ubuntu2
- Architecture: amd64
- CurrentDesktop: Unity
- Date: Sun Sep 28 16:19:49 2014
- ExecutablePath: /usr/bin/compiz
- InstallationDate: Installed on 2014-09-03 (25 days ago)
- InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902)
- ProcCmdline: compiz
- ProcEnviron:
-  PATH=(custom, no user)
-  LANGUAGE=en_AU:en
-  XDG_RUNTIME_DIR=set
-  LANG=en_AU.UTF-8
-  SHELL=/bin/bash
- Signal: 5
- SourcePackage: unity
- StacktraceTop:
-  ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
-  _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
-  XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
-  XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6
-  ?? () from /usr/lib/compiz/libunityshell.so
- Title: compiz crashed with signal 5 in _XReply()
- UpgradeStatus: No upgrade log present (probably fresh install)
- UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ An invalid line of code would occasionally cause Unity to crash.
+ 
+ [Test Case]
+ 
+ (1) Download and run the attached Python script test-1374942 to create a 
candidate application.
+ (2) Press the close button and wait for the Force Quit dialog to come up.
+ (3) Choose the Force Quit button.
+ 
+ The desktop shell should not crash.
+ 
+ [Regression Potential]
+ 
+ The fix for this bug involves converting an integer into a string and
+ appending it to an error message instead of adding the integer value to
+ the address of the error message.  There is unlikely to be a regression
+ from this.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been under daily use for some time
+ without apparent regressioon.

** Attachment added: Test script test-1374942
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1374942/+attachment/4349322/+files/test-1374942

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1374942

Title:
  compiz crashed with signal 5 in _XReply() from
  unity::decoration::ForceQuitDialog::ForceQuitDialog

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  An invalid line of code would occasionally cause Unity to crash.

  [Test Case]

  (1) Download and run the attached Python script test-1374942 to create a 
candidate application.
  (2) Press the close button and wait for the Force Quit dialog to come up.
  (3) Choose the Force Quit button.

  The desktop shell should not crash.

  [Regression Potential]

  The fix for this bug involves converting an integer into a string and
  appending it to an error message instead of adding the integer value
  to the address of the error message.  There is unlikely to be a
  regression from this.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been under daily use for some time
  without apparent regressioon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1374942/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1302955] Re: upstart user session leaks all the dbus events it receives

2015-03-18 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1302955

Title:
  upstart user session leaks all the dbus events it receives

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Confirmed
Status in unity source package in Trusty:
  In Progress

Bug description:
  Easiest way to see this:
  0. Make sure there is a user session job with a dbus rule (eg 
unity-greeter-session-broadcast)
  1. Install and run system-load-indicator (indicator-multiload)
  2. Set the update interval to 100ms
  3. Now watch the memory use of init --user increase by 100kb per second
  4. Also open up upstart-monitor to see all the dbus messages being sent

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  5 18:17:40 2014
  InstallationDate: Installed on 2013-06-22 (287 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2013-12-05 (120 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1302955/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1312137] Re: Local menus broken for Qt apps after opening dialog

2015-03-18 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Description changed:

+ [Impact]
+ 
  I have selected to have window menus in the window's title bar. This
  works great, except for Qt apps. After selecting a menu item in a Qt app
- that produces a dialog, the menu is no longer accessible. e.g.
+ that produces a dialog, the menu is no longer accessible.  The only way
+ to get the menu back, is to switch to another window, and then back to
+ the affected app.
+ 
+ [Test Case]
  
  1. Start qtcreator
  2. Resize window so that it is not maximised
  3. Select 'Help' - 'About Qt Creator'
  4. Dismiss 'About Qt Creator' dialog
- 5. Move mouse over window titlebar - menu is no longer shown.
+ 5. Move mouse over window titlebar.
  
- The only way to get the menu back, is to switch to another window, and
- then back to the affected app.
+ [Regression Potential]
  
- Note: This does not seem to affect the 'File' dialog from QtCreator -
- I'm assuming this is because it loads the Gtk file dialog.
+ It's possible other menu interaction bugs may have been introduced.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry-picked from the Ubuntu Vivid
+ Vervet dev release where it has been in production use for some time
+ without apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1312137

Title:
  Local menus broken for Qt apps after opening dialog

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  I have selected to have window menus in the window's title bar. This
  works great, except for Qt apps. After selecting a menu item in a Qt
  app that produces a dialog, the menu is no longer accessible.  The
  only way to get the menu back, is to switch to another window, and
  then back to the affected app.

  [Test Case]

  1. Start qtcreator
  2. Resize window so that it is not maximised
  3. Select 'Help' - 'About Qt Creator'
  4. Dismiss 'About Qt Creator' dialog
  5. Move mouse over window titlebar.

  [Regression Potential]

  It's possible other menu interaction bugs may have been introduced.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry-picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time
  without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1312137/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1302955] Re: upstart user session leaks all the dbus events it receives

2015-03-18 Thread Stephen M. Webb
** Description changed:

- Easiest way to see this:
+ [Impact]
+ 
+ The unity-panel-service process has been caching D-Bus messages sent
+ from upstart, effectively leaking memory.  The solution replaces the
+ offending code with a single upstart event emission.
+ 
+ [Test Case]
+ 
  0. Make sure there is a user session job with a dbus rule (eg 
unity-greeter-session-broadcast)
  1. Install and run system-load-indicator (indicator-multiload)
  2. Set the update interval to 100ms
  3. Now watch the memory use of init --user increase by 100kb per second
  4. Also open up upstart-monitor to see all the dbus messages being sent
  
+ [Regression Potential]
  
- ProblemType: Bug
- DistroRelease: Ubuntu 14.04
- Package: upstart 1.12.1-0ubuntu1
- ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
- Uname: Linux 3.13.0-22-generic x86_64
- ApportVersion: 2.14-0ubuntu1
- Architecture: amd64
- CurrentDesktop: Unity
- Date: Sat Apr  5 18:17:40 2014
- InstallationDate: Installed on 2013-06-22 (287 days ago)
- InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621)
- SourcePackage: upstart
- UpgradeStatus: Upgraded to trusty on 2013-12-05 (120 days ago)
- UpstartBugCategory: Session
- UpstartRunningSessionCount: 1
- UpstartRunningSessionVersion: init (upstart 1.12.1)
- UpstartRunningSystemVersion: init (upstart 1.12.1)
+ Some kind of hidden functionality depending on upstart events sent
+ through D-Bus to the unity-panel-service may have become disconnected.
+ Unlikely.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in regular use for some time
+ without apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1302955

Title:
  upstart user session leaks all the dbus events it receives

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Confirmed
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  The unity-panel-service process has been caching D-Bus messages sent
  from upstart, effectively leaking memory.  The solution replaces the
  offending code with a single upstart event emission.

  [Test Case]

  0. Make sure there is a user session job with a dbus rule (eg 
unity-greeter-session-broadcast)
  1. Install and run system-load-indicator (indicator-multiload)
  2. Set the update interval to 100ms
  3. Now watch the memory use of init --user increase by 100kb per second
  4. Also open up upstart-monitor to see all the dbus messages being sent

  [Regression Potential]

  Some kind of hidden functionality depending on upstart events sent
  through D-Bus to the unity-panel-service may have become disconnected.
  Unlikely.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in regular use for some time
  without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1302955/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1390562] Re: Moving the mouse out from the decoration hides the LIMs when Alt is pressed

2015-03-18 Thread Stephen M. Webb
** Description changed:

+ [Impact]
+ 
+ Pressing the Alt key while a locally integrated menu is open causes the
+ menu to hide.
+ 
+ [Test Case]
+ 
  Prerequisite: from Appearance - Behavior - Set menu visible in window
  titlebar
  
  1. Open a window with menus
  2. Press and keep pressed the Alt key
  3. Menus will show
  4. Move the mouse over the window decoration
  5. Move the mouse out from the window decoration
  
- Actual behavior:
+ Incorrect behavior:
  6. Menus hides, also if the Alt key is pressed.
  
  Expected:
  6. Menus should stay visible until the Alt key is released.
+ 
+ [Regression Potential]
+ 
+ Additional incorrect menu behaviour may be introduced.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in use for some time without
+ apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1390562

Title:
  Moving the mouse out from the decoration hides the LIMs when Alt is
  pressed

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]

  Pressing the Alt key while a locally integrated menu is open causes
  the menu to hide.

  [Test Case]

  Prerequisite: from Appearance - Behavior - Set menu visible in
  window titlebar

  1. Open a window with menus
  2. Press and keep pressed the Alt key
  3. Menus will show
  4. Move the mouse over the window decoration
  5. Move the mouse out from the window decoration

  Incorrect behavior:
  6. Menus hides, also if the Alt key is pressed.

  Expected:
  6. Menus should stay visible until the Alt key is released.

  [Regression Potential]

  Additional incorrect menu behaviour may be introduced.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in use for some time without
  apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1390562/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1390562] Re: Moving the mouse out from the decoration hides the LIMs when Alt is pressed

2015-03-18 Thread Stephen M. Webb
** Changed in: unity (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Low

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) = Stephen M. Webb (bregma)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1390562

Title:
  Moving the mouse out from the decoration hides the LIMs when Alt is
  pressed

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  Prerequisite: from Appearance - Behavior - Set menu visible in
  window titlebar

  1. Open a window with menus
  2. Press and keep pressed the Alt key
  3. Menus will show
  4. Move the mouse over the window decoration
  5. Move the mouse out from the window decoration

  Actual behavior:
  6. Menus hides, also if the Alt key is pressed.

  Expected:
  6. Menus should stay visible until the Alt key is released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1390562/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 955193] Re: Menu bar - add option for the global menu to make it always visible

2015-03-18 Thread Stephen M. Webb
** Description changed:

+ [ Impact ]
  
- 1) In System Settings/Appearance/Behavior ( see section 2.2 of 
http://tinyurl.com/7c7nofq ), the Application Menu options should be 
Integrated in menu bar and hidden (default) and Integrated in menu bar and 
visible
+ [Test Case]
  
- 2) If Integrated in menu bar and visible is selected, the menus should
- always be shown, in exactly the same manner they are currently displayed
- when the pointer is moved over the menu bar.
+ (1) enable menus in the window title bar System Settings  Appearance  
Behavior  Show the menus for a window  In the menu bar
+ (2) run gsettings set com.canonical.Unity always-show-menus true in a 
terminal
+ (3) move the mouse around between windows
+ 
+ The menus should remain displayed
+ 
+ [Regression Potential]
+ 
+ Any change to the menu functionality has the potential to cause
+ volunteer functionality in menu behaviour.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
+ Vervet dev release where it has been in production use for some time
+ with no apparent regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/955193

Title:
  Menu bar - add option for the global menu to make it always visible

Status in Ayatana Design:
  Triaged
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  New

Bug description:
  [ Impact ]

  [Test Case]

  (1) enable menus in the window title bar System Settings  Appearance  
Behavior  Show the menus for a window  In the menu bar
  (2) run gsettings set com.canonical.Unity always-show-menus true in a 
terminal
  (3) move the mouse around between windows

  The menus should remain displayed

  [Regression Potential]

  Any change to the menu functionality has the potential to cause
  volunteer functionality in menu behaviour.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid
  Vervet dev release where it has been in production use for some time
  with no apparent regression.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1427785] Re: Duplicate processes started after Resume of amd64 bit

2015-03-19 Thread Stephen M. Webb
Most of the processes you're seeing are run by the session upstart.  Try
'ps fax' to see the process tree.  You also get to see what state these
processes are in that way.

Still, this has nothing to do with Unity, which neither handles system
power states nor session process control.  You might want ot check logs
in /var/log/upstart or ~/.cache/upstart for more clues.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1427785

Title:
  Duplicate processes started after Resume of amd64 bit

Status in unity package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux ajsc855 3.13.0-46-generic #76-Ubuntu SMP Thu Feb 26 18:52:13 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  $ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION=Ubuntu 14.04.2 LTS

  Toshiba Satellite C855,  4GB RAM, 720GB HD

  I typically run Thunderbird, Firefox, a terminal or two, Gthumb, Gimp,
  Qcad, Gedit, Libreoffice, Inkscape, Document Viewer and occasionally
  Virtualbox.

  I just noticed this a couple of weeks ago, so I am guessing a recent
  update started it.

  It seems to me that there are quite a few duplicate copies of some
  processes populating memory after suspending/resuming a session for a
  few days.  Namely, dbus-daemon, gvfsd and gconfd-2.  The more I
  suspend/resume the session, the more of these processes appear.  After
  a while they start using up a significant amount of memory and system
  response seems to slow down.

  Logging out and back in did not alleviate the problem. Rebooting did.
  But, I will have to reboot again in a week to free up the memory used
  by these duplicate processes.

  The example session used to get the following results was probably
  well over a week in use.

  Before rebooting:
  $ ps -ef prereboot.txt
  $ grep -i dbus-daemon prereboot.txt|wc -l
  40
  $ grep -i gvfsd prereboot.txt|wc -l
  78
  $ grep -i gconfd-2 prereboot.txt|wc -l
  37

  After rebooting:
  $ ps -ef postreboot.txt
  $ grep -i dbus-daemon postreboot.txt|wc -l
  4
  $ grep -i gvfsd postreboot.txt|wc -l
  5
  $ grep -i gconfd-2 postreboot.txt|wc -l
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1427785/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 857487] Re: compiz crashed with SIGSEGV in CompScreen::insertServerWindow()

2015-03-19 Thread Stephen M. Webb
** Changed in: compiz
   Status: Fix Committed = Fix Released

** No longer affects: unity (Ubuntu)

** No longer affects: unity

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/857487

Title:
  compiz crashed with SIGSEGV in CompScreen::insertServerWindow()

Status in Compiz:
  Fix Released
Status in Compiz Core:
  Fix Released
Status in compiz package in Ubuntu:
  Fix Released

Bug description:
  sem detalhes

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: unity 4.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic i686
  ApportVersion: 1.23-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Fri Sep 23 11:56:42 2011
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x806d081 
_ZN10CompScreen18insertServerWindowEP10CompWindowm+193:mov
0xc(%eax),%eax
   PC (0x0806d081) ok
   source 0xc(%eax) (0x0025) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   CompScreen::insertServerWindow(CompWindow*, unsigned long) ()
   PrivateWindow::reconfigureXWindow(unsigned int, XWindowChanges*) ()
   CompWindow::configureXWindow(unsigned int, XWindowChanges*) ()
   CompWindow::updateAttributes(CompStackingUpdateMode) ()
   PrivateWindow::processMap() ()
  Title: compiz crashed with SIGSEGV in CompScreen::insertServerWindow()
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  UserGroups: adm admin lpadmin nopasswdlogin sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/857487/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 800592] Re: firefox window mapped fullscreen gets mapped under gnome-panel

2015-03-19 Thread Stephen M. Webb
** Changed in: compiz
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/800592

Title:
  firefox window mapped fullscreen gets mapped under gnome-panel

Status in Compiz:
  Fix Released
Status in Unity:
  Fix Released
Status in compiz package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Run gnome classic
  Start firefox
  Fullscreen it
  Close it
  Reopen it

  It gets stacked underneath the panels. That sucks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/800592/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 926979] Re: compiz crashed with SIGSEGV in nux::Propertybool::operator=(bool const) from unity::dash::DashView::AnalyseLensURI(std::string const) from unity::dash::DashView::

2015-03-20 Thread Stephen M. Webb
** Changed in: unity/7.0
   Status: Triaged = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/926979

Title:
  compiz crashed with SIGSEGV in nux::Propertybool::operator=(bool
  const) from unity::dash::DashView::AnalyseLensURI(std::string const)
  from unity::dash::DashView::OnActivateRequest(_GVariant*)

Status in Unity:
  In Progress
Status in Unity 5.0 series:
  Triaged
Status in Unity 6.0 series:
  Won't Fix
Status in Unity 7.0 series:
  Invalid
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  In Progress

Bug description:
  Clicked dash, Internet applications.

  Opened a new bug as the others appear to suggest a fix is released for
  those bugs.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unity 5.0.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
  Uname: Linux 3.2.0-3-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Sun Feb  5 14:51:39 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7eff5ff51d10 _ZN3nux8PropertyIbEaSERKb+32: mov
0x18(%rdi),%rdi
   PC (0x7eff5ff51d10) ok
   source 0x18(%rdi) (0x03f0) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   nux::Propertybool::operator=(bool const) () from 
/usr/lib/compiz/libunityshell.so
   unity::dash::DashView::AnalyseLensURI(std::string const) () from 
/usr/lib/compiz/libunityshell.so
   unity::dash::DashView::OnActivateRequest(_GVariant*) () from 
/usr/lib/compiz/libunityshell.so
   unity::UBusManager::OnCallback(_GVariant*, void*) () from 
/usr/lib/compiz/libunityshell.so
   ?? () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in nux::Propertybool::operator=()
  UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo 
usrp video

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/926979/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1430248] [NEW] FTBFS on Ubuntu Vivid (out of date lcov)

2015-03-10 Thread Stephen M. Webb
Public bug reported:

The unity-scope-home package fails to build during CI with the following
error.


checking for lcov version... invalid
configure: error: You must have one of the following versions of lcov: 1.6 1.7 
1.8 1.9 (found: 1.11).
== config.log ==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

** Affects: unity-scope-home (Ubuntu)
 Importance: Critical
 Assignee: Stephen M. Webb (bregma)
 Status: In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-home in
Ubuntu.
https://bugs.launchpad.net/bugs/1430248

Title:
  FTBFS on Ubuntu Vivid (out of date lcov)

Status in unity-scope-home package in Ubuntu:
  In Progress

Bug description:
  The unity-scope-home package fails to build during CI with the
  following error.

  
  checking for lcov version... invalid
  configure: error: You must have one of the following versions of lcov: 1.6 
1.7 1.8 1.9 (found: 1.11).
  == config.log ==
  This file contains any messages produced by compilers while
  running configure, to aid debugging if configure makes a mistake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-home/+bug/1430248/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1430784] [NEW] FTBFS using GCC-5

2015-03-12 Thread Stephen M. Webb
Public bug reported:

Unity fails to build from source using GCC 5.0 or later.

An excerpt from the failing build log follows.

/build/buildd/unity-7.3.1+15.04.20150126/hud/HudController.cpp:160:96:   
required from here
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:89:30: error: no match 
for call to '(sigc::bound_mem_functor1void, unity::hud::Controller, bool) 
(std::nullptr_t)'
 { return functor_(_A_arg1); }
  ^
In file included from 
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:9:0,
 from /usr/include/sigc++-2.0/sigc++/functors/slot.h:7,
 from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/Nux-4.0/NuxCore/Object.h:30,
 from /usr/include/Nux-4.0/NuxCore/NuxCore.h:730,
 from /usr/include/Nux-4.0/Nux/Nux.h:26,
 from 
/build/buildd/unity-7.3.1+15.04.20150126/hud/pch/hud_pch.hh:28:
/usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:1855:12: note: candidate: 
T_return sigc::bound_mem_functor1T_return, T_obj, T_arg1::operator()(typename 
sigc::type_traitT_arg3::take) const [with T_return = void; T_obj = 
unity::hud::Controller; T_arg1 = bool; typename sigc::type_traitT_arg3::take 
= const bool] near match
   T_return operator()(typename type_traitT_arg1::take _A_a1) const
^
/usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:1855:12: note:   conversion 
of argument 1 would be ill-formed:
In file included from /usr/include/sigc++-2.0/sigc++/functors/slot.h:7:0,
 from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/Nux-4.0/NuxCore/Object.h:30,
 from /usr/include/Nux-4.0/NuxCore/NuxCore.h:730,
 from /usr/include/Nux-4.0/Nux/Nux.h:26,
 from 
/build/buildd/unity-7.3.1+15.04.20150126/hud/pch/hud_pch.hh:28:
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:89:30: error: 
converting to 'bool' from 'std::nullptr_t' requires direct-initialization 
[-fpermissive]
 { return functor_(_A_arg1); }
  ^
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:89:30: error: 
return-statement with a value, in function returning 'void' [-fpermissive]
hud/CMakeFiles/hud-lib.dir/build.make:103: recipe for target 
'hud/CMakeFiles/hud-lib.dir/HudController.cpp.o' failed

** Affects: unity
 Importance: Medium
 Assignee: Stephen M. Webb (bregma)
 Status: Triaged

** Affects: unity (Ubuntu)
 Importance: Medium
 Assignee: Stephen M. Webb (bregma)
 Status: Triaged

** Also affects: unity
   Importance: Undecided
   Status: New

** Changed in: unity
   Status: New = Triaged

** Changed in: unity
   Importance: Undecided = Medium

** Changed in: unity
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Changed in: unity
Milestone: None = 7.3.2

** Summary changed:

- FTBFS on using GCC-5
+ FTBFS using GCC-5

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1430784

Title:
  FTBFS using GCC-5

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

Bug description:
  Unity fails to build from source using GCC 5.0 or later.

  An excerpt from the failing build log follows.

  /build/buildd/unity-7.3.1+15.04.20150126/hud/HudController.cpp:160:96:   
required from here
  /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:89:30: error: no 
match for call to '(sigc::bound_mem_functor1void, unity::hud::Controller, 
bool) (std::nullptr_t)'
   { return functor_(_A_arg1); }
^
  In file included from 
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:9:0,
   from /usr/include/sigc++-2.0/sigc++/functors/slot.h:7,
   from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
   from /usr/include/sigc++-2.0/sigc++/signal.h:8,
   from /usr/include/Nux-4.0/NuxCore/Object.h:30,
   from /usr/include/Nux-4.0/NuxCore/NuxCore.h:730,
   from /usr/include/Nux-4.0/Nux/Nux.h:26,
   from 
/build/buildd/unity-7.3.1+15.04.20150126/hud/pch/hud_pch.hh:28:
  /usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:1855:12: note: candidate: 
T_return sigc::bound_mem_functor1T_return, T_obj, T_arg1::operator()(typename 
sigc::type_traitT_arg3::take) const [with T_return = void; T_obj = 
unity::hud::Controller; T_arg1 = bool; typename sigc::type_traitT_arg3::take 
= const bool] near match
 T_return operator()(typename type_traitT_arg1::take _A_a1) const
  ^
  /usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:1855:12: note:   conversion 
of argument 1 would be ill-formed:
  In file included

[Touch-packages] [Bug 1398287] Re: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen

2015-03-11 Thread Stephen M. Webb
** Changed in: unity/7.2
 Assignee: (unassigned) = Stephen M. Webb (bregma)

** Changed in: unity/7.2
   Status: Triaged = In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1398287

Title:
  Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  When the power button is pressed, the shutdown dialog will be
  displayed. Then clicks the 'Lock' button on the HUD and it sometimes
  takes about 30~60s to lock screen. This happens on many Intel-only
  platforms.

  PS: If user moves the cursor out of the dialog window after clicking
  the 'Lock' button, it will switch to lock screen immediately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1398287/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


<    1   2   3   4   5   6   7   8   9   10   >