Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Security Update 2006-002 is out
- Thread starter rinseout
- Start date
- Sort by reaction score
Good to know I'm not the only one. Shiira doesn't work on any of my machines now.pawnstar said:
Whistleway said:I'm loosing my confidence on the mac platform these days.. don't get me wrong.. tiger on my ibook runs great.. but these
Compared to what? Windows which has security updates regularly every 2nd Tuesday of the month? Can you name a major virus, trojan, or worm that has affected Macs wholesale that would lead you to lose confidence in the Mac platform? Seems you are being a bit irrational in your loss of confidence.
The Mac is a SAFER OS (than Win), not a 100% safe OS. Any OS can be cracked is someone tries hard enough. If you go around like you are immune then maybe it's good you are becoming worried.
The other funny thing was my wireless signal dropped and it I tried to connect to my router and it said it failed to connect.
The only solution was to turn off AppleTalk. So now I can't communicate with my PB box, but I can write this post.
What's going on here...
The only solution was to turn off AppleTalk. So now I can't communicate with my PB box, but I can write this post.
What's going on here...
Thanks for the Shiira fix, I was worried I would have to go back to Safari for a second.Mitthrawnuruodo said:Hmmm... you seem to be right... Shiira starts up (ie. the icon appears in the Dock) but then nothing... no browser window, no menus, nothing...
Edit: Possible solution.
Edit 2: Yes, getting rid if ~/Library/Shiira/History.plist works. I got my backup browser back...
Go > Network broken?
After I installed the security update, trying to connect from my G5 iMac to my G4 iBook via Go>Network is broken - selecting Network has no effect. On my iBook (without the update), Go>Network works as it should.
Permissions were repaired before and after updating.
Does anyone else see the same behaviour? Any fix?
PS I know I can access Network via different routes - I just prefer to use the Go > Network one.
After I installed the security update, trying to connect from my G5 iMac to my G4 iBook via Go>Network is broken - selecting Network has no effect. On my iBook (without the update), Go>Network works as it should.
Permissions were repaired before and after updating.
Does anyone else see the same behaviour? Any fix?
PS I know I can access Network via different routes - I just prefer to use the Go > Network one.
Unless you follow rest of the advice from the link above and (temporarily until Shiira's updated) make the ~/Library/Shiira/ folder read only...joecool85 said:
Doctor Q said:
And of course number 3 and on the internet the most plausible...
Some people, not unlike some Elephants, are just Jerks.
I had very bizarre problem with my display upon rebooting. Instead of the usual blue screen, it came up purple. Then, my desktop looked posterized. Messing around with display settings did not fix; but luckily when I rebooted a second time, colors were normal. I still seem to be having a problem with my cursor; it occasionally vanishes from the screen. (Video card is the ATI X800XT, monitor is a Viewsonic VX900-2.)
Grasbak said:
"Repairing permissions" is part of the folklore in the Mac world. There is some very limited sets of circumstances where this might actually do something, but 99 percent of folks who use Mac site will swear to you that this has to be done. I've only used Macs for three years now, and I have never repaired permissions. I have a friend who has been a Mac fan for 20 years or so, and never repaired permissions.
There is a site for a group of Mac software engineers, "Unsanity", where there is an article explaining how unlikely it is that permissions need to be repaired, but that will not stop dozens of people from making a big fuss about this.
By the way, I am a Unix Systems Administrator and work with permissions all the time, and can tell you that it will be very rare that they will solve a problem when you install something, and virtually never will fix an upgrade from Apple.
But it can't hurt to do it - just don't expect much...
Well, since permissions just became an issue with OS X, then 20 years without repairing permissions isn't too impressive...notsure01 said:
Also: It's a hassle free and unharmful first line of troubleshooting, along with a simple reboot. And if trouble have occurred right after a major upgrade or software installation that required admin password, then it from time to time is enough to fix the problem. Not often, but still worth trying before bringing out the big guns...
And it does work every now and then: Example.
Mitthrawnuruodo said:Well, since permissions just became an issue with OS X, then 20 years without repairing permissions isn't too impressive...
Also: It's a hassle free and unharmful first line of troubleshooting, along with a simple reboot. And if trouble have occurred right after a major upgrade or software installation that required admin password, then it from time to time is enough to fix the problem. Not often, but still worth trying before bringing out the big guns...
And it does work every now and then: Example.
More often than not, when you repair permissions, you usually combine it with some other trivial "troubleshooting step" that actually fixes the problem. That is, you might log out/log in or you might restart after repairing permissions, and so it only seems like repairing permissions fixed the problem. In reality, it probably didn't.
Here's the Unsanity post about repairing permissions. The summary in a nutshell? Repairing permissions either before a system update is useless, because you give it your admin password, so it can overwrite any incorrect permissions anyway. After it's installed, everything has correct permissions anyway, so repairing won't help (at least everything that was modified has correct permissions, anyway).
Unless you have a specific reason for suspecting that repairing permissions will fix your problem -- like the Console specifically reporting a permissions error -- then repairing permissions is NOT going to fix your problem with 99.9999% probability. Granted, repairing permissions doesn't hurt, but in the vast majority of cases, it doesn't help either.
I honestly can't remember the last time I repaired permissions.
And Apple Support suggest that it might not be entirely useless:simX said:
I trust my own experience, and Apple Support, over unsanity.org...
I have had a problem with this update.
When i switch user, then switch back my monitor profile changes from adobe rgb to generic rgb (washed out) and you cannot change it back without a restart.
anyone got any ideas
ive repaired permissions and zapped the PRAM
When i switch user, then switch back my monitor profile changes from adobe rgb to generic rgb (washed out) and you cannot change it back without a restart.
anyone got any ideas
ive repaired permissions and zapped the PRAM
Mitthrawnuruodo said:And Apple Support suggest that it might not be entirely useless:
I trust my own experience, and Apple Support, over unsanity.org...
I've noticed that after repairing, or verifing permissions, my RAM in activity monitor get refreshed and I get a lot of the free (green) ram back in the pie chart.
Why is that?
I have no idea...quigleybc said:
Tested it myself because I just had to see if I could replicate it (and it's been a while and a couple of installs and upgrades since I repaired permissions anyway).
Before I started repairing permissions (using MainMenu) I had ~88 MB free (green) RAM and when it was finished that was increased to ~125 MB. Didn't do anything else in the mean time. Of a total of 640 MB that seems like a significant change.
But I have no good explanation as to why this happens... the only thing I can think of is that maybe the diskutil command (which is the one repairing the permissions) quits some processes (temorarily?) to perform its task and that this frees a bit of RAM...
Mitthrawnuruodo said:I trust my own experience, and Apple Support, over unsanity.org...
Yeah, and I trust my own experience over both Apple Support and unsanity.org. But in this case, my own experience correlates really well with the explanation over at unsanity.org: I can't recall the last time repairing permissions ever fixed a problem in the past few years of using Mac OS X. I used to do it as a troubleshooting step, but now I don't -- unless there's a specific indication of permissions damage, I don't bother.
Just because the Apple Support article says that permissions can cause slowdowns doesn't mean that it happens a lot. It just means that a slowdown could be caused by incorrect permissions. Repair permissions as a troubleshooting step if you must, but I find it to be more useless than useful.
simX said:
It's pretty rare but I've seen it resolve an issue in three threads this month alone. Since it's so easy to do, it's a very good first step.
I don't know anything about slowdowns (apart from what the above mentioned article says) but when an application misbehaves (like won't start, which the article also mentions) then repairing permissions, along with ditching the applications preference file, is the easiest thing to try first. And in most cases this, along with a reboot, this will fix the problem.simX said: