Bug 2103901 - windows placement bug in gnome 42
Summary: windows placement bug in gnome 42
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 36
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-05 08:36 UTC by Rouquier Philippe
Modified: 2023-05-25 16:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 16:23:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot of the result (191.10 KB, image/png)
2022-07-05 08:36 UTC, Rouquier Philippe
no flags Details

Description Rouquier Philippe 2022-07-05 08:36:49 UTC
Created attachment 1894629 [details]
Screenshot of the result

Description of problem:

For reasons I can't pinpoint, sometimes, seemingly at random, some windows, which were maximised, lose their placement and maximised state. A part of them is usually out of the screen and under the gnome top bar (see attachment) and sometimes they are almost out of reach.
The windows seem to "remember" that they were maximised because if I press "super" and click on them they are maximised again and regain their original placement (or if I move them in a different work space, in the gnome overview, they are immediately maximised).


How reproducible / Steps to Reproduce:
As I said I can't pinpoint what triggers this bug, but when it happens it seems to happen when the energy saver kicks in to turn off the screen or put the computer to sleep. I had once the impression that it can also happen when I open the gnome overview.

Actual results:
See the attachment in which gnome builder, which still has the focus, was maximised then was moved left partially out of the screen.

Expected results:
The windows should remain maximised.

Additional info:
To make sure it was not linked to my settings, I tried with a fresh user and that happened again.
There is apparently nothing in journaltcl (as far as I can tell), except that strange message (mostly related to firefox but also with liferea and a couple of others) :
Unsupported modifier, resource creation failed.
XXX: resource creation failed

BUT the bug never seems to happen with firefox but rather with applications such as evolution, gnome-builder, terminal for example.

Last, it started when I moved to fedora 36.

I chose mutter as the culprit but I could be wrong.

If you want more information, let me know.
Thanks

Comment 1 Ben Cotton 2023-04-25 17:33:18 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 2 Ludek Smid 2023-05-25 16:23:36 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active 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.