BUG: Renaming a file causes Finder to restart - after Update 2008-008
BUG: Renaming a file causes Finder to restart. This started occurring after installation of the Security Update 2008-008. I can't rename files or folders.
Is there a solution? A workaround? A software update? I repaired permissions but that didn't help.
But have you tried repairing the Hard Disk before Repairing Permissions?
Safe Boot , (holding Shift key down at bootup), & use Disk Utility from there to Repair Permissions, try dragging this file to the desktop, then reboot...
I tried all of the changes you suggested BDAqua, but the Finder still restarts when I try to rename a file or folder. I could use Terminal to rename files, but it takes so much more time! Is anyone else having this problem after the Security Update 2008-008?
Another poster said their computers crashed
when they renamed Folders in Finder. The
system log for that (different somewhat from
this) looked almost like a kernel panic.
This other issue was also related to the new
security update's installation in two portables.
Thought I'd ad this; though they may be different
enough to have unrelated specific causes outside
of the security update & resulting system issues.
Hi, I'm the "other user" that K Shaffer is talking about 🙂 I thought I'd add here that deleting .DS_Store files (using MainMenu) had no effect. And my RAM is fine, at least so far as memtest can tell me. You can read about everything else I've tried so far at "my" thread.
I deleted the .DS_Store file in a directory where I was trying to rename a file, but Finder still restarts when I try to rename a file. Sometimes the file rename is successful, most mostly fails.
Here's an excerpt of the crash dump referenced in the Console utility application.
Crash report written to: /Library/Logs/CrashReporter/Finder.crash.log
The first few lines shows that LockRenameUnicode is called when renaming the file, then the Finder crashes. What is causing this crash in Finder in Mac OS X 10.4.11 after installing the Security Update 2008-008?
Restarting the PowerBook G4 in Safe Mode (by holding down the Shift key) allowed the renaming of files in the Finder without causing a restart of the Finder. By the way, the Finder restarts when I hit the Return key to end my editing of a filename. I'll try restarting the machine without Safe Mode to see if that's changed.
[Mac OS X: Starting up in Safe Mode|http://docs.info.apple.com/article.html?artnum=107393]
[What is Safe Boot, Safe Mode? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=107392]
[Safe Boot takes longer than normal startup|http://docs.info.apple.com/article.html?artnum=107394]
Safe boot mode runs a directory check command similar to that used by Disk Utility's repair. In Tiger it ignores some stored information (cache) that is normally read that speeds up the boot process, and it moves some other caches to the trash. It also uses only System fonts and disables all startup items and any Login Items.
Note some of the things that starting in safe mode does. If you have startup items (Preference panel, accounts, login items) try disabling them to see if that does it. Perhaps using a tool such as TinkerTool to clear the caches might help replicate some of this (or check the third link which I think lists a cache file that may be removed).
I don't see anything obvious from your crash log that indicates third party issues but crash logs are not easy to read.
I had the same issues with the Finder restarting itself every time I tried to rename a file, after updating the Security Update 2008--008. I tried downloading and reinstalling the update manually, but that was only a slight improvement, as the Finder would relaunch, but allowed me to change the filenames until I closed a window. Then back to the same problem.
What I did to solve this was download the OSX 10.4.11 Combo Update and ran the installation. Only took a few minutes. Now things are running smoothly again.
From now on, I'm going to check these boards for issues with these updates before letting the Software Updater run automatically.
