Windows maximise underneath dock after monitor sleep

[Alan Pope 🍺🐧🐱 🦄]

Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock.

If I switch to the application in question, unmaximise and re-maximise, it goes back to maximising inside the usable area of my desktop.

But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.3-2ubuntu2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 5 19:21:39 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-06-11 (267 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago)

[jan.public (jan.public-redhat-bugs)]

Description of problem:

I have a two display setup in GNOME Wayland. One DVI, 100% scaled regular display and one Display Link, 150% scaled HiDPI display. When I maximize a window, for example gedit, on the right 150% scaled screen and lock the system with Tux-L, after unlocking the system (after waiting for roughly 30 minutes) gedit moved to the other 100% scaled window and is there in a weird place (see screenshot).

How reproducible:
Not always, maybe related to the waiting time between locking and unlocking the screen. I will try to figure out if this is related and update this issue with my findings.

Steps to Reproduce:
1. Set up a configuration as described.
2. Open gedit maximized on the right display.
3. Lock the system with Tux-L
4. Wait for a relative long time (say 30 minutes)
5. Unlock the screen by typing in the password.

Actual results:
gedit moved to the left display and is positioned in a wrong way (see screenshot)

Expected results:
gedit should be in the same display as when the system was locked.

Additional info:
I do not think that this issue is related to suspending the system, as I could reproduce after fresh boot without having the system suspended.

$ inxi -G
Graphics: Device-1: AMD Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] driver: amdgpu v: kernel
           Display: wayland server: Fedora Project X.org 1.20.8 driver: ati,modesetting unloaded: fbdev,vesa resolution:
           1: 1920x1080~60Hz 2: 1680x1050~60Hz
           OpenGL: renderer: Radeon RX 560 Series (POLARIS11 DRM 3.37.0 5.7.11-200.fc32.x86_64 LLVM 10.0.0) v: 4.6 Mesa 20.1.5

[jan.public (jan.public-redhat-bugs)]

Created attachment 1714638
GNOME display settings

[jan.public (jan.public-redhat-bugs)]

Created attachment 1714639
gedit moved to the other screen and in a wrong position

[jan.public (jan.public-redhat-bugs)]

You can see in the screenshot that it looks like that gedit is aligned at the top of the larger window, but having the size of the smaller window. In reality the bottoms of the windows are aligned, not the tops.

[jan.public (jan.public-redhat-bugs)]

See also: bug 1815492.

[jan.public (jan.public-redhat-bugs)]

See also: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419

[jan.public (jan.public-redhat-bugs)]

See also: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1001984

[jan.public (jan.public-redhat-bugs)]

See also:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2092
https://bugs.launchpad.net/gnome-shell/+bug/1295267
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/380
https://github.com/linuxmint/Cinnamon/issues/5487

[jan.public (jan.public-redhat-bugs)]

In GNOME mutter gitlab (https://gitlab.gnome.org/GNOME/mutter/-/issues/1419#note_937356) it was pointed out to me that the incorrect placement of the windows in the monitors happens when the monitors of different size and resolution are aligned at the bottom. When they are aligned at the top, the problem disappears.

[Daniel van Vugt (vanvugt)]

Assigning to Ubuntu Dock for now, because nobody is going to notice the bug without it. Although the eventual fix might end up being in some other package.

[Daniel van Vugt (vanvugt)]

Tracking in https://github.com/micheleg/dash-to-dock/issues/1370

[Daniel van Vugt (vanvugt)]

I think it's a mutter issue only:

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1755
https://gitlab.gnome.org/GNOME/mutter/-/issues/1627

[Daniel van Vugt (vanvugt)]

Looks like the fix is 8dd1e26d051 in salsa, so that will be released in:

https://launchpad.net/ubuntu/+source/mutter/3.38.4-1ubuntu1

(there's a typo in the changelog but it is this bug)

[Daniel van Vugt (vanvugt)]

Oh. There's also a gnome-shell fix coming in https://launchpad.net/ubuntu/+source/gnome-shell/3.38.4-1ubuntu1

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-shell - 3.38.4-1ubuntu1

---------------
gnome-shell (3.38.4-1ubuntu1) hirsute; urgency=medium

  * Merge with debian, containing a new upstream release
  * debian/control: (Build-)Depends on mutter 3.38.4
  * debian/patches:
    - Refresh
    - Remove input-thread related patches
    - Fix handling of OSK codes in keyboard (LP: #1918738)
    - Ensure Cancel button uses proper arguments (LP: #1918666)
    - Allow updating struts in Overview (LP: #1917939)
    - Configure Login Scree: cleanup code to match shell's JS
  * Remaining changes with debian:
    - Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
      gnome-themes-standard-data, gnome-backgrounds
    - Add some Recommends:
      + ubuntu-session (| gnome-session) to have the ubuntu session available
      + xserver-xorg-legacy
      + yaru-theme-gnome-shell for the default ubuntu theming
    - Update debian/gbp.conf with Ubuntu settings
    - gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
    - ubuntu/desktop_detect.patch:
      + add caching for desktop detection to avoid querying the current
        desktop env variable as iterate through the list each time. For the
        time of the Shell process, we can expect this env variable to stay
        stable.
    - ubuntu/smarter_alt_tab.patch:
      + quick alt-tab (without showing up the switcher) switch only between
        the last window of the last 2 applications to be focused instead of
        raising all windows of those apps.
    - ubuntu/lightdm-user-switching.patch:
      + Allow user switching when using LightDM.
    - ubuntu/lock_on_suspend.patch
      + Respect Ubuntu's lock-on-suspend setting.
    - ubuntu/background_login.patch
      + Change default background color as we modified the default GDM color
        for our ubuntu session.
    - ubuntu/gdm_alternatives.patch
      + Add support for GDM3 theme alternatives
    - optional-hot-corner.patch
      + enable patch proposed by upstream developer already in package (but
        not in series) to add a settings for optional hot corner activation.
    - main-show-an-error-message-on-gnome-shell-crash.patch,
      global-make-possible-to-set-debug-flags-dynamically.patch,
      main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
      main-add-backtrace-crashes-all-and-backtrace-all.patch,
      sessionMode-add-support-for-debugFlags-parameter.patch:
      + Improve debug JS tracing for crash reports
    - st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch:
      + Fix crash on theme changes
    - ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
      + stop searches when requested from UI
    - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
      + Show monitor scaled cursor when magnifier is enabled
    - Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814)

gnome-shell (3.38.4-1) unstable; urgency=medium

  * Team upload
  * New upstream release
    - Fix missing X11 fallback icons (particularly for games and other
      programs not installed system-wide), a regression in 3.37.3
    - Fix a Shell crash when a...

[Daniel van Vugt (vanvugt)]

mutter (3.38.4-1ubuntu1) hirsute; urgency=medium

[Daniel van Vugt (vanvugt)]

Bug 1922795 seems to suggest this regression has crept into focal-updates now.

[Daniel van Vugt (vanvugt)]

Confirmed you only need the mutter fix. The gnome-shell fix was in error.

[Daniel van Vugt (vanvugt)]

Turns out I wrote a new fix for this bug by accident, proposed in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1785

[Daniel van Vugt (vanvugt)]

Also proposed in https://salsa.debian.org/gnome-team/gnome-shell/-/merge_requests/48

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-shell - 3.38.4-1ubuntu2

---------------
gnome-shell (3.38.4-1ubuntu2) hirsute; urgency=medium

  [ Daniel van Vugt ]
  * Add layout-Try-to-allocate-before-getting-size-of-tracke.patch.
    To fix LP: #1919979 and also to re-fix LP: #1917939
    (LP: #1919979, #1917939)
  * Drop layout-Allow-updating-struts-in-Overview.patch.
    Because it caused a regression and doesn't seem to have been necessary
    anyway. (LP: #1922772)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Fix suggestions box actor population in non-latin languages
    (LP: #1914230)
  * debian/patches: Enable to use Escape to cancel auth requests (with limits)
    (LP: #1921929)
  * debian/patches: Refresh

 -- Marco Trevisan (Treviño) <email address hidden> Thu, 15 Apr 2021 06:20:27 +0200

[Daniel van Vugt (vanvugt)]

Sorry for the confusion but it is confusing...

* The first gnome-shell fix in comment #8 is bogus. It never worked and was removed in comment #14 because it had also caused regression bug 1922772.

* The first mutter fix included in 3.38.4-1ubuntu1 (comment #6) did work but also caused regression bug 1922034. So the mutter fix has now been removed.

* The second gnome-shell fix in comment #14 is the only fix we are now using.

[fedora-pgm (fedora-pgm-redhat-bugs)]

This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 32 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

[bcotton (bcotton-redhat-bugs)]

Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

[Daniel van Vugt (vanvugt)]

Upstream has just landed a new fix for Mutter v42:

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2103

[Daniel van Vugt (vanvugt)]

It looks like the Ubuntu fix/workaround in gnome-shell (layout-Try-to-allocate-before-getting-size-of-tracke.patch) can be dropped starting in GNOME 42. Because GNOME 42 has the upstream fix https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2103

[Launchpad Janitor (janitor)]

This bug was fixed in the package mutter - 42~beta-1ubuntu2

---------------
mutter (42~beta-1ubuntu2) jammy; urgency=medium

  * debian/patches: Skip monitor-size tests that may fail on autopkgtest

 -- Marco Trevisan (Treviño) <email address hidden> Mon, 14 Mar 2022 02:27:21 +0100

[Felipe Espic (felipeespic)]

This bug is still happening in Ubuntu 22.04LTS some times. (See the attached pic)

[Daniel van Vugt (vanvugt)]

This bug is closed. Please use bug 1961508 instead.

[Jan Vlug (z-j)]

Maybe related to this: https://gitlab.gnome.org/GNOME/mutter/-/issues/230#note_1551972.

[Ali Devrim OĞUZ (devrim-oguz)]

Still happening in Ubuntu 22.04.3 with the latest updates. I have a dual-monitor setup with Wayland. Bug occurs when I lock the screen and unlock it again. Everything gets left behind the dock. I think it is related to dash-to-dock implementation of Ubuntu. There is a workaround which fixes the issue, but it just hides and unhides the panel when unlocked: https://github.com/popov895/dash-to-dock-workaround

Why is the screen state not saved when the screen is locked? It feels like it tries to draw it again and misses the dock as if the screen starts from the edges.

Similar report: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1961508

[Hans109h (hans109h)]

Agreed. Also still affected

[Hans109h (hans109h)]

I've had at least 2 instances where the dash-to-dock workaround fails since installing it this morning, so I don't see that as a viable fix.

[tetsuo29 (russell-martin)]

This bug is happening to me on 22.04.4 with all updates installed. It's minor but also super annoying and the fact that it has gone unfixed for so long makes Ubuntu seem like an unpolished distro which is weird because I generally find Ubuntu to be the best and most polished distro of them all. What can a normal user like myself do to get a bug like this fixed? Make a donation? Keep reporting it here or somewhere else?

[Daniel van Vugt (vanvugt)]

This bug is closed. Please use bug 1961508 instead.