Resume from suspend on Wayland breaks window positioning

Bug #1778983 reported by Pedro Côrte-Real
44
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Mutter
New
Unknown
mutter (Fedora)
Confirmed
Medium
mutter (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken:

1) The session resumes on the 4th virtual desktop independently on where it was before
2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen)
3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes.

To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 27 20:14:45 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-05-31 (27 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Pedro Côrte-Real (pedrocr) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please report this bug to the Gnome developers here:

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

And if you can, please try to simplify the test case as much as possible.

tags: added: resume
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

When done, please let us know the ID of the new bug.

Revision history for this message
Pedro Côrte-Real (pedrocr) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks.

description: updated
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
tags: added: suspend-resume
Revision history for this message
In , meltingrobot (meltingrobot-redhat-bugs) wrote :

Description of problem:
This issue has been going on for awhile now, probably Fedora 29-31 on this desktop. I have 4 monitors(all having DVI/HDMI audio) Single video card Radeon 590. Anytime I lock/unlock my screen, windows get moved around and my audio output gets changed. It isn't consistent either. Sometimes windows on one monitor get moved to the primary, sometimes windows on monitor 3 get moved to 2. Audio output sometimes stays where it should, sometimes moves to a different monitor, and a lot of times moves to the motherboard aux out which has nothing plugged into it.

Version-Release number of selected component (if applicable):

How reproducible: Highly reproducable

Steps to Reproduce:
1. Lock screen/unlock screen with 4 monitors
2.
3.

Actual results: Windows moved, audio output changed

Expected results: Windows remain on monitor they were on before locking, audio stays on same output

Additional info:

Revision history for this message
In , meltingrobot (meltingrobot-redhat-bugs) wrote :

Just an update, I updated to the 32 Beta today (still Silverblue) and the issue still persists. I lock the screen and unlock and windows are moved to different monitors still.

Revision history for this message
In , jan.public (jan.public-redhat-bugs) wrote :

See also: bug 1878367.

Revision history for this message
In , meltingrobot (meltingrobot-redhat-bugs) wrote :

FYI, this still happens on Fedora 32 Silverblue. Would love to see this go away when 33 comes out, but I don't have a lot of hope unless this gets fixed upstream in Gnome.

Revision history for this message
In , jan.public (jan.public-redhat-bugs) wrote :
affects: gnome-shell (Ubuntu) → mutter (Ubuntu)
Revision history for this message
Jan Vlug (z-j) wrote :

Maybe related: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574251 (though that bug is against xorg).

Revision history for this message
Jan Vlug (z-j) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Those are the same bug but in Compiz. So not really relevant here. This bug is about gnome-shell/mutter.

Revision history for this message
In , bcotton (bcotton-redhat-bugs) wrote :

This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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.

Revision history for this message
In , meltingrobot (meltingrobot-redhat-bugs) wrote :

Bug still exists in 33, was also in 32

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mutter (Ubuntu):
status: New → Confirmed
Revision history for this message
In , meltingrobot (meltingrobot-redhat-bugs) wrote :

Latest update, in Fedora 34, sometimes one monitor won't come out of sleep after unlocking. I have to turn the monitor off/on with the power button to get it working again. The bigger annoyance though is that I lose my volume up/down and mute on my keyboard. Also, volume is full blast until I go into settings and touch the volume bar(even though the volume bar is in the middle)

Revision history for this message
In , boost113 (boost113-redhat-bugs) wrote :

After changing from nvidia to amd I started experiencing the windows moving around problem on Fedora 34 after resuming from suspend or switching one of my monitors on a kvm to a different computer and back. I didn't extensively test, but it seems that for me on gnome with xorg this problem is much smaller, only with wayland I get the problem where 80% of my windows get thrown around. With xorg only one or two windows seem to move their position. That linked gnome bug (https://gitlab.gnome.org/GNOME/mutter/-/issues/1419) seems to still be open.
This is a pretty annoying problem, especially the fact that using a kvm switch causes windows to get thrown around, otherwise I could kinda deal with just rebooting my computer each day instead of using sleep mode.

description: updated
Revision history for this message
Jan Vlug (z-j) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Bug 1927948 is tracking that one.

Revision history for this message
In , jan.public (jan.public-redhat-bugs) wrote :

Maybe this is related to bug 2027035 - Monitor(s) do not always wake up after suspend or blank screen.

Changed in mutter (Fedora):
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , bcotton (bcotton-redhat-bugs) wrote :

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

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

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Changed in mutter:
status: Unknown → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in mutter (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
John Avery (jkavery) wrote :

I still see the problem in Ubuntu 22.04.2.

A year and a half ago I gave up hope of ever seeing the problem fixed and wrote the All Windows + Save/Restore Window Positions Gnome extension that successfully works around it.

Changed in mutter (Ubuntu):
status: Won't Fix → Confirmed
tags: added: jammy
removed: bionic
Revision history for this message
elPraga (elpraga) wrote :

Thank you @jkavery for the extension! This is not a serious bug, but it is very annoying!

Thank you!

Revision history for this message
Deyan Petrov (deyanp) wrote :

Thanks a lot, @jkavery, such a relief after **years**(!!!) of messed up windows after resume!

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That's cool, but please also consider contributing a permanent fix to mutter so we don't need extensions.

Revision history for this message
John Avery (jkavery) wrote :

Thank you for the positive comments! I do not have the knowledge or time to fix the problem. Writing a Gnome extension was new to me as well, but not difficult. After seeing zero evidence of progress on the bug over many years, I had given up hope that it would get fixed.

I hope that the existence of the Gnome extension does not delay a real fix. I suspect that it won't because I'm guessing the eventual fix will be the side-effect of some other change.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.