Recently my Finder started crashing multiple times per day, so I opened up the Console application and looked for the crashlogs. Looks like Dropbox was the culprit. In each of the 14 Finder crashes I’ve had since November 4 2013, the following line appears in the crashing thread:
“This may have nothing to do with your Finder crashes, but do you have a Lion-compatible version of Dropbox installed?”
…which got me thinking. I’m running OS X 10.8.5. Looking at my Dropbox version (Menubar > Dropbox icon > Preferences > Account), I saw that my Dropbox version was 1.6.4 and that the software had no mechanism to autoupdate nor a way to “check for updates”.
So I checked Dropbox’s website, and lo-and-behold, the current version is 2.4.7, which I promptly installed. Hopefully this cures my woes!
So, I’ve moved in with my significant other (yay!), and part of that move is a reconfiguration of my office space. Part of this involves me examining things I’ve been holding onto for a while. Those things? Software packaging. Giant, shelf-space hogging, software packaging. Boxes, just filled with cardboard & plastic, so as to take up more space on retail shelves, so that they get noticed by consumers and picked up. I just recycled so much of that stuff.
Now that we’re in the age of electronic software distribution, that won’t be so much of a problem. That said, I couldn’t bear to part with my box for American McGee’s “Alice”, one of the first games I bought for the first computer I bought, all the way back in 2001. So there’s a part of me that regrets this loss of the physical manifestation of software, too. The future of software will be a colder place in that regard.
So, I’ve known for a long time that “undo” in the vi editor can be accomplished by pressing escape, then the “u” key. But how to “redo” eluded me this morning. I tried various things before resorting to a Google search: escape, “U” (capital “u”); escape, “r”, etc. Turns out it’s the Control-R. Duh.
The other half was figuring out what type of Chinese text encoding was being used in the source files. EditPad Pro for Windows was extremely helpful in this regard, as it allowed me to quickly preview what many different text encodings looked like. In the command line above, “GBK” is the source text encoding (one of several text encoding standards for Simplified Chinese).
It costs money, but BinaryMark’s Batch Encoding Converter for Windows would have also done the conversion work once I’d figured out the source text encoding was GBK. As it stands I used the “iconv” tool which is built into OS X.
This occurred mid-way through a photo import (happening at the same time as a sync operation via iTunes). Result was no photos imported (but they were all still on the phone, so nothing lost). The phone disappeared from iPhoto, but was still present in iTunes.
4/10/12 12:18:08.983 AM com.apple.launchd.peruser.501: ([0x0-0x3e13e1].com.apple.
PTPCamera) Job appears to have crashed: Illegal instruction: 4
Thought I’d post here in case anyone else has run into this issue.