I did a clean install of Leap on my GF’s laptop. HP Notebook. It appears the Print Screen button doesn’t invoke a screenshot. The button has a double function (with Fn pressed) as Insert. Insert works, so the button isn’t dead.
In the shorcuts window the button is set as Print Screen and you can also re-set it as Print Screen. Yet, it will not make screenshots.
From the command-line I can run gnome-screenshot and it will make screenshots and put them in the ~/Pictures directory.
But this is hard when trying to make a screenshot of full screen apps. I also tried to swap Insert (Fn + Print Scrn) with Print Scrn but then, Insert still works and Print Screen still doesn’t.
Does anyone have an idea as for why the Print Scrn button isn’t working?
No idea why you’re experiencing your problem,
But typically screenshot apps have the ability to specify special keystroke combinations to take snapshots (I don’t know about your Gnome app, but that is the case in KDE).
So, it won’t solve your problem directly, but should provide a satisfactory solution.
I’m having the same problem with my desktop. Print screen button doesn’t do anything. Any idea how to fix this? There has to be some printscreen setting = false or something like that in one of the configuration files, but I don’t have any idea where to look.
To fix it I went to settings -> shortcuts -> custom shortcuts and hit right click, new global shortcut, command. From there I assigned the printscreen button to the ksnapshot command, and it is back and working. Not sure why that was necessary, but it did the job so far.
With stock settings of KDE Plasma Workspace in openSUSE Leap 42.1 installed from scratch:
System settings — Workspace — Shortcuts — Global keyboard shortcuts
action (PrtScr) seems to have no effect at all, regardless of key assignments: even if some other combination is bound to Global alternate shortcut for this, nothing happens upon pressing that;
Take active window screenshot
(Win+PrtScr) — works as expected;
Take full screen screenshot
(Shift+PrtScr) — works as expected.
So it looks like the generic PrintScreen action is simply not handled. The solution is to use the more specific shortcuts.