Ayatana Design

Bug #160311
Comment #357

Comment 357 for bug 160311

Revision history for this message

madbiologist (me-again) wrote on 2013-01-31:

#357

Aleve - I think what Andrea was trying to say is what John Lea subsequently said - the specific bug for the window title bar/top border resizing issue is bug #717444. However that does ignore your first paragraph about the left border being more difficult to grab than the bottom and right borders. It is a puzzling dilemma about whether the latter should be opened as a new bug or not - technically it might have a different cause, but usability-wise it has the same effect.

What really annoys me is the comments made by Sam Spilsbury:

> 1. It is fixed in Unity-3D, which has been the default since 12.10
> 2. It isn't worth fixing in Unity-2D, since it would require extensive patching to metacity's frame display code

If I understand this bug's description correctly, this problem exists in Unity-2D on Ubuntu 12.04 "Precise Pangolin". This is an LTS release - according to https://wiki.ubuntu.com/Releases it will be supported on both the desktop and the server until April 2017. This should mean fully and wholly supported, not partly supported.

I also disagree with marking this bug's unity-2d task as Invalid while the upstream GNOME bug is still open as this implies that even if GNOME were to develop and deploy a fix, Ubuntu would not adopt the fix. And of course the fact that GNOME are considering fixing this issue should not in any way preclude Ubuntu from attempting to fix it.

> 3. Comments like these are not helpful.

Sam - these comments are not intended to help you. They are intended to help the people using Unity-2D on Precise. And even if the issue of providing full-support for Precise were to be sadly and frustratingly ignored, advising people using Unity-2D on Precise to upgrade to Ubuntu 12.10 "Quantal Quetzal" is unlikely to help matters, due to the fact that if their GPU is too old/weak to run Unity-3D then their CPU is also likely to be too old/weak to run Unity-3D using the LLVMpipe fallback code - see bug 1046497 and bug 1055936.

Aleve - I think what Andrea was trying to say is what John Lea subsequently said - the specific bug for the window title bar/top border resizing issue is bug #717444.  However that does ignore your first paragraph about the left border being more difficult to grab than the bottom and right borders.  It is a puzzling dilemma about whether the latter should be opened as a new bug or not - technically it might have a different cause, but usability-wise it has the same effect.

What really annoys me is the comments made by Sam Spilsbury:

> 1. It is fixed in Unity-3D, which has been the default since 12.10
> 2. It isn't worth fixing in Unity-2D, since it would require extensive patching to metacity's frame display code

If I understand this bug's description correctly, this problem exists in Unity-2D on Ubuntu 12.04 "Precise Pangolin".  This is an LTS release - according to https://wiki.ubuntu.com/Releases it will be supported on both the desktop and the server until April 2017.  This should mean fully and wholly supported, not partly supported.

I also disagree with marking this bug's unity-2d task as Invalid while the upstream GNOME bug is still open as this implies that even if GNOME were to develop and deploy a fix, Ubuntu would not adopt the fix.  And of course the fact that GNOME are considering fixing this issue should not in any way preclude Ubuntu from attempting to fix it.

> 3. Comments like these are not helpful.

Sam - these comments are not intended to help you.  They are intended to help the people using Unity-2D on Precise.  And even if the issue of providing full-support for Precise were to be sadly and frustratingly ignored, advising people using Unity-2D on Precise to upgrade to Ubuntu 12.10 "Quantal Quetzal" is unlikely to help matters, due to the fact that if their GPU is too old/weak to run Unity-3D then their CPU is also likely to be too old/weak to run Unity-3D using the LLVMpipe fallback code - see bug 1046497 and bug 1055936.