When using "Rectangular Region", guidelines for the area, if any, are not visible. So I have no idea exactly what area will be grabbed. And I have no apparent ability to adjust the initial area before taking the screenshot. The screen seems to dim, but I have no idea what that means.
Could you share picture of the issue? Normally, there should be a blue border around the area and rounded drag handles like this (ignore the magnifier on the right): https://phabricator.kde.org/file/data/npflmjckjtckfvmcljnf/PHID-FILE-hscwob7if7c5mckykwfj/ Also, please let us know what graphics driver your system is using.
No answer, closing as WORKSFORME. Perhaps the rectangle was not drawn yet by click-dragging.
There is no border. The screen does seem to subtly change tint. I'm now sure how to get a screenshot before the actual screenshot. ;) When I select "Take a New Screenshot", a dialog box appears center-screen "Click anywhere...". (In fact, I tried to take a screenshot then, but the app locked up the desktop, and I had to switch to another console to kill it.) At that point a cross cursor appears, followed a few seconds later with the screen seeming to dim a bit. I and click-drag the cursor to create a rectangle, although the borders for it never appear. Hitting <Enter> takes the shot. After which the app reappears showing a preview, which I can save.
> how to get a screenshot before the actual screenshot. You could use a camera or test in a VM. > I tried to take a screenshot then, but the app locked up the desktop Please open a separate bug for this issue. > Also, please let us know what graphics driver your system is using. Ping.
Created attachment 113139 [details] Photo of app waiting to execute screenshot. Here is a photograph of the app waiting for me to hit <Enter> to take the shot. The cursor is apparently on the lower right corner of the (invisible) border of the region.
Thanks for the image, I can now see what you mean. > Also, please let us know what graphics driver your system is using. Could you provide this information, e.g. by running "sudo lspci -k | grep -EA3 'VGA|3D|Display'" or by looking into KInfoCenter (Graphical Information → OpenGL)? In addition, your version of Qt would be good to know (Spectacle's Help button → About Spectacle → Libraries).
If you can provide the information requested in comment #6, please add it.
On 06/20/2018 06:15 PM, Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=394499 > > --- Comment #7 from Christoph Feck <cfeck@kde.org> --- > If you can provide the information requested in comment #6, please add it. [root@proteus ~]# lspci -k | grep -EA3 'VGA|3D|Display' 02:00.0 VGA compatible controller: NVIDIA Corporation G94 [GeForce 9600 GT] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 1270 Kernel driver in use: nouveau Kernel modules: nouveau Spectacle Libraries: KDE Frameworks 5.47.0 Qt 5.10.1 (built against 5.10.1) The xcb windowing system
Thanks for the update. I'm reopening this for now because we don't know yet where the real issue is. Nevertheless, I doubt we are doing anything wrong from Spectacle's side, since it's working fine on a bunch of different hardware. This seems like a problem with Qt, Mesa or Nouveau. You could also try to boot another recent distro (e.g. openSUSE Leap 15) from a USB thumb drive, to see whether it works there with a particular kernel version or graphics stack (your Qt and KF5 seem recent enough). It might also be worth asking Qt or the Nouveau developers for advice. Finally, more reports from people using similar hardware are appreciated. BTW, there is currently work underway to port the rectangular region selector to a different backend (see https://phabricator.kde.org/D12626), which might avoid the issue.
*** Bug 376516 has been marked as a duplicate of this bug. ***
Rafael: It would be great if you could add details for your hardware. David: Does disabling KWin's compositing by pressing Alt + Shift + F12 before taking a screenshot fix the issue for you? This might be a workaround for you, and a confirmation for us that indeed this is a graphics problem.
If you can provide the information requested in comment #11, please add it.
To further investigate this issue, KDE developers need the information requested in comment #11. If you can provide it, or need help with finding that information, please add a comment.
If you can, please provide the info requested. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!