Clicking Activities in the corner doesn't work

[Douglas Silva]

[ Impact ]

Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it.

The unclickable spot is exactly one pixel large.

Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again.

Specs:
- Graphics: AMD RX 560
- CPU: Intel Core i3-8100
- Ubuntu 19.10 Eoan

[ Test case ]

- Move the mouse to the top-left corner pixel and click on it
- Activities should open

[ Regression potential ]

Mouse picking location could be wrong in all clutter operations

[Sebastien Bacher (seb128)]

Thank you for your bug report? Do you have any extension installed? Could you test if that's also happening in a GNOME session (you need to install 'gnome-session:' to have the session listed on the login screen)?

[Douglas Silva (o-alquimista)]

No extensions were installed. Also, I'm using the native AMDGPU drivers, not the proprietary ones.

I've tested the vanilla GNOME session as you suggested, and the bug is there too. Due to the hover highlighting of the panel items, I had a visual cue to test with. The highlighting does not happen at the unclickable spot. Move one pixel away from it, and the panel item lits up again.

That was on Xorg, of course. On Wayland, the problem is gone, at least initially. As I said on the initial report, after using the Wayland session for a while, I started having the problem again. No idea what caused it.

[Sebastien Bacher (seb128)]

Thanks for testing a GNOME session, it would be nice to report it upstream as well since it doesn't seem to be due to some extension or Ubuntu specific components
https://gitlab.gnome.org/GNOME/gnome-shell/issues

[Douglas Silva (o-alquimista)]

It was already reported.

Here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
And here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1601

[Daniel van Vugt (vanvugt)]

Thanks for the bug report and screenshot. That does confirm it is https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649

[Daniel van Vugt (vanvugt)]

I will need to debug this more in detail. If we find it is Xorg giving us the negative pointer coordinates then it should be fixed there. But it might just be a mutter bug...

[Dimitrij Mijoski (dimztimz)]

I experience this bug, too. What is interesting is that even if:

1. I hide the top bar of gnome shell with extension,
2. Disable dash-to-dock and
3. Bring a window so it occupies the most top-left corner (or maximize it),

the windows does not react if I click the corner. In this case the expected behavior is to grab and drag the window.

[Daniel van Vugt (vanvugt)]

Fixed in 3.34.3:
https://gitlab.gnome.org/GNOME/mutter/commit/5724310899

[Launchpad Janitor (janitor)]

This bug was fixed in the package mutter - 3.34.3-1ubuntu1

---------------
mutter (3.34.3-1ubuntu1) focal; urgency=medium

  * Merge with debian. Remaining changes:
    + debian/control:
      - Update VCS flags to point to launchpad
    + debian/gbp.conf: update branch to point to ubuntu/master
    + debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
      - X11: Add support for fractional scaling using Randr

mutter (3.34.3-1) unstable; urgency=medium

  * New upstream release
    + Fix window recording on HiDPI
    + Fix top-left pixel being insensitive to clicks (LP: #1849135)

 -- Iain Lane <email address hidden> Mon, 06 Jan 2020 17:56:09 +0000

[Łukasz Zemczak (sil2100)]

Hello Douglas, or anyone else affected,

Accepted mutter into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.34.3-1ubuntu1~19.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Douglas Silva (o-alquimista)]

I have tested 'mutter' version 3.34.3-1ubuntu1~19.10.1 from eoan-proposed on an Xorg session, and it doesn't fix the issue. Testing was made after package installation, followed by a system reboot.

mutter/eoan-proposed,now 3.34.3-1ubuntu1~19.10.1 amd64 [installed]

I don't know what other information to get from this.

[Douglas Silva (o-alquimista)]

Let me add that I also tested a GNOME session (package 'gnome-session') and there was no difference from the results of testing the Ubuntu Xorg session. The proposed package does NOT fix the issue for me.

[Marco Trevisan (Treviño) (3v1n0)]

I can confirm the bug isn't fixed, however, I please ask the SRU team to don't consider this an update-failure not having a regression here, but instead a non-fix.

So I think we can just mark it as verification-needed again and prepare a proper fix for another update.

[Daniel van Vugt (vanvugt)]

That's tricky then. I verified the upstream fix resolved the issue for me and that the same fix is in the above proposed update. So any remaining issue is one that I can't reproduce :(

[Alexey Kulik (doctor-rover)]

Quite strange... I can confirm that the bug is fixed for me in Xorg session in Focal with regular upgrades and in Eoan after updgrade with proposed enabled.
Version of mutter in Eoan is 3.34.3-1ubuntu1~19.10.1
Is there any useful information I can provide?

[Daniel van Vugt (vanvugt)]

To move this bug forward, someone still experiencing problems should please open a new upstream issue at:

  https://gitlab.gnome.org/GNOME/gnome-shell/issues

and tell them that it's different to the current upstream bugs we have (which are definitely fixed and closed):

  https://gitlab.gnome.org/GNOME/mutter/issues/893
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649

[Daniel van Vugt (vanvugt)]

Those still experiencing problems: Do you use multiple monitors or have a single screen?

[Douglas Silva (o-alquimista)]

I'll create the new issue there.

I have only one monitor.

[Douglas Silva (o-alquimista)]

Here's the new issue:

https://gitlab.gnome.org/GNOME/gnome-shell/issues/2164

[Łukasz Zemczak (sil2100)]

As per my discussion with Laney, I will be releasing the mutter + gnome-shell SRU that's currently in eoan-proposed, even though it doesn't seem to be fixing all the issues for users. We'll be re-opening the bugs so that they can be investigated further.

[Launchpad Janitor (janitor)]

This bug was fixed in the package mutter - 3.34.3-1ubuntu1~19.10.1

---------------
mutter (3.34.3-1ubuntu1~19.10.1) eoan; urgency=medium

  * Backport to eoan (LP: #1858683)

mutter (3.34.3-1ubuntu1) focal; urgency=medium

  * Merge with debian. Remaining changes:
    + debian/control:
      - Update VCS flags to point to launchpad
    + debian/gbp.conf: update branch to point to ubuntu/master
    + debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
      - X11: Add support for fractional scaling using Randr

mutter (3.34.3-1) unstable; urgency=medium

  * New upstream release
    + Fix window recording on HiDPI
    + Fix top-left pixel being insensitive to clicks (LP: #1849135)

mutter (3.34.2-2ubuntu1) focal; urgency=medium

  * Merge with debian. Remaining changes:
    + debian/control:
      - Update VCS flags to point to launchpad
    + debian/gbp.conf: update branch to point to ubuntu/master
    + debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
      - X11: Add support for fractional scaling using Randr

mutter (3.34.2-2) unstable; urgency=medium

  * d/p/EGL-Include-EGL-eglmesaext.h.patch: Cherry pick from master. This
    fixes the generated EGL includes for the move of exlext.h from mesa to
    libglvnd, which has just happened in Debian.

mutter (3.34.2-1ubuntu1) focal; urgency=medium

  * Merge with debian including new upstream version 3.34.2 (LP: #1857037):
    - Fix an hang when using DisplayLink with Wayland (LP: #1853357)
    - Kill window effects on destroy (LP: #1844222)
    - Fixed a crash when using various Java apps such as Intellij (LP: #1845281)
    - Fixed a crash when handling X11 events (LP: #1846403)
    - Fixed some double-scaling in wayland
    - More crash and hang fixes
    Remaining changes:
    + debian/control:
      - Update VCS flags to point to launchpad
    + debian/gbp.conf: update branch to point to ubuntu/master
    + debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
      - X11: Add support for fractional scaling using Randr

mutter (3.34.2-1) unstable; urgency=medium

  * Team upload
  * New upstream release
    - d/libmutter-5-0.symbols: Update
    - d/copyright: Update
  * d/gbp.conf: Use upstream/3.34.x branch
  * Remove obsolete Lintian override
  * Standards-Version: 4.4.1 (no changes required)
  * d/tests: Use correct compiler for proposed autopkgtest
    cross-architecture testing support

 -- Marco Trevisan (Treviño) <email address hidden> Wed, 08 Jan 2020 13:31:04 +0000

[Daniel van Vugt (vanvugt)]

Although this was declared fixed in mutter 3.34.3-1, it doesn't matter anymore if anyone thinks it's still an issue for eoan because that's EOL next month.