When booting up, Greenshot is set to automatically start. Prior to having Greenshot installed I had another screen capture software installed and when I uninstalled it, it left the "PrintScreen" button registered still.
I now get the warning message below (attached screenshot too) each time I boot up. Where do I find this setting and how do I remove the error?
"The hotkey(s) "PrintScree" could not be registered. This problem is probably caused by another tool claiming usage of the same hotkey(s)! You could either change your hotkey settings or deactivate/change the software making use of the hotkey(s)."
In spite of this message, the hotkey "PrintScreen" does work properly for Greenshot.
I am not sure why this message appears even though the hotkey is obviously registered - would you mind to upload/send us your log file, or the part of it when this happens? You can simply [access Greenshot's log file](http://getgreenshot.org/faq/where-can-i-find-greenshots-log-file/) from the "About" dialog.
Anyway, as a workaround you can try changing the hotkey in the settings dialog, "General" tab, see screenshot.
Thanks and best regards,
Thanks for the prompt reply. I have uploaded my latest Greenshot.log file for you to peruse.
Thanks for the log... however, I could not find anything special in there.
When you are saying that the PrintScreen hotkey is working properly, are you sure that it is actually Greenshot responding to the PrintScreen key press? Or could it be the funtionality of another program that is still installed and registering the hotkey before Greenshot can do so?
The behavior of the PrintScreen key should be exactly the same as right-clicking the Greenshot icon and then clicking "Capture region", depending on your configuration. By default, the destination picker should be displayed, providing options what to do in the next step. (see screenshot)
Can you confirm that this is the case?
Changing the shortcut for "Capture region" to something else should make the message go away, but will probably not fix the actual problem causing it...