If you are using a Wacom tablet as your primary means of controlling your Mac, you may have noticed that you can’t access your Keychain any more – when something wants access to it and pops up the “type your keychain password” dialog, the ‘always allow’ and ‘allow’ buttons give you absolutely no response when you press them.
If you bring up the Console and try doing this, you’ll notice an error popping up when you try to press ‘allow’:
11/4/15 1:24:02.755 PM SecurityAgent[893]: Ignoring user action since the dialog has received events from an untrusted source
This is because Apple has added means to prevent applications creating “synthetic clicks on keychain prompts” to get access to your keychain without your authorization. Which is all well and good. Except it would be really nice if they would, you know, pop up an error dialog saying that this has happened, and which program provided the offending clicks, instead of silently doing absolutely nothing when you press the ‘allow’ button.
Sadly, the latest versions of Wacom’s drivers do not fix this. I tried both the latest drivers for the Intuos3/4/5 (I have a 3 on my desk and a 4 in my travel bag), and the higher-numbered latest ones for the “current Intuos Pro”; neither of them solved this issue. Nor did visiting the Security and Privacy pane of the system prefs and manually adding /Library/Applcation Support/Tablet/WacomTabletDriver.app to the list of apps allowed to control my computer.
So I guess now if I want to do anything involving the Keychain, I need to reach around my desk and open up my computer to use the trackpad to click on those buttons. Fun!
(When I’m at my desk, the computer is closed and plugged into an external monitor, you see.)
Anyway. Mostly I am documenting this so that someone else with the same problem can have some hope of figuring it out faster; I blew most of my morning on tracking this down.
And as a side note – holy shit there are way too many Wacom drivers on their driver download page. There are seven categories of drivers that all have the exact same version number (6.3.15-1), and I have a strong suspicion that same driver will actually work with pretty much anything that connects via USB – supposedly I should be using a different one with a lower version number (6.3.11w3), but I’m using the 6.3.15-1 just fine now. What the hell guys, consolidate that shit.
Edit. 28-Dec-2015: There’s a new version of the driver, 6.3.15-3. It’s still not a trusted input source.
Hmm, I had a similar experience last week – I was trying to diagnose an Internet connection issue to see where the problem was, but the Diagnostics process stuck when Keychain requested permission to make changes. In the end, I had to back out of the diagnostics, and wait for my ISP to pull their finger out. I also have an old Microsoft optical wheel mouse plugged in (mostly for 3D apps and games), but it made no difference. Touch wood, hasn’t reoccurred, but now I know it wasn’t just my bad luck.
I’ve got a Bamboo tablet, and according to their drivers page, the last driver version for Mac was released back in January of this year—nothing for El Capitan, it seems. Since Wacom decided to confuse the heck out of their customers by renaming the old Intuos range to Intuos Pro and the old Bamboo range to Intuos, I’m wondering if the latest (supposedly) Intuos drivers will work with my tablet? Only one way to find out, I suppose. Wish me luck…
I bet it’ll work. Won’t solve the keychain authorization issue (though I’m told Wacom is aware of that and is working on it) but it’ll probably work.
Right now the only way to authorize a keychain dialog box is to not generate ANY movement from an untrusted pointing device while it’s up. Which can be troublesome if you don’t have a trusted pointing device available, and can’t invoke the dialog via keyboard…
Ah, that’s really good to know. I always have a mouse hooked up to my computer as well as my Wacom (since I like switching based on what I’m doing) but I could see that issue seriously giving me a case of the WTFs if I ran into it.
The historical reasons for the proliferation of driver categories made some level of sense back when it first started (since they forked the driver for Intuos vs. Bamboo, as well as Intuos vs. Cintiq I think?) but yeah it’s gotten really out of hand. They should switch to just listing the three(?) driver types and all of the devices they work with, and then modifying the dropdown to make it more clear as to what model you’re selecting for the filter.
I think there’s also a weird split on the Bamboo line, which doesn’t help. And then they’re always renaming things but reusing the names of previous things. Like today’s Bamboo has nothing to do with the previous Bamboo (which was the replacement to the Graphire line). Oh and if you have an Intuos, a Cintiq, AND a Bamboo (as I do) things can get really confusing because you have multiple separate control panels to configure them!
Really they could just bundle all their drivers together and only have them show the configuration capabilities based on the device you select. And why the crap are the drivers 100+ MB apiece?
And why the crap do they also remove support for nearly-identical hardware from newer drivers too? (Yes I realize that sort of conflicts with the previous point BUT it tells me that the way they develop and maintain drivers is really freaking inefficient)
I’m going to go several steps further and say Wacom should have a SINGLE driver package per OS that needs unique drivers, period.
Linux has had a single unified Wacom driver for years, over a decade now I believe in fact, and I also believe this multitude of Wacom drivers is half of their stability problem: instead of troubleshooting one codebase they’re tracking dozens. :S
Pretty much, yeah. I was having similar thoughts. Mmmaybe like 3 at most for the weirder things like that ballpoint pen that records your strokes and their embedded hardware. But “I just bought a Wacom tablet!” should lead to one download no matter what.
Indeed, I had to remove my Wacom driver to get Keychain to work at all. The trackpad on the laptop was blocked, too. Wacom, WTF?
WACOM does not care–apparently
I received a case number and was told to install the latest driver software–DUH!
Did not fix the problem, I spent an hour with MAC support before I discovered using a regular mouse plugged in worked fine, the table would not.
It appears that this is caused whenever the process WacomTabletDriver is running. It doesn’t seem to matter if the Wacom is connected or not, or whether input is coming from a different input device or the Wacom tablet. I also tried to add WacomTabletDriver.app as a trusted input source application in System Preferences>Security & Privacy>Privacy>Accessibility, but that didn’t work.
If you kill the two WacomTabletDriver processes, you can view the password.
To “kill” or stop the WacomTabletDriver processes enter the following In Terminal.app:
pkill WacomTabletDriver
You can then go view the password or other information you are looking for in Keychain Access.app.
To restart the WacomTabletDriver processes enter the following In Terminal.app:
open /Library/Application\ Support/Tablet/WacomTabletDriver.app
You may be able to just double-click on the application WacomTabletDriver.app, but it’s faster to use the Terminal.
i know i’m a bit late but is everyone now saying that with the new el capitan on macs we can no longer use in my case the wacom intros 4 ptr-640? i’ve been trying to find the right driver since changing to the mac but if its pointless i will be going back to pc world..
My two Wacoms (an Intuos 3 and an Intuos 4) work just fine on El Capitan, aside from this security issue.