Kernel panic in 10.8.2 solved (for me)

Question

Thanks to the Apple Support crew who spent hours on the phone with me figuring this out. S, you are great!
Background:
I have seven machines from Apple.  These range from Macbook Air to iMac to numerous others, all Intel-based.  Over a period of a month I began upgrading from 10.8.1 to 10.8.2, one machine at a time, and with days betweeen working on the next machine.  Each time I upgraded a machine I began experiencing kernel panics upon startup on the upgraded machine.  These kernel panics began the same day I did the upgrade, and often I'd have three kernel panics back-to-back before I was ever able to log in.
Apparent Cause of the kernel Panics:
I use the word "apparent" as not to lay blame.  Nevertheless, the common denominator on all the panic machines was the remote login software called LogMeIn (as far as I can tell).
How to Stop the Panics:
I suggest doing this only if you can do without using logmein.  If you can't, you might want to move or rename files rather than delete them, or beat on the logmein support staff to hurry up and fix this apparent conflict.
LogMeIn has files and daemon processes all over the place.  Open a terminal window and change directory to /Library/Application Support/LogMeIn
The % sign is the command prompt in the following examples.  Don't type the % sign in your command.
"cd" is the command for changing directories, "ls" is the command for listing directory contents, and "pwd" is the command for identifying where you are in the file structure.
cd like this:
% cd /Library/Application\ Support/LogMeIn
Note the "\" backslash character above.  That lets terminal know you are entering a space between the words Application and Support.
You may have to do additional hunting, but find a file in the LogMeIn directory (or possibly a slightly differently named LogMeIn directory) called uninstall.sh  The file uninstall.sh is the LogMeIn uninstaller, and it will be in one of the logmein directories.
Run the LogMeIn uninstaller from inside the directory where it is located:
%./uninstall.sh
The uninstaller doesn't seem to do much uninstalling, but it does stop a few daemon processes from being cranked up.  You've now killed most of the logmein daemon processes but not all of them.  You will also still have the round logmein icon up top on your command bar and the LogMeInGui application showing up in the startup list rolling through your console.
Go back to the finder, and look in Macintosh HD/Library/Internet Plugins.  Find the logmein directory and delete it.
At this point, the kernel panics will stop, but you'll still have a few logmein daemons running and the icon will still be on your command bar up top.
Either spotlight "logmein" or search a few library directories for logmein subdirectories.  Delete them all.
Search these:
MacintoshHD/Library/Application Support/ ... any logmein stuff in here
MacintoshHD/Library/LaunchAgents/
MacintoshHD/Library/LaunchDaemons/
Under your username you need to look in the Library directory.  If you haven't already created an alias for it so you can see it all the time, press the option key while you are in finder and already looking at the "Go" menu from up top.
In username/Library, look in these directories: (and do it for each username on you machine to be safe)
/username/Library/Internet Plug-Ins/
/username/Library/LaunchAgents/
To round out the extermination, you might want to do one final spotlight for anything logmein-related, and delete it.
For the record, I used logmein daily to connect to my office and to help administer remote machines.  I'll gladly return to using the software once this weird system killer has been fixed.  Other than the kernel panics it caused with 10.8.2, I found logmein to be some of the most user-friendly remote access software around. I was never fully comfortable with all the daemon processes, and as for security, it always gave me the creeps, but those are my own personal disorders....
I haven't had a kernel panic since, and I also no longer spend every waking hour of my time at home logged into my office machine.  Double whammy.

Answer 1

Nice work, thanks for the report, hopefully it'll help someone else!