[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 --- Comment #11 from Nate Graham --- *** This bug has been marked as a duplicate of bug 460247 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #10 from Nate Graham --- Indeed: Bug 432873. Marking as a duplicate. *** This bug has been marked as a duplicate of bug 432873 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 Bernhard Scheirle changed: What|Removed |Added CC||bernhard+...@scheirle.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 gran...@tempmail.de changed: What|Removed |Added CC||gran...@tempmail.de --- Comment #9 from gran...@tempmail.de --- 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? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 Jose M. Prieto changed: What|Removed |Added CC||jmpri...@gmx.net --- Comment #8 from Jose M. Prieto --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 --- Comment #7 from Nate Graham --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 --- Comment #6 from Kai Uwe Broulik --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 --- Comment #5 from Nate Graham --- 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 are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185
--- Comment #4 from Kai Uwe Broulik ---
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
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Nate Graham --- Attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 --- Comment #2 from Nate Graham --- Created attachment 126438 --> https://bugs.kde.org/attachment.cgi?id=126438=edit kscreen-doctor -j output -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Kai Uwe Broulik --- Please provide the output of kscreen-doctor -j with screens in this configuration. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418185] Notification widget incorrectly sees extended display as mirrored and inappropriately enters Do Not Disturb mode
https://bugs.kde.org/show_bug.cgi?id=418185 Nate Graham changed: What|Removed |Added Version|5.18.0 |master Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
