I've tried to add keyboard shortcuts to start mate-screenshot in various different modes -- in particular, to be able to capture a screenshot of an area with Ctrl+Prtsc -- but it doesn't seem to actually work. Am I setting this correctly?
Pressing Ctrl-Print doesn't do anything.
in v17.04 and I think in almost all previous versions for me it was already set and no need for any additional key binding.
On my keyboard it is just print scr and it takes a snap shot. (in reality mine is FN + Print Scr) because it share the Home key.
I've always found that handy and have never had to set it up. and I just plugged in a different keyboard with just print scr and it work fine too.
Certainly PrtSc takes a full-screen screenshot. However, I’d like to bind “screenshot an area” to Ctrl+PrtSc, and that’s what’s not working…
Working here. Contol+PrintScreen executes “mate-screeenshot -a”, then the mouse pointer changes and I can click and drag an area on the screen. Upon releasing the mouse button, dialog pops asking where to save.
You can also use scrot.
*(If it’s not allready installed.)
sudo apt install scrotNext command waits for you to select an area, creates the image and then moves it to the ~/Pictures
No confirmation or dialogs, it just saves with the defined image name.
scrot -s '%Y-%m-%d_$wx$h_scrot.png' -e 'mv $f ~/Pictures/'More on scrot command in the manual and help.
man scrotscrot --helpCan you tell me where you set that up? (Or perhaps it was done for you as part of installation? It doesn't seem to have been done for me, when I installed the UM desktop on Ubuntu 16.04.)
I've set this up with the same way as you.
The only difference is this is 17.10 
Hi @sil,
Did you try a combo other than Ctrl+PrntScrn?
Are you running compiz (it would normally be set in Mate-Tweak)? That DOES change things. If so, are you familiar with CompizConfigSettingsManager? It can be set there under “Commands”.
By the way, my hotkey on this 16.04 install is Ctrl+Shft+PrntScrn.
I am, I am, and I will use ccsm which I'd forgotten about. Thank you!
Immensely frustratingly, I can't bind Ctrl-Print in ccsm. Or, more accurately, I can, but I get an error sound when I use it. I can bind something other than Ctrl-Print to "take a window screenshot" and it works, so this suggests that Ctrl-Print is already bound to something else, perhaps... but I don't know how to find what that is...
I’m seeing the same and I believe that’s why I used Ctrl+Shift+Print.
By creating and searching a full compiz profile I don’t see Ctrl+Print being used by compiz anywhere. Unfortunately, there’s lots of layers in keyboard mapping where this may be.
EDIT…
Hmmm… and now, after resetting then key-grabbing, it’s working as Ctrl+Print. Yet I know it didn’t work at one time.
Question. You get a beep. Do you get that beep ONLY after programming Ctrl+Print? If you get it all the time it could be another mapping somewhere.
Here is a deeply weird thing. I get a beep (well, more a sort of echoey clang -- the error sound) when hitting Ctrl+Print. But if I hit Ctrl-Print lots of times, I get lots of error sounds... and a screenshot grab cursor! So it seems like there's some sort of race-condition error thing going on here...
[quote=“sil, post:11, topic:15561”]So it seems like there’s some sort of race-condition error thing going on here…[/quote]It sure does. I spent a career tracking down race conditions of the electrical type.
I’m not seeing that here based on only 10 times in a row it’s working when I know it didn’t before. I turned on sounds (normally off) and tried some stressing but no sign of failure and no sound except the camera-shutter on screen grab.
BTW, I know I would have selected the obvious Ctrl+Print if it had worked. I suspect some setting is different but this install goes back to May 2016 so it could be a lot of things.
I’ll play around with a virtual machine but graphics isn’t a VM’s strong suit.
EDIT: Did you by chnace leave the custom shortcut still in your system in the regular Keyboard Shortcuts?
No luck on a virtual machine running compiz. It’s unstable BUT just got an upgrade for VirtualBox for later.