Bug 458127 - Multi-monitor setup. Different resolutions. At random times Apps in main screen can only maximize to 2/3 of the screen. Energy saving not working.
Summary: Multi-monitor setup. Different resolutions. At random times Apps in main scre...
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.25.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-21 06:34 UTC by Myrmidom
Modified: 2022-10-02 04:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screenshot (89.21 KB, image/jpeg)
2022-08-21 06:34 UTC, Myrmidom
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Myrmidom 2022-08-21 06:34:19 UTC
Created attachment 151469 [details]
screenshot

SUMMARY

I have a two monitor setup:
Main (right) 1440p 165 Hz running at 165 Hz.
Secondary (left) 1080p 144 Hz running at 144 Hz.

The problem is that, at random times, sometimes after exiting a full screen app, sometimes after the logon screen... The windows on the right screen will maximize to cover the lower 3/4 of the screen. The width remains normal, mouse movement and wallpaper are unaffected and so are full screen applications. Trying to move a window to the empty area causes it to maximize.

Behavior traced to Kscreen 2

STEPS TO REPRODUCE
Happens at random after system changes the screen by : App going full screen. System going into Log on screen. System Start.

OBSERVED RESULT
Windows maximize to 2/3 of the screen.

EXPECTED RESULT
Windows should maximize to the total screen area.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version:  5.25.4
KDE Frameworks Version:  5.97.0
Qt Version:  5.15.5

ADDITIONAL INFORMATION
Garuda O.S.
Bug observed in conjunction with the already reported automatic screen shutdown for energy saving Bug: Automatic screen shutdown doesn't work and instead sends all my windows to the left screen, remaining both on. 
Disabling Kscreen 2 prevents both Bugs from happening.
Comment 1 Nate Graham 2022-08-23 12:54:34 UTC
Are you using the X11 session or the Wayland session?
Comment 2 Myrmidom 2022-08-23 14:02:26 UTC
(In reply to Nate Graham from comment #1)
> Are you using the X11 session or the Wayland session?

X11
Comment 3 Nate Graham 2022-08-25 07:11:21 UTC
Can you try the Wayland session and see if it works there for you?
Comment 4 Myrmidom 2022-08-31 10:35:42 UTC
(In reply to Nate Graham from comment #3)
> Can you try the Wayland session and see if it works there for you?

Tried Wayland. Turning off the screen for Energy saving works but, not only migrates all windows to the left monitor, it also crashes some apps or the system itself. In addition to that, Wayland brought some other new glitches that made me return to X11. 

I didn't see the maximization bug happening, but given the randomness of its occurrence and that I could only stay in Wayland for 24 hours before returning to X11, I wouldn't assume that it does or not occur in Wayland.
Comment 5 Nate Graham 2022-09-01 13:09:43 UTC
Thanks.

I think there is a very high chance that this issue will have been fixed by work that just want in yesterday for Plasma 5.26: https://invent.kde.org/plasma/kwin/-/merge_requests/2573.

Can you test again once Plasma 5.26 is released, or using Neon Unstable?
Comment 6 Myrmidom 2022-09-01 15:33:37 UTC
(In reply to Nate Graham from comment #5)
> Thanks.
> 
> I think there is a very high chance that this issue will have been fixed by
> work that just want in yesterday for Plasma 5.26:
> https://invent.kde.org/plasma/kwin/-/merge_requests/2573.
> 
> Can you test again once Plasma 5.26 is released, or using Neon Unstable?

I will try when Plasma 5.26 is released and update with my findings.
Thanks.
Comment 7 Bug Janitor Service 2022-09-17 04:35:57 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2022-10-02 04:49:07 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!