Bug 525036 - Centered window placement is not always correct if no applications are open and then one is launched
Summary: Centered window placement is not always correct if no applications are open a...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.7.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 525412 (view as bug list)
Depends on:
Blocks:
 
Reported: 2026-08-31 07:40 UTC by Aaron
Modified: 2026-09-09 18:53 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 6.8.0
Sentry Crash Report:


Attachments
Example of where Konsole opens, despite the window placement being set to "Centered" (2.55 MB, image/png)
2026-08-31 07:40 UTC, Aaron
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron 2026-08-31 07:40:29 UTC
Created attachment 195636 [details]
Example of where Konsole opens, despite the window placement being set to "Centered"

DESCRIPTION
When the system is set to Window placement as centered, seemingly random apps don't respect it. This includes Konsole, a first party KDE app. This is not a result of apps setting their own window placement, as they will respect if I set it to "Under mouse", "maximized", "upper left corner", etc. Centered seems to offset, with the top left corner of the app seemingly always ending up in the same spot. 

If there is another window spawned, or a fullscreen window present, the same apps will open normally in their centered position. The screen has to be cleared of all other windows. 


STEPS TO REPRODUCE
1. Ensure that window placement is set to "Centered" in Settings > Window Behavior > Advanced
2. Ensure you have no specific window rule overrides for Konsole.
3. Close or minimize all windows on the desktop
4. Open Konsole

OBSERVED RESULT
The app opens down and to the right of the center of the screen 

EXPECTED RESULT
The app should open dead center in the middle of the screen, as it has historically. 

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44 (KDE Plasma Desktop Edition)
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.29.0
Qt Version: 6.11.1

ADDITIONAL INFORMATION
I have tested this across 3 separate machines, all running Fedora 44. There is a variety of Nvidia, AMD, and Intel GPUs, and all are fully up to date as of writing this report. 

Most apps are unaffected by this. Konsole is the only KDE system app that I could find that is affected. It also seems to not matter if an app is a Flatpak or a system package. I had this happen with Konsole (system), Haruna (system), Help Center (system), ProtonPlus (flatpak), and An-Anime-Game-Launcher (flatpak)

Attempts to force an application specific window rule override to "centered" also does not work.
Comment 1 Akseli Lahtinen 2026-08-31 08:23:01 UTC
I'm unable to repro this, though windows sometimes try to avoid completely overlapping each other. I have no idea why Konsole in your example has decided to do so.

Did you have any windows open in other virtual desktop, monitor or such?

Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.1
Kernel Version: 7.1.10-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 6600
Comment 2 Aaron 2026-08-31 09:11:16 UTC
(In reply to Akseli Lahtinen from comment #1)
> I'm unable to repro this, though windows sometimes try to avoid completely
> overlapping each other. I have no idea why Konsole in your example has
> decided to do so.
> 
> Did you have any windows open in other virtual desktop, monitor or such?
> 
> Operating System: Fedora Linux 44
> KDE Plasma Version: 6.7.4
> KDE Frameworks Version: 6.30.0
> Qt Version: 6.11.1
> Kernel Version: 7.1.10-200.fc44.x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
> Memory: 16 GiB of RAM (15.5 GiB usable)
> Graphics Processor: AMD Radeon RX 6600

I have tested this with and without windows open on other monitors. I have also reproduced this on a laptop with no other screens or apps open, on fresh boots. The moment any other window *is* open on the same monitor, the issue goes away. The screen has to be explicitly clear of all windows for this to occur.
Comment 3 Aaron 2026-08-31 09:23:39 UTC
> I have tested this with and without windows open on other monitors. I have
> also reproduced this on a laptop with no other screens or apps open, on
> fresh boots. The moment any other window *is* open on the same monitor, the
> issue goes away. The screen has to be explicitly clear of all windows for
> this to occur.

Here are some more screenshots with examples of the situation, includes windows that are and are not affected. All are native packages besides ProtonPlus, that is a flatpak. 
https://drive.proton.me/urls/RHKVHN5SX0#63UwFIMqmv1k
Comment 4 Aaron 2026-08-31 09:49:26 UTC
Also I think I accidentally set it to FIXED by mistake, Ive changed it back to WAITINGFORINFO, my mistake. Im new to reporting bugs here
Comment 5 TraceyC 2026-09-01 17:30:38 UTC
I found that there's an existing bug about this, so I'll merge this in with the older one. Please follow bug 524018 for updates.

*** This bug has been marked as a duplicate of bug 524018 ***
Comment 6 Aaron 2026-09-01 21:06:44 UTC
(In reply to TraceyC from comment #5)
> I found that there's an existing bug about this, so I'll merge this in with
> the older one. Please follow bug 524018 for updates.
> 
> *** This bug has been marked as a duplicate of bug 524018 ***

Hello, this is not a duplicate of that bug. Reading the behavior of their issue does not match the behavior of my issue. 

They report that it opens centered properly unless there is a fullscreen window

I am reporting that it opens incorrectly **unless** there is another window present already. And that it applies to only some applications.
Comment 7 Aaron 2026-09-01 21:14:11 UTC
I should clarify, I said fullscreen, I meant maximized. Mine has nothing to do with whether a window was maximized and/or restored, this is upon opening a fresh non-maximized window on a desktop cleared of all other windows.
Comment 8 Aaron 2026-09-01 21:17:43 UTC
(In reply to Akseli Lahtinen from comment #1)
> I'm unable to repro this, though windows sometimes try to avoid completely
> overlapping each other. I have no idea why Konsole in your example has
> decided to do so.
> 
> Did you have any windows open in other virtual desktop, monitor or such?
> 
> Operating System: Fedora Linux 44
> KDE Plasma Version: 6.7.4
> KDE Frameworks Version: 6.30.0
> Qt Version: 6.11.1
> Kernel Version: 7.1.10-200.fc44.x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
> Memory: 16 GiB of RAM (15.5 GiB usable)
> Graphics Processor: AMD Radeon RX 6600

Try making your default konsole size smaller, Ive noticed that sometimes if the affected app is beyond a certain size, it will not be affected by this bug. Set konsole to the lowest size default you can and testing. (make sure no other windows are present on screen)
Comment 9 Nate Graham 2026-09-02 00:26:03 UTC
I also can't reproduce the issue as described on KDE Linux.

This can't be a plasmashell issue since plasmashell isn't responsible for window placement; moving to KWin.
Comment 10 Aaron 2026-09-02 09:55:52 UTC
(In reply to Nate Graham from comment #9)
> I also can't reproduce the issue as described on KDE Linux.
> 
> This can't be a plasmashell issue since plasmashell isn't responsible for
> window placement; moving to KWin.

Here is a video of the issue: https://youtu.be/iwmzVoCJbWs

As you can see, the size of the window impacts whether the issue happens, as well as whether a window is present at all on the same display. 

Additionally, this occurs on 3 separate machines of mine in testing, all running the latest Fedora 44 and KDE updates. Only one has multiple monitors, and whether windows are open on other displays/workspaces does not impact the results of this bug. Only if windows are open on the same display.
Comment 11 TraceyC 2026-09-02 20:19:48 UTC
In the video:

1. Open KWrite, it incorrectly opens to the right and below center
2. Close and reopen KWrite. Make the window taller
3. Reopen KWrite, it correctly opens in the center
4. Reopen KWrite, make the window shorter.
5. Reopen KWrite,  it incorrectly opens to the right and below center

Additionally
Making the window bigger from the bottom left corner makes KWrite open right and below center

I'm still not able to reproduce this on Plasma built from git-master, even with no other applications open, or other apps open and minimized
Tested with KWrite and Konsole at smaller and minimal sizes
Comment 12 Aaron 2026-09-03 10:08:26 UTC
(In reply to Aaron from comment #10)
> (In reply to Nate Graham from comment #9)
> > I also can't reproduce the issue as described on KDE Linux.
> > 
> > This can't be a plasmashell issue since plasmashell isn't responsible for
> > window placement; moving to KWin.
> 
> Here is a video of the issue: https://youtu.be/iwmzVoCJbWs
> 
> As you can see, the size of the window impacts whether the issue happens, as
> well as whether a window is present at all on the same display. 
> 
> Additionally, this occurs on 3 separate machines of mine in testing, all
> running the latest Fedora 44 and KDE updates. Only one has multiple
> monitors, and whether windows are open on other displays/workspaces does not
> impact the results of this bug. Only if windows are open on the same display.

I genuinely wish I had a way to help everyone reproduce this. My KDE configuration is pretty stock, I haven't changed much in regards to window behavior, especially on my laptops I never even touched window behavior settings and this still occured. 

I don't know how long the bug has existed, but I noticed it adter updating my system this last Saturday. I update weekly and the only KDE package that was even updated in that time was kde-settings. If needed, I can setup a fedora VM, update it, and see if I can reproduce the issue on a clean installation. I'm out of ideas otherwise
Comment 13 Aaron 2026-09-03 10:48:25 UTC
I cannot immediately get it to happen in a VM, even at the exact same screen resolution and package versions. I will try to apply my usual configs to the system, despite them not being window rules, and see if I run into something that causes it.
Comment 14 Aaron 2026-09-03 11:51:26 UTC
(In reply to Aaron from comment #13)
> I cannot immediately get it to happen in a VM, even at the exact same screen
> resolution and package versions. I will try to apply my usual configs to the
> system, despite them not being window rules, and see if I run into something
> that causes it.
@Nate, TraceyC, and Akseli

Okay, Update! I got it to reproduce reliably! I was even able to capture it happening on video. 

Steps to reproduce:
1. Install Fedora 44 KDE Plasma Edition in a virtual machine, install it with all default settings, then update it. 

2. Reboot the system. 

3. If not already set, set the display resolution to 1920x1080

4. Reboot again (maybe 2-3 times if it doesnt work)

Important notes:
 While I had my display resolution set to 1080p, Im unsure if this will be as easily reproducible on other resolutions. 

 In the linked video below, I started recording on step 3. I had updated and rebooted once. After i set display resolution I simply rebooted and was able to reliable reproduce the issue on two additional fresh VMs. 

Video: https://youtu.be/q3pGn7cjAm0

(VM DETAILS:
KDE Plasma 6.7.4
KDE Frameworks 6.29.0
QT 6.11.2
Kernel 7.1.12-200
8GB RAM
1080P Output resolution
Comment 15 Nate Graham 2026-09-03 23:03:05 UTC
I'm told this should be fixed by https://invent.kde.org/plasma/kwin/-/commit/1073df28fe18b6b69cd791472c6ab154e41c7beb!

Please re-test once Plasma 6.8 is released, or now with git master (wither by compiling it yourself, or in a distro/with packages that ship the git master version of Plasma and KWin).
Comment 16 TraceyC 2026-09-09 18:53:08 UTC
*** Bug 525412 has been marked as a duplicate of this bug. ***