During startup, googleleads / Doubleclick is trying to use my keyboard API
WTF is going on here? Macintosh CONSOLE MESSAGES:
6/2/14 9:05:00 PM [0x0-0x1c01c].org.mozilla.firefox[172] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/2/14 9:05:00 PM [0x0-0x1c01c].org.mozilla.firefox[172] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/2/14 9:05:00 PM [0x0-0x1c01c].org.mozilla.firefox[172] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/2/14 9:05:00 PM [0x0-0x1c01c].org.mozilla.firefox[172] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/2/14 9:08:01 PM [0x0-0x1c01c].org.mozilla.firefox[172] NOTE: child process received `Goodbye', closing down 6/2/14 9:08:30 PM [0x0-0x1f01f].org.mozilla.firefox[197] Background starting... 6/2/14 9:14:04 PM [0x0-0x1f01f].org.mozilla.firefox[197] NOTE: child process received `Goodbye', closing down 6/2/14 9:18:33 PM com.apple.launchd.peruser.501[114] ([0x0-0x1f01f].org.mozilla.firefox[197]) Exited: Terminated
6/2/14 9:19:04 PM [0x0-0x28028].org.mozilla.firefox[232] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/2/14 9:19:04 PM [0x0-0x28028].org.mozilla.firefox[232] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/2/14 9:19:04 PM [0x0-0x28028].org.mozilla.firefox[232] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/2/14 9:19:04 PM [0x0-0x28028].org.mozilla.firefox[232] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/2/14 9:21:41 PM [0x0-0x28028].org.mozilla.firefox[232] NOTE: child process received `Goodbye', closing down 6/2/14 9:21:44 PM [0x0-0x2a02a].org.mozilla.firefox[244] Background starting...
Alle Antworten (8)
I dunno, but I if were to see something that hinted that something was attempting to access my keyboard, I'd be thinking "keylogger?" and immediately reaching for the complete virus/malware/rootkit scan button.
Geändert am von pendantry
Keeps happening:
6/11/14 1:50:59 AM [0x0-0x271271].org.mozilla.firefox[5633] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/11/14 1:50:59 AM [0x0-0x271271].org.mozilla.firefox[5633] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/11/14 1:51:00 AM [0x0-0x271271].org.mozilla.firefox[5633] No permission to use the keyboard API for http://googleads.g.doubleclick.net 6/11/14 1:51:00 AM [0x0-0x271271].org.mozilla.firefox[5633] No permission to use the keyboard API for http://googleads.g.doubleclick.net
Geändert am von VerizonSucks
Are those messages generated by Firefox or by the OS or by some security software?
Have you considered blocking doubleclick.net? I'm pretty sure its only purpose is advertising.
The Mac CONSOLE application shows these error messages.
I'm wondering if this is the way they access mobile devices. But they are wasting MY clock cycles because they are too stupid to figure out that I'm using a real computer.
AFAIK Blocking would have to be at the level of my DSL router/modem and I'm not qualified to mess with that.
You can install AdBlock Plus, or the YesScript extension (block everything from doubleclick.net), or figure out how to use the hosts file for blocking it (this is a common approach on Windows).
I DO use Adblock.
Little Snitch is a good app to monitor all traffic & block connections. The free trial ran out but paying requires all sorts of uneccessary personal information I don't want to hand out.
I'll try YesScript...
EDIT: Oh, Snitch told me that doubleclick actually runs about half a dozen other-named URLs.
Geändert am von VerizonSucks
How do I turn this off? A while ago I looked at the Developer Tools to try and find some sort of log to track down these errors:
6/11/14 9:35:10 PM kernel firefox (map: 0x17d5e000) triggered DYLD shared region unnest for map: 0x17d5e000, region 0x7fff81000000->0x7fff81200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
I don't know about Mac console logging. Hopefully a Mac person can advise.