There’s nothing quite like finally determining the cause of something like that. I know the feeling!
Hi Tracy,
I have the exact same issue (shortcuts involving ctrl-alt-cmd resulting in ctrl permanently stuck) on my MacMini and my MacBook Air, both of which have a Wacom driver installed. It appeared right after the last Mac OS X update (10.11.6).
Please keep us posted if you find an efficient solution to the problem. I will do the same.
Best
Benoît
Well, 14 days after reporting this issue, I finally got a reply, obviously from first-level support.
They simply suggested I install version 6.3.17-5. Don’t bother trying this, as it still has the issue.
Support does not seem to be aware of the fact that this issue has already been escalated to the driver team as per Tracy’s message above.
Now, what do all these experiences tell us about the quality of Wacom drivers, their QA and their support?
Just downgraded to 6.3.15-3 and it seems that does the trick.
I confirm that downgrading the Wacom driver to 6.3.15-3 solved the issue on my side.
1 Like
WHEE!!!
Today’s release of the driver, version 6.3.18.4, has fixed the problem!
(At least for me… YMMV)
1 Like
Wow, Peter just pointed me to his thread. I wrote to him about having the very same problem and I too have a Wacom Cintiq. I am going to install the new driver and hope this solves it. So glad to get this information. Thank you!
I too am having this issue. I have a basic Wacom Intuos tablet, but I completely removed the Wacom drivers and Wacom software last week and KM is still crashing my keyboard when I invoke a few specific macros.
The main macro I am having an issue with is a bit of a hack. I have an if/else action that checks to see if the Mac app xScope is running, if it isn’t, it opens the app, pauses until the app is running, pauses 1 additional second, then types a keystroke (cmd+option+control+m) which activates a specific tool inside xScope.
Now I invoke this macro through Alfred via some AppleScript:
on alfred_script(q)
tell application "Keyboard Maestro Engine"
do script "23)xScope: Measure"
end tell
end alfred_script
If xScope is running and I invoke the macro separately through Keyboard Maestro and Alfred, everything fires completely fine. If xScope is not running, the macro works fine through Keyboard Maestro, but if I invoke through Alfred via the AppleScript, my keyboard starts typing characters like this “ÅÍÎÅÍÎÅÍÎÅÍÎÅÍÎÅÍÎÅÍÎÅÍÎÅÍΔ instead of “asasasa” and I have to restart the computer to get my keyboard back to normal. I have tried 3 different keyboards, so it is not a hardware problem.
Any ideas?
My guess would be that you have not entirely eradicated the Wacom driver.
Rats. The problem came back after updating the Wacom driver. I used the Wacom utility to uninstall the old driver. Is there something else which could have remained? How would I know?
I went through and deleted everything I could find, but yea, you are probably right, there must be some leftovers that are causing the problem.
I installed the latest Wacom Driver (6.3.18.4) and the problem got way worse for me. The keyboard is crippled anytime I invoke triggers on Alfred via my hyper key, so this issue is well beyond KM at this point. I am just going to wipe and do a clean install.
Is there any fix for this yet? Nothing seems to work!
###Logitech Control Center Issues
No one has mentioned using a Logitech keyboard or mouse, but I’d like to add to the knowledge base here that the Logitech Control Center (LCC), when installed, can sometimes cause erratic key behavior.
In my case I found that it was causing a “q” to be typed after I had issued a ⌘Q to quit an app.
After I removed the LCC, I did not have any more problems with the “q”.
If you want to see my troubleshooting, with suggestions from others, see:
What is Causing the Character “q” To be Typed?
I have tried installing every driver, uninstalling every driver, removing everything related to wacom manually, nothing works!! all happened after I installed these damn drivers!!
Check out these troubleshooting steps provided by @Tom.
If all else fails, and it is important to you to make things work correctly, you may need to do a clean install of the macOS, and then be very careful and selective about what stuff you install.
Thanks for your suggestion, but my problem is not the “q” problem, everytime my maestro does a shift modifier key, the shift is beind held down several times due to something the wacom driver did to my mac! 
Perhaps you need to find all references to any wacom software and delete it.
In the Terminal:
find / -iname "*wacom*" -print
might do it, though they may use some other names too.
Be careful with what you delete though!
Ok this is crazy guys, I even changed to my girlfriends mac, no wacom driver has ever been installed there, its even El Capitan, not Sierra like mine, and upon making a makro that requires the press down of shift key, the key is being held down all the time!
Look at this example, I want to make a smiley with one hotkey just a simple “;)” and this happens:
";));)););)," See it shoots out like 4 times of what it should!! same with my mac!
OP here. It’s not Wacom, obviously. (I have not had the problem thru the last several updates.)
Create a new user on your machine. Login with that user, and see if the problem remains. If it’s gone, it’s some startup item with your regular user, or something installed for that user. If the problem remains, then it is likely something as simple as some startup item you share with your girlfriend.
Tvalleua, thanks for the response but this is something I have already tried… switching user, switching MAC… trying every version of Wacom… This happened right after I installed the Wacom driver so what else can it be… No matter where I go, or what version of wacom I install or uninstall, the shift is still being held down at random times of me pressing my macro.
It seems I am doomed