Created attachment 126408 [details] Not mirrored When I plug in my external screen, the desktop gets extended. However the notification widget sees it as mirrored, and therefore inappropriately enters Do No Disturb mode. I can turn Disturb mode off, but it turns on again every time I disconnect and re-connect the external display.
Please provide the output of kscreen-doctor -j with screens in this configuration.
Created attachment 126438 [details] kscreen-doctor -j output
Attached.
So your right screen is at "pos": { "x": 1919, "y": 0 }, which overlaps by 1 pixel. How did you set the screen position? Through the OSD or by manually dragging? I probably should make the check more lenient (e.g. only if the screens overlap by 10 pixels or so) but I would like to know the cause first
I didn't manually set anything; I just plugged it in and it automatically appeared to the right of my current screen. Could the check see if the geometry of both screens is 100% overlapping, rather than having any overlapping?
You sure it didn't restore a previous config of sorts? Then it's probably a KScreen bug. 100% wouldn't work as you can have different sized screens overlapping, e.g. a projector only showing a section of your main screen.
How can I check to see if it restored a previous config? Regardless, yeah I guess it would be nice to build in a bit of wiggle room for the overlap calculation.
I'm also seeing this and had a 1px overlap. I noticed the DnD mode after I disabled one of the screens in kscreen for a screen sharing session and then enabled it again. I have tried to reproduce: * if I disable the screen, apply, enable screen and apply I don't get the 1px overlap, but * if I close kscreen after disabling, when I open it again and enable the screen, the 1px overlap is there.
I also have the 1px overlap. But > disable the screen, apply, enable screen and apply did not help :/ Is there already a bug for kscreen filed?
Indeed: Bug 432873. Marking as a duplicate. *** This bug has been marked as a duplicate of bug 432873 ***
*** This bug has been marked as a duplicate of bug 460247 ***