Several years ago I bought Mel an iMac. It was a 27″, top of the line, all the bells and whistles. I secretly replaced her existing 21″ iMac with the new one after she had gone to bed one night. It took her several pre-coffee minutes to realize something wasn’t quite the same the next morning. Hilarity ensued.
After two and three quarter years, the video started glitching. Little pink artifacts that would dance around the screen, especially after long sessions playing World of Warcraft. Apple Care to the rescue, we took it in. They replaced the video card, and all was well. For a few weeks. Then they came back. Took it in again. This time they said they were going to replace the motherboard. When we picked it up, they told us they had just replaced the screen instead. No worries, we took it home and it worked flawlessly. Right until the Apple Care expired. Then it started flaking out with the same glitches. Two very expensive repairs, had they not been covered under Apple Care, and it looked like we were going to have to foot the bill on the last option: the mother board replacement they had opted out of on the last repair.
We made an appointment. We hoped to plead that this was a recurring issue that hadn’t been previously fixed, and maybe we could get out of an expensive repair.
We had several days before our appointment, and I kept thinking about why the previous repairs had worked temporarily. It couldn’t be that they had replaced the correct parts, and yet the symptoms had gone away. A loose, and/or oxidizing, connection could explain it. I took apart the front display, and disconnected the data and power connectors on the LCD. After putting it back together, the video glitches are gone again. This may only last a few weeks or months, but now I know how to fix it for free.
The moral of the story? Don’t be afraid to take your stuff apart!
Mavericks has a lot of nifty features, and because Apple thinks everything they do is nifty these features are turned on by default. A co-worker of mine recently upgraded to Mavericks on his work machine (I won’t do that until 10.9.1 is released next week), and he discovered that every time he walked away from his computer he lost most of his SSH sessions. He did some testing, and found that only SSH connections in SecureCRT were dropping, while test connections in Terminal were not.
Long story short, since I don’t want to blow up Gene’s ego in regards to his work diagnosing this, the problem turned out to be App Nap. App Nap is a new feature that puts applications into a suspended state while the screen saver is active, thereby reducing power consumption.
Why wasn’t Terminal affected? Apple engineers are well aware that sleeping a terminal app will cause dropped connections, so they completely removed the App Nap option from Terminal. You can’t turn it on if you wanted to. All other apps default to enabled.
So, if you are having issues with dropped connections, or other application wonkiness when your screen saver kicks in, head on over to here for the fix:
If you found this page looking for help compiling MacPorts for OS X 10.11 El Capitan, please check out this post.
FINAL UPDATE: 2013-10-26 – The Official MacPorts installer for Maverics has been released, so there is no longer a need to jump through hoops. Please visit the MacPorts Download page to get the official version.
If you are a bleeding edge lunatic who has installed Mavericks before the first patch release, you may have realized you can’t install any new MacPorts. You can search ports, but nothing will install. No worries, I can help. 🙂
Note: These instructions have evolved a bit since they were first posted, prior to the official release. If you visited before and had problems, try again now. These instructions assume you have already installed Mavericks.
- Follow steps 1, 2 & 3 of the Migration page: https://trac.macports.org/wiki/Migration
- Follow the Uninstall instructions: https://www.macports.org/guide/chunked/installing.macports.uninstalling.html
- Install Xcode from the App Store
- Launch XCode, agree to the license terms, and enter your password in the auth dialog box.
- Go to Preferences/Downloads
- Select “Check for and install updates automatically” and then click “Check and Install Now”
- Open a Terminal window:
## Reset your path, in case you have a previous install that
## might bugger the configure. (Thanks Rainer)
## Install Xcode CLI. Install dialog should open up and auth
## the install. (Thanks Drew, and others)
## Fetch MacPorts source code
curl -O https://distfiles.macports.org/MacPorts/MacPorts-2.2.0.tar.bz2
## Uncompress source and change to the source directory
tar jxvf MacPorts-2.2.0.tar.bz2
## Configure the make file for MacPorts (Thanks Clemens)
## Compile MacPorts
## Install MacPorts
sudo make install
## Fix your path (Thanks Peter)
echo 'export PATH=/opt/local/bin:/opt/local/sbin:$PATH' >> ~/.profile
## Update your ports
sudo port -dv selfupdate
- Re-install your ports.
- Post nice comments. 🙂
UPDATE: 2013-10-23 – I really appreciate the feedback I’ve been getting on this page. If the steps above don’t work perfectly for you, please check the comments below.
UPDATE 2: 2013-10-23 – My apologies to everyone for the site slowness and instability earlier. This was a new VM and I hadn’t optimized my Apache config. I was caught a little off-guard by the huge increase in traffic. 🙂
UPDATE 3: 2013-10-24 – Thanks to all of the wonderful contributors to this thread, there are new, improved and simplified instructions. The current instructions have been tested in a brand new Mavericks VM, but should also work with systems that have previous MacPorts installs. If you have any problems, please leave me feedback and I’ll try to help.