can no longer alt-drag firefox/thunderbird windows above top of screen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
metacity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[General information about the SRU]
* It includes fix for bug 1582687 which was already backported.
* It fixes bug 1509031, bug 1592953 and bug 1596574.
* Other commits are minor bugfixes, the full log can be seen here:
https:/
* There is also a NEWS file, here:
https:/
[Impact]
Windows can not be moved above the top of screen because the coordinates system used is wrong.
[Test Case]
* Launch a non-CSD application, such as Firefox or Thunderbird;
* Try Alt-dragging it above the top of the screen.
[Regression Potential]
The fix is changing the coordinates system to the right one and should not cause any regressions.
-------
After upgrading to 15.10, I can no longer Alt-drag Firefox and Thunderbird windows above the top of the screen. When I attempt to do so, the window snaps downward along the y-axis so that the titlebar aligns with top of screen. Other applications such as gnome-terminal do not seem to be affected.
I ran git-bisect on metacity, and narrowed the regression down to this commit:
https:/
commit 90b36abebdf69be
Author: Alberts Muktupāvels <email address hidden>
Date: Fri Apr 3 23:30:20 2015 +0300
window: add a meta_window_
Based on mutter commits:
https:/
https:/
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: metacity 1:3.17.2-4ubuntu1
ProcVersionSign
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Flashback
Date: Thu Oct 22 13:35:02 2015
InstallationDate: Installed on 2014-09-22 (394 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: metacity
UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)
https:/ /git.gnome. org/browse/ metacity/ commit/ ?id=967eebdd5bd f378e220f385675 6745ea39f7415b
Can you verify that this commit fixes regression and does not introduce new regressions?