Created attachment 175904 [details]
this is the status of the system monitor when you just open it before you try to do any setting

Created attachment 175905 [details]
these are the identify of the 3 display

Comment on attachment 175905 [details]
these are the identify of the 3 display

please delete this

Created attachment 175908 [details]
3 display identification

(In reply to matteofavaro+kde.org from comment #0)
> Created attachment 175903 [details]
> when deselecting the "mirror" state this is what appears
> 
> ***
> If you're not sure this is actually a bug, instead post about it at
> https://discuss.kde.org
> 
> If you're reporting a crash, attach a backtrace with debug symbols; see
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports
> 
> Please remove this comment after reading and before submitting - thanks!
> ***
> 
> SUMMARY
> I have a setup using thunderbolt dock. i always use the monitor of the
> laptop in addition
> there are two external displays attached to the dock via DP to the dock
> 
> Laptop is a tuxedo stellaris with intel + nvidia configuration
> 
> STEPS TO REPRODUCE
> 1.  start up the laptop, use wayland
> 2. connect the thunderbolt connector 
> 3. wait
> 4. open system-settings and go to arrange display
> 
> OBSERVED RESULT
> In non zero occasion the system-monitor when in wayland shows that one of
> the monitor is set to "mirror" the built in display.
> Even the system is set up and working with the 3 monitors set side by side
> to each other.
> There is no way to fix this, if you unselect the "mirror of" drop down and
> set it to none, the name of the display appears
> but no drag-able "rectangle" that allows you to setup the arrangement, so a
> red warning appear that there are gaps between displays, but there is no way
> that you can fix that.
> 
> 
> especially when i move from home to work and viceversa where the setup is
> similar but with different display at different resolution the thing become
> even more annoying because display got set up with an overlap and the
> internal display shows part of the external display.
> there a couple of works around i found:
> - go back to X11 set up the displays, reboot a couple of times and then the
> display got configured correctly but the system-settings still believe that
> it is in mirror state.
> - to disable the nvidia card, so one display is active. setup in wayland the
> display, save, reboot, re-enable the nvidia graphic card, DON't OPEN system
> settings, reboot, hope for the best, 1 out 5 works and i got the monitor in
> a "extendend" situation
> 
> EXPECTED RESULT
> 
> the state of the display-setting shown is align with reality. 
> 
> 
> SOFTWARE/OS VERSIONS
> Operating System: Fedora Linux 41
> KDE Plasma Version: 6.2.3
> KDE Frameworks Version: 6.8.0
> Qt Version: 6.8.0
> Kernel Version: 6.11.7-300.fc41.x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 32 × Intel® Core™ i9-14900HX
> Memory: 62.5 GiB of RAM
> Graphics Processor: Mesa Intel® Graphics
> 
> 
> ADDITIONAL INFORMATION

Today i tried again and i can add more details on how to reproduce it.

1) starting with he setup with 3 monitors (2 external + laptop) disconnect and put the laptop into sleep
2) go to a station a try a bunch of configuration with a single external monitor, everyting works
3) put the laptop to sleep
4) reconnect the configuration with the 3 monitor while the laptop is asleep and boot up
5) now 1 external monitor is mirroring the laptop monitor and there is nothing you can do for fixing it via the settings. The bug i reported manifest and you cannot deselect the mirror state. 

work around:
1) dont' touch anything in the setting
2) disconnect the cable and monitors
3) reboot with the monitor disconnected
4) log in and only when plasma is loaded connect the monitors
5) the old configuration is back with the 3 monitor set up as it was at beginning

(In reply to matteofavaro+kde.org from comment #5)
> (In reply to matteofavaro+kde.org from comment #0)
> > Created attachment 175903 [details]
> > when deselecting the "mirror" state this is what appears
> > 
> > ***
> > If you're not sure this is actually a bug, instead post about it at
> > https://discuss.kde.org
> > 
> > If you're reporting a crash, attach a backtrace with debug symbols; see
> > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> > How_to_create_useful_crash_reports
> > 
> > Please remove this comment after reading and before submitting - thanks!
> > ***
> > 
> > SUMMARY
> > I have a setup using thunderbolt dock. i always use the monitor of the
> > laptop in addition
> > there are two external displays attached to the dock via DP to the dock
> > 
> > Laptop is a tuxedo stellaris with intel + nvidia configuration
> > 
> > STEPS TO REPRODUCE
> > 1.  start up the laptop, use wayland
> > 2. connect the thunderbolt connector 
> > 3. wait
> > 4. open system-settings and go to arrange display
> > 
> > OBSERVED RESULT
> > In non zero occasion the system-monitor when in wayland shows that one of
> > the monitor is set to "mirror" the built in display.
> > Even the system is set up and working with the 3 monitors set side by side
> > to each other.
> > There is no way to fix this, if you unselect the "mirror of" drop down and
> > set it to none, the name of the display appears
> > but no drag-able "rectangle" that allows you to setup the arrangement, so a
> > red warning appear that there are gaps between displays, but there is no way
> > that you can fix that.
> > 
> > 
> > especially when i move from home to work and viceversa where the setup is
> > similar but with different display at different resolution the thing become
> > even more annoying because display got set up with an overlap and the
> > internal display shows part of the external display.
> > there a couple of works around i found:
> > - go back to X11 set up the displays, reboot a couple of times and then the
> > display got configured correctly but the system-settings still believe that
> > it is in mirror state.
> > - to disable the nvidia card, so one display is active. setup in wayland the
> > display, save, reboot, re-enable the nvidia graphic card, DON't OPEN system
> > settings, reboot, hope for the best, 1 out 5 works and i got the monitor in
> > a "extendend" situation
> > 
> > EXPECTED RESULT
> > 
> > the state of the display-setting shown is align with reality. 
> > 
> > 
> > SOFTWARE/OS VERSIONS
> > Operating System: Fedora Linux 41
> > KDE Plasma Version: 6.2.3
> > KDE Frameworks Version: 6.8.0
> > Qt Version: 6.8.0
> > Kernel Version: 6.11.7-300.fc41.x86_64 (64-bit)
> > Graphics Platform: Wayland
> > Processors: 32 × Intel® Core™ i9-14900HX
> > Memory: 62.5 GiB of RAM
> > Graphics Processor: Mesa Intel® Graphics
> > 
> > 
> > ADDITIONAL INFORMATION
> 
> Today i tried again and i can add more details on how to reproduce it.
> 
> 1) starting with he setup with 3 monitors (2 external + laptop) disconnect
> and put the laptop into sleep
> 2) go to a station a try a bunch of configuration with a single external
> monitor, everyting works
> 3) put the laptop to sleep
> 4) reconnect the configuration with the 3 monitor while the laptop is asleep
> and boot up
> 5) now 1 external monitor is mirroring the laptop monitor and there is
> nothing you can do for fixing it via the settings. The bug i reported
> manifest and you cannot deselect the mirror state. 
> 
> work around:
> 1) dont' touch anything in the setting
> 2) disconnect the cable and monitors
> 3) reboot with the monitor disconnected
> 4) log in and only when plasma is loaded connect the monitors
> 5) the old configuration is back with the 3 monitor set up as it was at
> beginning

I forgot to mention, still the settings are showing a wrong configuration (mirror), and it is not possible to fix it, but at least the monitors are in the "extend" mode and in the right position.

I've seen similar behavior to what you have reported in the past. I'm not currently able to reproduce this with the same screen setup in Plasma 6.2.5. Are you still able to reproduce this bug?

(In reply to TraceyC from comment #7)
> I've seen similar behavior to what you have reported in the past. I'm not
> currently able to reproduce this with the same screen setup in Plasma 6.2.5.
> Are you still able to reproduce this bug?

Hi thanks a lot for looking into it.
The bug it is still present and it is manifesting in front of me right now :)
in the last few days i haven't changed the hardware setup 
i am using:
 - same thunderbolt docking station with 2 display attached to it
- lid of the laptop open 

the configuration that is working is correct: 3 monitors that works as one
but the setting showed are completely wrong.

i will try to record a screen recording in addition to the current screenshot
https://www.dropbox.com/scl/fi/cmra6bw86mpc4pxspg34w/Kde-Bug.mkv?rlkey=om85pipdfkzkts3k176wrtw38&st=q42nw3vi&dl=0

https://www.dropbox.com/scl/fi/ravcoxy2qcp9aomfus8ng/Bug-kde-better-res.mkv?rlkey=b5hfkcsvovm8gymoup1xzdt06&st=5gsszwcm&dl=0

The screen shot is too big to upload this is the file :) 

https://www.dropbox.com/scl/fi/3tvnr6nf0u1uuapn8y4w3/Bug-KDE-Screenshot_20250205_162724.png?rlkey=0wb4yko8feo3rrshwd4mtfsp7&st=d8rqb2vf&dl=0

Thanks for providing the screen recordings. That makes it very clear what's happening visually.

Can you attach kwin logs too please? (when kscreen fails to disable screen duplication)
See https://community.kde.org/KWin/Debugging#Getting_debug_log_output

Also, it would be great if you could capture drm log output.
https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues

Hi, i am trying to get the logs as requested, but i am finding a problem.

the instructions in the page you suggested they said to type two commands but they are not exactly working

```
matteo@fedora:~$ cat ~/.local/share/sddm/wayland-session.log
cat: /home/matteo/.local/share/sddm/wayland-session.log: No such file or directory
matteo@fedora:~$ 

```
i have found that there is some result for waylang in `journalctl` but i am not sure how to enable the debug
`journalctl -b | grep -i 'wayland.*]: '` produces the following output
```
Feb 07 12:03:33 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 12:03:33 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 12:03:33 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 12:08:24 fedora kwin_wayland[3013]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Feb 07 12:08:49 fedora kwin_wayland[3013]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Feb 07 12:09:06 fedora kwin_wayland[3013]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Feb 07 12:09:09 fedora kwin_wayland[3013]: kwin_wayland_drm: atomic commit failed: Invalid argument
Feb 07 13:13:40 fedora kwin_wayland[3013]: kwin_libinput: Libinput: event5  - UNIW0001:00 093A:0255 Touchpad: kernel bug: clickpad advertising right button. See https://wayland.freedesktop.org/libinput/doc/1.27.1/clickpad-with-right-button.html for details
Feb 07 13:14:17 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Feb 07 13:14:17 fedora kwin_wayland[3013]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Feb 07 13:14:17 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Feb 07 13:14:17 fedora kwin_wayland[3013]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Feb 07 13:14:17 fedora kwin_wayland[3013]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
Feb 07 13:14:17 fedora kwin_wayland[3013]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
Feb 07 13:14:17 fedora kwin_wayland[3013]: kwin_wayland_drm: atomic commit failed: Invalid argument
Feb 07 13:14:29 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Feb 07 13:14:29 fedora kwin_wayland[3013]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Feb 07 13:14:29 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Feb 07 13:14:29 fedora kwin_wayland[3013]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Feb 07 13:14:29 fedora kwin_wayland[3013]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
Feb 07 13:14:29 fedora kwin_wayland[3013]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
Feb 07 13:15:16 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:15:16 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:15:16 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:15:16 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:15:16 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:15:16 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:15:16 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:15:16 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:15:40 fedora kwin_wayland[3013]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Feb 07 13:16:09 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:16:09 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:16:09 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:16:09 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:16:09 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:21:52 fedora kwin_wayland[3013]: kwin_wayland_drm: atomic commit failed: Invalid argument
Feb 07 13:27:08 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:27:08 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:27:08 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:27:08 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:27:08 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:27:08 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:27:08 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:27:08 fedora kwin_wayland[3013]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 07 13:27:41 fedora kwin_wayland[3013]: kwin_libinput: Libinput: event27 - Logitech Wireless Mouse MX Master 2S: client bug: event processing lagging behind by 26ms, your system is too slow
Feb 07 13:34:57 fedora kwin_wayland[3013]: kwin_wayland_drm: atomic commit failed: Invalid argument
matteo@fedora:~$ 

```

but i am not sure that is related to logs thaty ou asked me to produce... i am using fedora 41 is there something else i can try?

the other request instead was more straight forward i attach the file

the file is too big, i attach the file as the others 
https://www.dropbox.com/scl/fi/xyast79rwu7jnpzxdi9nb/drm-debug.log?rlkey=6p9jc53nsp36t4dracx2hslkx&st=ouff176n&dl=0

Thanks for the logs. That will help us investigate.