OSX "Leopard Problems" and Fixes....

xzusa8ky · Post by **xzusa8ky** » Wed Feb 20, 2008 2:08 pm

Don't Believe the Hype!

Flavor.......

xzusa8ky · Post by **xzusa8ky** » Wed Feb 20, 2008 2:11 pm

Hi Yhtomit

Nice to see that you help other users

But! I can only advice people NOT to repair their permissions with the Original Leopard 10.5 install disk!

Why? The disktool is not working proberly on the original 10.5 Leopard release!

Apple did actually first fix the disktool with the Combo Update in 10.5.2

So please do NOT use the disktool from the Original 10.5 disk.!

I am still having problems myself (and thousands of other users! Even Macpro users! see Apple Discussion Forum!) even after de-installing all hardware on my G5!

Still Kernel panics! And i can NOT use TM since 10.5.2 it still crashes my finder.

To all the loyal Apple people here, please notice that a lot of the problems i have is not hardware related and my 10.5 was also running for a couple of weeks, but it seems that the system STILL got some seriously bugs in it!

So take care! Even if your system seems to run smooth today. Tomorrow it could be you writting the next post here....

Kind Regards

Yhtomit · Post by **Yhtomit** » Wed Feb 20, 2008 2:45 pm

xzusa8ky, Thnx for the info. I have edited my post

icedsushi · Post by **icedsushi** » Wed Feb 20, 2008 3:04 pm

Thread summary:

xzusa8ky wrote:Leopard Sucks! Apple the new Microsoft?

xzusa8ky wrote:Yes i know this ain't gonna be true for everybody, but for me it is! What a Horror release!

OvertoneZero wrote:Seems ok for me.

jesso wrote:No probs here. The original poster must have something wrong with his computer.
Sucks.

xzusa8ky wrote:Hi

The problem is FIXED!

xzusa8ky wrote:Leopard Sucks! Apple the new Microsoft?

xzusa8ky wrote:
snowtires wrote:i have had absolutely no problems and i updated like a week after it was released. sounds like a problem with the user, not the os
Mr Clever! You just sound like you are an big Jerk!

xzusa8ky wrote:Leopard Sucks! Apple the new Microsoft?

For those of us not running Leopard yet, we now have some information to keep in mind before upgrading. According to the summary above ^ we have a set of facts, confirming theory of what seems to be an accurate claim here. Leopard sucks and is a horrible release. This has nothing to do with this xzusa8ky's personal configuration. And anyone who is running Leopard without problems is a jerk (except for xzusa8key who now has no problems) because this is a horror release for xzusa8ky even though it's not true for everybody.

xzusa8ky · Post by **xzusa8ky** » Wed Feb 20, 2008 3:18 pm

Hi Iced

Why do you bother then?

You are not even on Leopard yet?

It would be nice if you would stay to the topic.

If you haven't anything constructive to say!

Stay away!

Winston · Post by **Winston** » Wed Feb 20, 2008 3:19 pm

I've had a few glitches, but it runs good enough now.

What I've noticed:

Time Machine gave me lots of errors. It took forever to get it to back up. I just kept trying again. It would do a little bit of the backup and then quit from an error (It just said "error" but gave no details). Then I would try again it would take up where it left off. Sometimes it would stop right away. Eventually it did the whole back up and is fine now (The first time takes a long time because it back up everything at that moment).

Also, the new finder search feckin' blows. It's so much more of a pain in the arse to find what I'm looking for. No more nice categories automatically in finder searches and I have to specify every time I want to include my system files in the search. It worked great before and they had to mess it up.

xzusa8ky · Post by **xzusa8ky** » Wed Feb 20, 2008 3:26 pm

theire we go again

Nice to hear that some users are having problems too! and they do actually post them here so that other mac users can hear whats going on with this release from apple.

It's not a shame to admit that Apple is not perfect! (it never was!)

Even the big goodfather Steve Jobs can tell story's (and he is).....

icedsushi · Post by **icedsushi** » Wed Feb 20, 2008 3:42 pm

Hi xzusa8ky

I just think the thread title seems a little extreme and overreacting for what actually happened that's all. I think you'd get more help if you didn't jump to conclusions, make wide sweeping assumptions and call people a jerk if they don't have the same problems you do. In light of that, I was surprised how much help you actually did get.

But ok good point, and if you don't like to hear it, I am happy to keep my sarcasm and my opinion to myself. After all, Hyerstay and some others were more helpful than I was...

xzusa8ky · Post by **xzusa8ky** » Wed Feb 20, 2008 3:47 pm

No hard feelings Iced

I also got humor

heres some fresh news from MacFixIt:

http://www.macfixit.com/index.php

Mac OS X 10.5.2: Time Machine problems a'plenty

Time Machine problems a'plenty Time Machine continues to be the bane of Mac OS X 10.5.2 upgraders, causing a variety of issues that can hamper the function's own operation or interfere with other system processes. The most common problems are:
the error message "Unable to complete backup. An error occurred while copying files to the backup volume."
a situation where Time Machine is persistently "preparing" the backup but never actually starts backing up
dismal backup speed
A few recent reader reports:

Time Machine fails within the first few megabytes of data -- consistently.
"Every time Time Machine runs on my system I get a Kernel panic after updating to 10.5.2." -- Stu C.
"I just upgraded to Leopard yesterday and I cannot get Time Machine to function -- I left it to run overnight. I went to bed after several hours of "preparing." I will try your fix now. Wish me luck." -- Hope Luhman
"I had the same problem with Time Machine after update 10.5.2, it would stall at "preparing". I tried your fix using Console but it stalled as well. I finally fixed it by changing target disk and throwing away 3 months of backup. Its extreme but it worked."
"I am having the same issues on my mac. After the update, Time Machine has ceased to work. It won't recognize my backup disk. As a matter of fact, Time machine just gives the error "The backup disk image could not be mounted". The problem is, that the disk is mounted. I even deleted the old backup on that drive and tried to start over, but to no avail. Hopefully a fix is imminent." -- Dan Johnson"
Fixes
Boot in safe mode and backup Try booting your Mac in safe mode (hold down the Shift key while starting up), then performing a Time Machine backup. If the backup is successful, try restarting normally and backing up again. The process may no work normally on all subsequent attempts.

Switch to a different drive It appears that Time Machine under Mac OS X 10.5.2 may exhibit issues with specific types of USB drives. Try switching to a different drive and check for alleviation of the problems. MacFixIt reader Jim Stogdill writes:

"Time machine stopped working after the update, but oddly, when I switch it to another external USB drive it works fine. If I switch back to the old drive, a drobo, (even after deleting the previous backups) it still hangs. Console doesn't seem to indicate a problem with a particular file."

Repair Permissions Launch Disk Utility, located in /Applications/Utilities and run the "Repair Disk Permissions" function on both your startup drive and the used for Time Machine then restart.

MacFixIt reader Adam Sheck writes:

"I had same problem, went away after I repaired permissions and restarted."

Remove USB hubs If you're experiencing kernel panic assocaited with Time Machine, try removing all USB hubs and connecting the Time Machine drive directly to your Mac.

Delete backups Navigate to your Time Machine volume and delete the directly subsequent (most recent) and current backup then reattempt usage. MacFixIt reader Greg Hughes writes:

"I found that if I deleted the last back-up and the next back-up (I forget what that file is named) on Time Machine, after upgrading to Mac OS X 10.5.2, everything gets working again."

Check the system log As previously reported: Launch Console, located in /Applications/Utilities, then inspect the system log while Time Machine is running. You may find that it is getting stuck on a specific file or directory. Remove that offending item (by excluding it from Time Machine's designated files or moving it to a different drive) and re-attempt the backup.

MacFixit reader Joel Nelson recently found that Quicken files were to blame:

"It seems that in many cases with the Time Machine error in 10.5.2, Quicken 2007 data files may be at fault. I checked my console logs when I was getting the errors, and found that Quicken data files and backups were the problem. Interestingly enough, the files really are not "playing nice" with 10.5.2 as I also can't make a compressed archive containing those files. They aren't corrupt, as Quicken can read/write the files. But Quicken (2007; maybe earlier as well) seems to be the culprit. Excluding the Quicken data folder from Time Machine solved the problem. I'm still backing up my Quicken file to .Mac (which often works, but not always). Hoping to switch to iBank after I get 2007 taxes finished up."

Clear caches The old standby saves again. Try clearing caches with a tool like Cocktail or Leopard Cache Cleaner then re-attempt the Time Machine backup.

Change privileges Mac OS X 10.5.2 makes a number of privilege changes that can adversely affect Time Machine backups. Check to make sure that read and write privileges are accurate on the target Time Machine drive (all user accounts backing up to the device have access), or change standard accounts that are having problems to Admin.

MacFixIt reader George Wilde writes:

"I recently upgraded both the MacBook Pro to Leopard 10.5.2 and the Mac Mini to Leopard Server 10.5.2, and Time Machine ceased to run as a network backup. I traced the problem down to the account privileges of the User Account being used on the Leopard Server for backup. The account had been set up as a Standard Account which caused it to not recognize the external drive being used as backup on the Mac Mini. Changing this account to an Admin account solved the problem. I might have also been able to solve the problem by changing the staff privileges on the external drive to Read & Write. Leopard 10.5.2 altered a number of privileges and solved most of the privilege problems I was having under 10.5.1, but these changes may well have resulted in the Time Machine problems I was having."

The "Stephanie" process We couldn't think of a good way to summarize the process that Stepahnie Gans used to solve her 10.5.2/Time Machine issues, so here it is, verbatim: "In my case, when visiting the Time Machine app, I noticed that my previous backups had been deleted in the new OS's attempt to perform the Time Machine backup. So, I erased the drive - but still encountered an error stating that my destination drive didn't have enough room. I re-erased the drive, then, in the Time Machine System Preference, I turned off time machine, restarted the computer, turned Time Machine back on, and then selected an alternate drive for the backup - then reselected my original, newly erased drive. This seemed to work, and has been running for a few days now."

Yikes.

MacFixIt advice at work One MacFixIt reader had a number of serious problems with Mac OS X 10.5.2 that were solved, in quick succession, by fixes posted here. In case you're experiencing similar issues, here is his rpeort:

"After updating to 10.5.2 I had a kernel panic just after the inital startup. As suggested by MacFixIt i unplugged the only thing connected to my iMac 2.4 which is a 500GB WD Hard drive [Ed.- Suggested here], that seemed to solve the problem. I then found a firmware update [Ed.- Suggested here] for the drive and that seems to have solved the hard drive and kernel panics. I was also getting an error message from Time Machine under 10.5.1 and possibly 10.5.2, so after updating I erased the external hard drive [Ed.- Suggested here] and started again with Time Machine. No more kernel panics or problems with Time Machine."

Parallels problems, fix We continue to report on problems with the Parallels virtualization environment under Mac OS X 10.5.2. Now some readers are noting that having Firefox closed when launching Parallels can alleviate issues. One reader writes:

"Parallels 3 ( build 4128 ) will routinely fail with a EXC_CRASH (SIGSEGV) if Firefox 2.0.2 is open while starting up the emulator. If Firefox is closed, Parallels starts normally."

Feedback? [email protected].

Previous coverage:

Mac OS X 10.5.2: Time Machine broken; system utilities must be updated
Mac OS X 10.5.2: poor performance; AirPort, device issues; more
Mac OS X 10.5.2: Problems starting up; ACL messages in Disk Utility; more
Mac OS X 10.5.2 troubles: AirPort Problems, device issues; more
Mac OS X 10.5.2 released
Mail Story to a Friend 5 comments Most Recent Post: 02/19 10:45PM by chashulme_dotmac

Yhtomit · Post by **Yhtomit** » Wed Feb 20, 2008 4:12 pm

Also, disable Spotlight! Seriously. Spotlight is a constant CPU hog

How to turn off Spotlight entirely:

Go into sys prefs, to Spotlight. Unvink all search categories, disable keycommands too. Then hit the tab privacy and select all your internal and external drives. Remember the connections of the external drives to let them disabled forever.
Then put EasyFind into the Dock and use that instead to search data. Your search bar in Finder is also disabled now so you can go ahead and remove that.

Time Machine should also be disabled, of course.

jonny72 · Post by **jonny72** » Wed Feb 20, 2008 4:17 pm

I did a clean install of Leopard to a brand new hard drive, then used migration assistant to move everything over. Haven't had a single crash or problem so far, whilst my Tiger install was crashing all the time (especially Finder).

All of my applications are working fine as well, it didn't break a single thing.

condra · Post by **condra** » Fri Feb 22, 2008 6:01 am

Yhtomit wrote:Also, disable Spotlight! Seriously. Spotlight is a constant CPU hog

How to turn off Spotlight entirely:

Is there a way to simply "turn it off" ?

Tarekith · Post by **Tarekith** » Fri Feb 22, 2008 6:13 am

Spotlight is now used by a lot of different aspects of OSX, even apps like Logic make extensive use of the functions it provides behind the scenes. I'd highly recommend NOT turning it off.

Once my drives are indexed, I never have any issues with it affecting performance whatsoever. What kinds of issues are you seeing Yhtomit?

aqua_tek · Post by **aqua_tek** » Fri Feb 22, 2008 9:06 am

oh noez!

leopard workz fine for meez! am i abletun geek pariahz nowz?

Hervé · Post by **Hervé** » Fri Feb 22, 2008 9:35 am

5.2 is real stable here on a first gen blackbook . no probs, happy music making for me. (:

OSX "Leopard Problems" and Fixes....

For those just tuning in. No need to read all 4 pages.