Bug 445451 - some screen geometry detection critically buggy
Summary: some screen geometry detection critically buggy
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.23.0
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-14 01:18 UTC by David Chmelik
Modified: 2022-07-03 01:51 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Chmelik 2021-11-14 01:18:48 UTC
SUMMARY
Sometimes when I open, for example, dolphin, from the upper screen menu, but it opens on my lower screen, I move it to my upper screen, but unless I keep it partially past the left or right edge (though I don't think it should be possible to go past the edge) it will jump back down to the lower screen.  If I want it on the upper screen I'm forced to maximize it (which I normally wan to anyway but prefer to do after fitting it into the screen manually, which if I try to do, it jumps back down.)

STEPS TO REPRODUCE
1. Open a program intended for the upper screen, but might open on a lower screen.
2. Try to size it to the upper screen.
3. See it jump back down.

OBSERVED RESULT
Depending how you move a program from the lower to upper screen and start moving/sizing it there, it may jump back down to the lower screen, because some of the geometry calculations are off.

EXPECTED RESULT
Once you have a program on the upper screen, don't force it back down onto the lower one just from moving/sizing it without going below the upper one.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Slackware64-current / 5.23.2
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
I wish I could make a video for you but don't think I'm going to be able to. Let me know if I need to describe more.
Comment 1 David Chmelik 2021-11-14 01:55:59 UTC
My top screen is 1600x1200--I hope you still take such case (4:3 shape screens including some resolutions lower than this) into consideration.
Comment 2 Nate Graham 2021-11-23 18:53:04 UTC
X11 or Wayland? If X11, does it work better on Wayland?
Comment 3 David Chmelik 2021-11-28 00:36:20 UTC
X11. I'm unsure I'm going to try Wayland...
Comment 4 Nate Graham 2021-11-29 20:17:16 UTC
Why not?
Comment 5 Bug Janitor Service 2021-12-14 04:35:13 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 6 David Chmelik 2021-12-14 07:40:24 UTC
Wayland is experimental, even if I heard it doesn't crash as much as used to (but crashes can be worse, requiring restarts, not always case with X) and seems not as good as X as Wayland does much less, and KDE's main page on Wayland has a long bug list with some serious bugs... one minor movement bug that has a solution isn't as bad as that long list of bugs, as this geometry detection bug hasn't happened since. Something must've triggered it, either me disabling & reenabling a display, or too much graphics resources were being used (not likely the case again), then either way KDE maybe automatically reconfigured & moved my screens, then something went wrong with that geometry. Those things won't always even do it, and perhaps I had the PC on for several days/weeks and a restart of KDE or reboot of Slackware (also if I had updated KDE) would've solved the geometry thing. I still use and like several X programs. I'm not sure all my hardware works on Wayland, but I know they're working on it. Using Wayland is completely out of the question unless it ever becomes a default/only option.

In the future I'll reinstall one or more desktop session video recorders and in the rare chance the bug might happen again, see if I'm able to capture it.  I don't care if you close it for now because I haven't been able to record it.
Comment 7 Bug Janitor Service 2021-12-29 04:34: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-01-13 04:37:12 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!
Comment 9 David Chmelik 2022-07-03 01:51:51 UTC
It never worked for me, but apparently isn't a KDE bug, but a X bug of whatever (Xinerama?) controls multi-monitor management for any window manager (WM) or desktop environment (DE) as I had same problem when using XFCE.