[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-05-21 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=507702

TraceyC  changed:

   What|Removed |Added

Version||6.7.0
  Fixed/Implemented||
 In||

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-05-18 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=507702

Zamundaaa  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/-/commit/999f702e87
   ||f3505756ebcfd09a0bd2e9137a3
   ||431

--- Comment #37 from Zamundaaa  ---
Git commit 999f702e87f3505756ebcfd09a0bd2e9137a3431 by Xaver Hugl.
Committed on 18/05/2026 at 14:42.
Pushed by zamundaaa into branch 'master'.

outputconfigurationstore: guard against invalid output positions

While we already guard against them in the output management protocol
implementation, invalid positions were in some cases saved before that check
was implemented.

M  +7-0src/outputconfigurationstore.cpp

https://invent.kde.org/plasma/kwin/-/commit/999f702e87f3505756ebcfd09a0bd2e9137a3431

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-05-15 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=507702

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #36 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/9212

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-05-15 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=507702

Zamundaaa  changed:

   What|Removed |Added

  Component|multi-screen|output configuration

--- Comment #35 from Zamundaaa  ---
Okay. If it's 'just' saved values, those might be from the time where KScreen
did that in some cases for mirroring. KWin disallows them though, so adding a
guard when loading configs should hopefully be enough to fix this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-05-13 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=507702

TraceyC  changed:

   What|Removed |Added

 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #34 from TraceyC  ---
(In reply to Zamundaaa from comment #31)
> Do you have some reproducible steps to trigger it? When working on
> mirroring, I found a case where KScreen would do this, but I fixed that one.
> 
> If it always happens, is that position maybe just saved in the config from
> when KScreen was still broken in this way? If yes, then we could just add
> some safe guards in KWin against loading such positions.

On my XPS, this always happens.
Right click the desktop -> Display Configuration
Click the second monitor
Click the Enabled checkbox
See error
Also, the preview of the 3rd screen isn't shown

As noted in comment #16, kwinoutputconfig.json has an unusually large value for
x and y for a screen position (max of an int32)

409:"position": {
410-"x": 2147483647,
411-"y": 2147483647
412-

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-05-11 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=507702

--- Comment #33 from Zamundaaa  ---
Wrong EDID information is definitely a problem, but a pretty different one from
this. Ultimately that one is something that has to be fixed in the kernel (the
GPU driver specifically), though ideally we'd still handle it anyways. You can
open a separate bug report for it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-05-01 Thread Willian
https://bugs.kde.org/show_bug.cgi?id=507702

Willian  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #32 from Willian  ---
(In reply to Zamundaaa from comment #31)
> Do you have some reproducible steps to trigger it? When working on
> mirroring, I found a case where KScreen would do this, but I fixed that one.
> 
> If it always happens, is that position maybe just saved in the config from
> when KScreen was still broken in this way? If yes, then we could just add
> some safe guards in KWin against loading such positions.

Hi, can you describe the recent fixed issue? Im experiencing the issue on
Plasma 6.6.4. 

The problem I'm experiencing is that sometimes, when unplugging and plugging
the external display very fast (e.g. power surge on the usb-c dock), the
external display would become inaccessible by the cursor, showing the gap
message in the display settings. 

Some useful information is the following diffs between kscreen-doctor outputs,
in the working and bugged states:

diff kscreen-good.log kscreen-bug.log

<   Modes:  91:[email protected]!  92:[email protected]  93:[email protected] 
94:[email protected]  95:[email protected]  96:[email protected] 
97:[email protected]*  98:[email protected]  99:[email protected] 
100:[email protected]  101:[email protected]  102:[email protected] 
103:[email protected]  104:[email protected]  105:[email protected] 
106:[email protected]  107:[email protected]  108:[email protected]  109:[email protected]
 110:[email protected]  111:[email protected]  112:[email protected] 
113:[email protected]  114:[email protected]  115:[email protected]  116:[email protected] 
117:[email protected]  118:[email protected]  119:[email protected]  120:[email protected] 
121:[email protected]  122:[email protected]  123:[email protected]  124:[email protected] 
125:[email protected]  126:[email protected]  127:[email protected]  128:[email protected] 
129:[email protected]  130:[email protected]  131:[email protected]  132:[email protected] 
133:[email protected]  134:[email protected]  135:[email protected]  136:[email protected] 
137:[email protected]  138:[email protected]  139:[email protected] 
140:[email protected]  141:[email protected]  142:[email protected] 
143:[email protected]  144:[email protected] 
---
>   Modes:  91:[email protected]*!  92:[email protected]  93:[email protected]  
> 94:[email protected]  95:[email protected]  96:[email protected]  97:[email protected] 
>  98:[email protected]  99:[email protected]  100:[email protected]  
> 101:[email protected]  102:[email protected]  103:[email protected]  
> 104:[email protected]  105:[email protected]  106:[email protected]  107:[email protected] 
>  108:[email protected]  109:[email protected]  110:[email protected]  111:[email protected]  
> 112:[email protected]  113:[email protected]  114:[email protected]  115:[email protected]  
> 116:[email protected]  117:[email protected]  118:[email protected]  119:[email protected]  
> 120:[email protected]  121:[email protected]  122:[email protected]  123:[email protected]  
> 124:[email protected]  125:[email protected]  126:[email protected]  127:[email protected]  
> 128:[email protected]  129:[email protected] 
57c57
<   Geometry: 0,0 1707x960
---
>   Geometry: 0,0 1280x720

My understanding is that the external display hardware bugs for an instant and
the wrong edid information is received, making kscreen interpret the display as
having a lower resolution than before ([email protected] vs [email protected]),
which calculates the wrong geometry and thus creates the unwanted gap.

Let me now if it's related and how can I help debugging it. I was ready to
search for the bug on the code before I saw your comment.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-04-30 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=507702

--- Comment #30 from TraceyC  ---
Still affecting Plasma 6.6.4

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-04-30 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=507702

Zamundaaa  changed:

   What|Removed |Added

 CC||[email protected]
 Status|CONFIRMED   |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #31 from Zamundaaa  ---
Do you have some reproducible steps to trigger it? When working on mirroring, I
found a case where KScreen would do this, but I fixed that one.

If it always happens, is that position maybe just saved in the config from when
KScreen was still broken in this way? If yes, then we could just add some safe
guards in KWin against loading such positions.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-03-31 Thread postix
https://bugs.kde.org/show_bug.cgi?id=507702

postix  changed:

   What|Removed |Added

   See Also|https://bugs.kde.org/show_b |
   |ug.cgi?id=502546|

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-03-30 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=507702

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=479952

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-03-02 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=507702

--- Comment #29 from TraceyC  ---
This is still affecting Plasma 6.6.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-03-02 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=507702

TraceyC  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=506777

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-02-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=507702

[email protected] changed:

   What|Removed |Added

 CC|[email protected] |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2026-01-30 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=507702

TraceyC  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=514796

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2025-12-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=507702

Bug Janitor Service  changed:

   What|Removed |Added

   Priority|NOR |HI

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2025-12-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=507702

Nate Graham  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #28 from Nate Graham  ---
*** Bug 510936 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2025-12-09 Thread postix
https://bugs.kde.org/show_bug.cgi?id=507702

--- Comment #27 from postix  ---
(In reply to Nate Graham from comment #25)
> > Geometry: 2147483647,2147483647 1366x768
> Looks suspicious.

Yeah, like I wrote
> fwiw, 2147483647 is the largest number, which fits into an int32.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2025-12-09 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=507702

Nate Graham  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #26 from Nate Graham  ---
*** Bug 502546 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 507702] Error on enabling secondary screen: Gaps between displays are not supported. Make sure all displays are touching.

2025-12-09 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=507702

Nate Graham  changed:

   What|Removed |Added

Product|systemsettings  |kwin
   Assignee|[email protected]   |[email protected]
  Component|kcm_kscreen |multi-screen

-- 
You are receiving this mail because:
You are watching all bug changes.