jackthelad

Q: Removing com.google.keystone.daemon

I have tried every suggestion that I can find to disable Google's auto update including the Terminal command:

sudo /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resou rces/GoogleSoftwareUpdateAgent.app/Contents/Resources/install.py --uninstall

 

According to my Console, this software update is being launched every 10 seconds. All Google software has been removed, as well as all Google Keystone related .plist that I could find, but to no avail.

 

Have anyone found a viable solution to this agent that continues to flood my Console searching for something that seemingly doesn't exist?

MacBook, Mac OS X (10.6.8), Intel Core 2 Duo Processor

Posted on Jul 28, 2012 6:19 PM

Close

Q: Removing com.google.keystone.daemon

  • All replies
  • Helpful answers

Previous Page 2
  • by WZZZ,

    WZZZ WZZZ Jul 30, 2012 5:15 AM in response to roam
    Level 6 (13,112 points)
    Mac OS X
    Jul 30, 2012 5:15 AM in response to roam

    Sorry, deleted and posted new reply to the OP

  • by WZZZ,

    WZZZ WZZZ Jul 30, 2012 5:28 AM in response to jackthelad
    Level 6 (13,112 points)
    Mac OS X
    Jul 30, 2012 5:28 AM in response to jackthelad

    Do you have Google Desktop installed? Did you install anthing Google for Safari? What other Google software do you have installed?

     

    What do you have if, anything, in /Library/Input Methods and ~/Library/Input Methods? (That's in your home folder/Library.) Might also be called Input Managers.

     

    Navigate to /System/Library/Extensions, what do you have, if anything, from Google there?

  • by roam,

    roam roam Jul 30, 2012 5:55 AM in response to WZZZ
    Level 6 (13,569 points)
    Jul 30, 2012 5:55 AM in response to WZZZ

    WZZZ

    here is the last paragraph. It skips your (phantom) question, though it was a good read.

     

    Reiterating your suggestion somewhat,...

     

    The initial inquiry proved that he has a bit of Google stuck in the guts of his machine, and I think the better course would be to 'go back to the drawing board' and examine all log-in / launch / startup items with reference to Google and remove them. It is surprising how many different locations for these there are. I don't think this was dome throughly enough to begin with. I reckon if he does that, he may solve the problem without resorting to surgery.

     

    Some places check. list is not exhaustive.

    ~/Library/LaunchAgents

    HD/Library/LaunchAgents

    HD/Library/LaunchDaemons

    HD/Library/StartupItems

    HD/System/Library/LaunchAgents

    HD/System/Library/LaunchDaemons

    HD/Library/StartupItems

     

    Message was edited by: roam

  • by WZZZ,

    WZZZ WZZZ Jul 30, 2012 5:56 AM in response to roam
    Level 6 (13,112 points)
    Mac OS X
    Jul 30, 2012 5:56 AM in response to roam

    I deleted my post because I realized it might not be a kext you were referring to. But sure, I'd like to read it. We've been focusing on Chrome, but what do you think of the other-Google-software-installed possibility? I would think uninstalling any of that wouldn't do any deep damage.

     

    EDIT: written before your latest post.

     

    Message was edited by: WZZZ

  • by roam,

    roam roam Jul 30, 2012 6:03 AM in response to WZZZ
    Level 6 (13,569 points)
    Jul 30, 2012 6:03 AM in response to WZZZ

    what do you think of the other-Google-software-installed possibility?

    Yes. they probably tie in at some point and it's that other bit that is being loaded elsewhere that has been orphaned from the part removal of the 'Google suite'.

  • by WZZZ,

    WZZZ WZZZ Jul 30, 2012 6:23 AM in response to roam
    Level 6 (13,112 points)
    Mac OS X
    Jul 30, 2012 6:23 AM in response to roam

    Might also try looking in /private/var/run/StartupItems (if it exists.) Paste into Go>Go to folder from the Menubar.

     

    Also think it might be worthwhile having a look in Activity Monitor>All Processes for anything Google or Google related.

     

    Just re-read more carefully and saw this.

     

    I should point out once again that all Google related programs have been removed (Chrome, Google Desktop, etc.), however some of the peripheral files may still be present, buried in sub-folders somewhere.

    So, yes, most likely something orphaned.

     

    Message was edited by: WZZZ

  • by WZZZ,

    WZZZ WZZZ Jul 30, 2012 7:24 AM in response to jackthelad
    Level 6 (13,112 points)
    Mac OS X
    Jul 30, 2012 7:24 AM in response to jackthelad

    jack: have a look also in your home folder/Library for Google and, same place, in Application Support/Google. Also in HD/Library/Application Support. Look for anything you may have left behind when you uninstalled.

     

    From ~/Library/Google (that's your user)

     

    Screen shot 2012-07-30 at 10.10.22 AM.png

     

     

    Right-click the GoogleSoftwareUupdate.bundle to show package contents. If you find GoogleSoftwareUupdate.bundle, trash the whole damned thing.

     

    Screen shot 2012-07-30 at 10.14.25 AM.png

     

    Also

     

     

    Screen shot 2012-07-30 at 10.23.23 AM.png

  • by jackthelad,

    jackthelad jackthelad Jul 30, 2012 5:49 PM in response to WZZZ
    Level 1 (11 points)
    Jul 30, 2012 5:49 PM in response to WZZZ

    WZZZ & roam...

     

    Thank you for your continued interest in helping me to solve my problem. As to whether it is truly a problem, or merely an annoyance, I'd have to confess to the latter. I'm not entirely certain that the issue at hand is actually affecting the performance of my computer. Rather it would seem that it is simply leeching some of my bandwidth sending an update query literally every 10 seconds. Nevertheless, I appreciate your willingness to lend a hand.

     

    In addressing your most recent theories and suggestions, here's where I stand. I've performed as thorough of a HD search for Google related items as I believe is humanly possible. After running Monitor activities for 'All Processes,' it revealed no Google activity leading me to believe we are on the right track. Exploring your additional suggestions for possible hiding places, I'm happy to report that most all were dead ends, although I did find a few other small and seemingly innocuous Google colonies elsewhere and have confidently eradicated them. There are 2 exceptions however: The previously mentioned 'Gild.frameworks'  and 'GoogleML.bundle,' neither of which do I have any idea of their intent or function. Both are the only Google folders remaining on my HD. I am prepared to eliminate them as well (to create a clean sweep), but I'd really like to know their purpose before doing so. Any ideas?

     

    At this point, and in light of my report, you're then probably wondering whether or not my logs still show any signs of 'com.google.keystone.daemon' gumming up the works. Honestly, I'm almost afraid to look for fear that if in fact it is still present, I may just chuck my laptop out the window in frustration.

     

    So, should I opt to rid my HD of the last 2 remaining vestiges of Google, I will then reboot, perform a maintenance check and gauge the outcome of our fishing expedition.

     

    I await your suspicions surrounding the importance of 'Gild.frameworks' and 'GoogleML.bundle.'

     

    Regards.

  • by WZZZ,Solvedanswer

    WZZZ WZZZ Jul 30, 2012 8:04 PM in response to jackthelad
    Level 6 (13,112 points)
    Mac OS X
    Jul 30, 2012 8:04 PM in response to jackthelad

    I wouldn't hesitate to  trash both of those. But don't empty the trash just yet. You can always use File>Put Back from the Trash if needed. But I don't see why trashing either of those will cause any problems. They are both third-party Google and can't possibly be essential to the OS.

     

    Most hits I'm seeing for those are related to problems with Safari crashing. Must be part of, or orphaned from, some Google input manager.

     

    Message was edited by: WZZZ

  • by jackthelad,

    jackthelad jackthelad Jul 30, 2012 10:02 PM in response to WZZZ
    Level 1 (11 points)
    Jul 30, 2012 10:02 PM in response to WZZZ

    WZZZ...

     

    In an earlier comment, roam seem to feel assured that the Gild.framework and its associated driver should be 'unloaded' rather than 'trashed.' See below:

     

    com.google.driver.Gild' does ot exist.

    It does exist. You have already proved that. But it is not something to be found in Finder. It is a process that is loaded in the kernel.

    I said "This driver sits at a fundamental level"

     

    It does not have to be removed, it has to be unloaded. using the correct command in Terminal.

  • by roam,

    roam roam Jul 30, 2012 11:02 PM in response to jackthelad
    Level 6 (13,569 points)
    Jul 30, 2012 11:02 PM in response to jackthelad

    Disregard my previously overcautious advice,.

    Go ahead with WZZZ's advice and trash all the Google you can find

  • by jackthelad,

    jackthelad jackthelad Jul 31, 2012 6:07 PM in response to roam
    Level 1 (11 points)
    Jul 31, 2012 6:07 PM in response to roam

    roam & WZZZ...

     

    Problem solved!! I held off on trashing the last 2 items (mentioned above) solely out of trepidation, assuming that if all else failed I push the button. I then tempted fate by running one last maintenance check before pulling the trigger. Surprisingly, the 'google.keystome.daemon' that's been filling up my system logs with calls every 10 seconds has been terminated, apparently after the last batch of Google related files that I found were trashed. Among them was Google Talk, the last item that I had systematically eliminated. Although I've never downloaded Google Talk )as I have no use for such services), components of it somehow managed to find their way onto my computer. Perhaps it's a part of their Google+ social networking garbage, although again, I've never signed up for it, nor have I created an account.

     

    Regardless, the culprit appears to be gone (at least for now) unless it somehow manages to stealthily penetrate my system once again.

     

    I sincerely thank you both for your input and for your salient suggestions in walking me through this. My regards to you both.

  • by jackthelad,

    jackthelad jackthelad Jul 31, 2012 6:57 PM in response to jackthelad
    Level 1 (11 points)
    Jul 31, 2012 6:57 PM in response to jackthelad

    Oh yeah, just to clarify --- the Google Talk file that I disposed of was NOT an application. All (3) of my former Google apps were among the first of items to be deleted. If memory serves, I found the folder in either my Application Support folder or Input Managers. Although I don't recall specifically what sort of files were contained within, I simply knew that I had no use for anything like Google Talk and chucked it. It may have merely been an element that was present and ready to be utilized should I ever wish to put Google Talk in place. I hope that's of help to you, and anyone else troubleshooting this same problem.

  • by roam,

    roam roam Jul 31, 2012 8:27 PM in response to jackthelad
    Level 6 (13,569 points)
    Jul 31, 2012 8:27 PM in response to jackthelad

    That's good news. It was a bit of a saga, and glad you fixed it.

  • by WZZZ,

    WZZZ WZZZ Jul 31, 2012 8:29 PM in response to jackthelad
    Level 6 (13,112 points)
    Mac OS X
    Jul 31, 2012 8:29 PM in response to jackthelad

    That is great news. Glad it's sorted out and hope it stays that way.

Previous Page 2