The Console.app found in the Application -> Utilities folder (or Other folder in Launchpad) gives you access to the logs for the machine.
Under /var/log, the file named install.log (and any variants named install.log.x.bz2) will give you the information about the last install.
Note the files named install.log.x.bz2 are older versions of the same file created duting a process called rolled over when the file size of the current install.log file reaches 1000K
You need to search your install.log for the string "OSXUpd10.8.2Supp.pkg" which will give you an idea of what happened during your install.
Update: From your log file, it would appear that your have a Kernel Extension that is causing this issue. Either it has a permissions problem, or is somehow causing this annoying issue.
can you paste this line into Terminal, and post the results?
kextstat -kl | awk ' !/apple/ { print $6 $7 } '
Update 2: This would appear to be at least a trial and error solution. There are multiple threads on the Apple Support forums, from installing 10.8.2 to installing Xcode. Each one has different people each having issues with different kernel extensions that when removed resolved their issues.
I'm afraid I don't have any way to determine which of your kernel extensions is the cause; someone else may be able to shed more light. I would however expect the Virtual Box and Parallels extensions to be fine, not the least since I have them both also, but that this issue would be more widespread if they were the issue.
Finally: the manual for kextcache advises that using the touch command on /System/Library/Extensions/ forces the kext cache to be rebuilt. You could use this as a method to determine which kext is causing the issue by uninstaling each in turn, performing the cache update and checking the logs to see if the cache was updated successfully.
When you have problems to empty the trash, rm -rf ~/.Trash/* in the terminal does the job for you.
Edit :
You have to keep in mind that there might be multiple .Trash directories.
For example on a USB stick or a external Drive, OSX will create another .Trash at the root of the drive. So you might need to use rm -rf /Volumes/DriveName/.Trash.*
Best Answer
Finder’s trash can is an amalgam of several different directories:
~/.Trash//.Trashes/<uid>/on each volume (including the startup volume)e.g.
/Volumes/Big Media Volume/.Trashes/501/Most trash operations will move the trashed item to the directory under your home directory. If you trash something on an separate volume, however, Finder will move the item into the volume’s
/.Trashes/<uid>/directory instead (because moving a file to a location on the same volume is very fast, but copying a file from some other volume to your home directory’s trash directory could be quite slow).Try checking your main trash directory (in a Terminal window):
If the result does not look like start with
drwx------and show your user’s “short name” twice (the second is actually a group name), then your personal trash directory has probably been fouled. You can move it aside then logout and login again:This should create a new
~/.Trashdirectory for you. You may want to investigate the contents of the.Trash.oldfile/directory to try to determine its origin.If the problem is with a per-volume trash directory, you should be able to use the same idea: move it aside, eject it, then remount it (disconnect and reconnect an external disk, reopen a disk image, use Disk Utility to remount an internal volume):
You may need
… && sudo mv …if the volume has “Owners Enabled”.