Bug 1893466 - Application Windows Are Always Initially Placed in Same Spot
Summary: Application Windows Are Always Initially Placed in Same Spot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kwin
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Vrátil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-31 19:57 UTC by Garry T. Williams
Modified: 2020-12-17 22:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-17 22:07:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Garry T. Williams 2020-10-31 19:57:05 UTC
Description of problem:
Application windows are started on the screen in the same spot.  If I move the window and then close it, the next time, that application window is placed in the same spot as it was when it was last closed.

I have selected Window Management -> Window Behavior -> Advanced -> Window Placement -> Minimal Overlapping.  Furthermore, I have *always* had that setting.  It just recently stopped working.

I also see that focus is broken in that closing a window fails to change focus to last focused window.  This, too, is new behavior, but I do not know of a setting to adjust it.


Version-Release number of selected component (if applicable):
kwin-5.19.5-4.fc33.x86_64
kf5-kwindowsystem-5.75.0-1.fc33.x86_64


How reproducible:
Always


Steps to Reproduce:
1.  Open new application, say konsole.
2.  Open same application again.
3.

Actual results:
Application windows are on top of each other.


Expected results:
Application windows are not overlapped.


Additional info:

Comment 1 Rex Dieter 2020-10-31 22:08:29 UTC
Can you confirm this is regression with kf5-5.75?  Did this perform properly prior to installing that recent update?

Comment 2 Garry T. Williams 2020-11-09 21:42:27 UTC
Oh, sorry; I missed your comment.

Yes.  A downgrade restored correct placement of windows.  My test is opening two konsole windows, back to back.  Now they open non-overlapped again.

I downgraded everything that matched kf5*5.75, so I cannot tell you who the culprit is.

Comment 3 Garry T. Williams 2020-11-09 21:43:15 UTC
Also, I was wrong about focus being a problem.  It is fine as far as I can see.

Comment 4 Garry T. Williams 2020-11-12 17:54:16 UTC
Let me know, if you want me to selectively upgrade to narrow down or identify the faulty change.  In the mean time, I am updating with --exclude=kf5\* to avoid the annoying bug.

Comment 5 Garry T. Williams 2020-11-23 00:15:38 UTC
I finally could not start KDE after updating with updates-testing and excluding kf5*.

So, I allowed kf5* to get back to a system that would actually boot, starting the desktop.  Now I was back to the very annoying application window placement being broken.  In an effort to narrow down the problem, I did:

* sudo dnf downgrade kf5-kwindowsystem -- no help
* sudo dnf downgrade kf5-plasma -- no help
* sudo dnf downgrade kwin kwin-common kwin-libs kwin-x11 -- disaster -- no desktop again

(It looks like one of kwin, kwin-common, kwin-libs, or kwin-x11 is missing some dependency, because the desktop won't start when I downgrade these.)

So, it looks like the update that was pushed introduced a bug in application window placement.

Comment 6 Garry T. Williams 2020-12-17 22:07:58 UTC
The problem was a setting that was updated: System Settings -> Window Management -> Window Behavior -> Advanced the checkbox for "Allow KDE apps..." was selected.  Unchecking the box restored the original behavior.  Now opening multiple konsole windows doesn't result in all opening in same spot.

So it wasn't ... -> Advanced -> Window Placement -> Minimal Overlapping broken.

I selected notabug, but it really *is* a bug when someone decides to arbitrarily change a setting.  It is unexpected and very unwelcome.  And it seems to happen often with KDE, unfortunately.


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