Bug 1815492 - After unlocking screen, windows moved and audio output changed
Summary: After unlocking screen, windows moved and audio output changed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-session
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-20 12:34 UTC by meltingrobot
Modified: 2022-06-08 00:48 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-08 00:48:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description meltingrobot 2020-03-20 12:34:20 UTC
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:

Comment 1 meltingrobot 2020-04-01 15:39:05 UTC
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.

Comment 2 Jan Vlug 2020-09-12 13:47:27 UTC
See also: bug 1878367.

Comment 3 meltingrobot 2020-09-12 14:03:40 UTC
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.

Comment 4 Jan Vlug 2020-09-12 15:58:59 UTC
See also: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419

Comment 5 Ben Cotton 2020-11-03 16:30:55 UTC
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.

Comment 6 meltingrobot 2020-11-03 19:18:49 UTC
Bug still exists in 33, was also in 32

Comment 7 meltingrobot 2021-05-24 11:26:25 UTC
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)

Comment 8 Henri Hyyryläinen 2021-07-26 12:36:44 UTC
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.

Comment 9 Jan Vlug 2022-01-17 08:34:54 UTC
Maybe this is related to bug 2027035 - Monitor(s) do not always wake up after suspend or blank screen.

Comment 10 Ben Cotton 2022-05-12 16:31:13 UTC
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.

Comment 11 Ben Cotton 2022-06-08 00:48:45 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

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


Note You need to log in before you can comment on or make changes to this bug.