Bug 481222

Summary: Support proper output mirroring
Product: [Plasma] kwin Reporter: Iyán Méndez Veiga <me>
Component: platform-drmAssignee: KWin default assignee <kwin-bugs-null>
Status: CONFIRMED ---    
Severity: wishlist CC: bridgesensemc, fanzhuyifan, kevin.kofler, kishore96, leon.halic, mira.jary, mokazemi, mydj555, nate, ngompa13, postix, rafael.palma.lima, serzavevich13, tobiaspotocek, tomblackwhite, xaver.hugl
Priority: HI Keywords: qt6
Version: 5.93.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Iyán Méndez Veiga 2024-02-11 13:18:05 UTC
SUMMARY
First of all, a big THANK YOU for all the hard work and improvements around the multi-screen support. Plasma 5.x always felt a bit unreliable when connecting external screens. The RC 2 already feels much much better. Specially the "unify output" mode, which was quite broken in Plasma 5.x in my opinion.

After playing around with different setups, I only notice one small bug. My laptop has a 16:10 screen. When I connect at 16:9 external monitor and I change to "unify outputs" mode, the resolutions (correctly!) changes to a 16:9 one. There are some black bands in the built-in laptop screen (as it should!) and the external screen shows exactly the same as the laptop without any artifacts as it happens with Plasma 5.27.10.

However, when detaching the external monitor, the 16:9 resolution is kept instead of restoring the native 16:10 one.


STEPS TO REPRODUCE
1. Select native 16:10 resolution on a laptop (in my case 1920x1200)
2. Attach an external 16:9 monitor (in my case I tried with a 1920x1080 one)
3. Switch to "unify outputs" mode
4. Detach external screen

OBSERVED RESULT
Laptop keeps the 1920x1080 (16:9) resolution with black bands on the top and bottom edges

EXPECTED RESULT
Laptop should switch back to its native 16:10 resolution before the "unify outputs" mode was enabled


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: LENOVO
Product Name: 20XYCTO1WW
System Version: ThinkPad X1 Yoga Gen 6
Comment 1 Zamundaaa 2024-02-19 15:58:24 UTC
Yeah, we'll need to properly plumb screen mirroring from KScreen to KWin, and handle this properly in KWin
Comment 2 Zamundaaa 2024-02-20 22:26:22 UTC
*** Bug 481584 has been marked as a duplicate of this bug. ***
Comment 3 Zamundaaa 2024-03-13 16:07:15 UTC
*** Bug 483437 has been marked as a duplicate of this bug. ***
Comment 4 Zamundaaa 2024-06-05 09:55:27 UTC
*** Bug 487796 has been marked as a duplicate of this bug. ***
Comment 5 Zamundaaa 2024-06-06 14:44:41 UTC
*** Bug 488111 has been marked as a duplicate of this bug. ***
Comment 6 Zamundaaa 2024-09-19 14:23:38 UTC
*** Bug 491144 has been marked as a duplicate of this bug. ***
Comment 7 Nate Graham 2024-09-19 16:01:39 UTC
*** Bug 492827 has been marked as a duplicate of this bug. ***
Comment 8 Miroslav Jarý 2024-09-22 09:07:10 UTC
Hey there!
Any news on when this can be expected?
Comment 9 Zamundaaa 2024-09-22 22:22:03 UTC
I plan to tackle this for the Plasma 6.3 release. No promises on completeness by then though, some parts of doing things properly require quite a lot of changes in KWin.
Comment 10 Nate Graham 2024-09-23 17:57:06 UTC
*** Bug 493478 has been marked as a duplicate of this bug. ***
Comment 11 Iyán Méndez Veiga 2024-09-23 18:23:19 UTC
Many bugs marked as duplicated of this one seem to be quite different to what I'm describing here.
Comment 12 Nate Graham 2024-09-23 18:36:16 UTC
I'll leave that for Xaver to explain, but as I understand it, they all have the same root cause.
Comment 13 Iyán Méndez Veiga 2024-09-23 18:39:59 UTC
No need to waste time explaining to me here. If it was not by mistake and the root cause is clear to Xaver, all good :) I was just confused by some of the other bugs. The bug I tried to describe here was a very minor issue, but others seem more severe and annoying.
Comment 14 Zamundaaa 2024-10-01 12:07:54 UTC
*** Bug 493913 has been marked as a duplicate of this bug. ***
Comment 15 Nate Graham 2024-10-11 19:13:13 UTC
*** Bug 494447 has been marked as a duplicate of this bug. ***
Comment 16 Nate Graham 2024-10-22 17:24:04 UTC
*** Bug 493811 has been marked as a duplicate of this bug. ***