For those who don’t like to read: the fix.
I upgraded to Snow Leopard (OS X 10.6) from Leopard (OS X 10.5) last week and everything seemed to go off without a hitch, until…
I have a bluetooth, wireless, keyboard that I use for work. At some point in the past week, not initially, my keyboard started acting up. At first I didn’t think anything of it because the lady’s computer is also paired with the same keyboard and when the problem first occurred it was because the keyboard was connected to her computer, also on Snow Leopard, rather than mine. I ended up removing the keyboard from her bluetooth setup and re-pairing (no pun intended) the keyboard to my computer. Everything worked fine and I went through my day.
The next day, I found that my keyboard would not pair up again. WTF!? So I go through the process again, thinking maybe Laura and I did a keyboard swap or something and that was the problem. Re-paired, everything’s cool. Whatever. If it happens again, I’ll deal with it.
Finally, today, day 3, I start up my computer and the keyboard won’t connect. Immediately I try to re-pair the keyboard and suddenly the computer tells me there must be some compatibility issue. Thanks Apple. I have an Apple keyboard I’m using with an Apple Macbook Pro and I have a f***ing compatibility issue. You’d think they would make sure that bluetooth continued to work between upgrading from Leopard to Snow Leopard. Oh well.
So I resort to Google. And basically what I find is that I have to reset my System Management Controller (SMC). Do I know what an SMC is? No. Do I care? Not really… okay, so I do a little. Apparently the SMC handles a lot of the lower level operations performed by the computer like “the power button”. Sweet Apple. Okay, so what to do. You have to reset the SMC. To do this follow the steps specified here. Be sure to read through the process and select the procedure that matches your computer. Different laptops, desktops, etc. will have a different method for resetting the SMC.
All in all, it’s disappointing that Apple overlooked this issue. Seems too often that companies can be aware of an issue be keep it quiet for the majority of users that don’t use (in this case) bluetooth, while those that due have to spend have their day in frustration.
Dear Apple,
Don’t pull Quit pulling a Microsoft.
Your Friend,
Mr. Customer
Today I was messing around with the built in Apache server on my Mac. What I was doing seemed simple enough; start my apache server with Web Sharing turned off in my system preferences. So I turned off Web Sharing and went for my Terminal, entering:
apachectl graceful
Expecting Apache to restart/start I was surprised to get this error:
launchctl: CFURLWriteDataAndPropertiesToResource( /System/Library/LaunchDaemons/org.apache.httpd.plist) failed: -10
After searching around online for a bit I realized that my problem was I failed to enter the command as root (or I forgot to put sudo in front of my command.
With a second attempt I entered:
sudo apachectl graceful
And vuala, apache is on. No errors. However, now when I enter:
sudo apachectl status
I get this error:
/usr/sbin/apachectl: line 106: lynx: command not found
Not sure what that’s about. If anyone’s got any ideas, I’d appreciate it.