https://bugs.kde.org/show_bug.cgi?id=375990
Nate Graham changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=375990
--- Comment #4 from Frederick Zhang ---
No, I cannot reproduce it either. I guess it was fixed somewhere upstream :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375990
Nate Graham changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=375990
--- Comment #2 from Frederick Zhang ---
Please ignore my previous comment. It was just coincidentally not reproduced
when I was using a single screen.
I'm now on 16.12.3, the issue still remains.
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=375990
--- Comment #1 from Frederick Zhang ---
I noticed that this only occurs when I place Spectacle in one monitor and try
to capture a region in the other (I'm using an HDMI external monitor). If I
capture a region in the same monitor as Spectacle, the issu