The last few days I am under a spell of bad luck: a near the elbow left-arm fracture, an old spine hernia that came back with a vengeance, confining me to bed the past two days, and, today, a Macbook Air that refuses make a sound while it won’t let me end a dialog.
Since the health of the body is less important than the health of the
mind Mac, I will skip the first and focus on the second 🙂
I have a 4,5 year Mac book Air (first generation), with an 80Gb disk. I have managed to keep upgrading up to Snow Leopard and then stopped. I have decided that my next upgrade will be a new Mac book, not a new OSX for the current one.
In the short (or long, depending on the perspective) life of this machine I have experienced two serious problems, both taken care by Apple Support.
Before turning to apple support for this one too, I want to describe it here, hoping that someone might stumble on it and offer a solution that I haven’t already found (i.e. tried, and rejected) googling for an answer.
The sound problem looks like a hardware one. At least, this was my first impression since input and output devices ceased to show up in the Sound Settings in System Preferences.
The first search though, revealed that this is an all too common Mac problem, highly correlated to Air’s and Lions. So with an Air and no Lion I have a 50% chance of a software problem.
The program I use most frequently (next to Chrome) is Coda, since I am doing most of my professional and personal work with it. But today it let me down too, although I don’t think it is strictly a Coda issue, as I noticed the same behavior with a couple of other programs too, namely Mail and SourceTree, but since I do not use them often I did not pay attention.
So what is this problem? Every time I attempt to open Coda I get stuck with the dialog below. I cannot close it, press a button, or make it progress. It stays there eternally.
What the dialog says is true. I indeed got stuck saving a remote file, that forced to quit coda, and since then…
My thought was that if I cleaned the local copies the dialog would disappear.
I tried to clear the cache but had problem finding it.
I deleted the Cache.db file in ~/Library/Caches/com.panic.Coda and all the entries in ~/Library/Coda/ (which look unrelated, but did it nevertheless). Then I looked at ~/Library/Application Support/Coda/Logs but the folder was empty.
In short, I did not find the cached remote files.
As a last resort, I also attempted to reinstall Coda. I got exactly the same result.
The funny thing is that if I click on a document that normally opens with Coda, the document opens nicely but then the accursed dialog kicks in.
So here I stand, or, rather, I lie, with no other solution left only than to beg you, kind reader, for one, before I make apple support richer.
I managed to get rid of the annoying dialog by cleaning some cache files in /Library/Caches. More specifically, after cleaning blindly all the cache files and folders that had a date close to yesterday, I opened Coda, saw the dialog again but this time clicking on cancel actually worked. Then, it asked me for a key, as I had reinstalled it and after putting the original purchase key, the confirmation dialog got stuck again. This time I knew where to look and it appeared that the only newly created cache file was /Library/Caches/com.apple.DiagnosticReporting.Networks.plist. I deleted it again, reopened Coda, repeated the above steps but this time, after entering the license key, the confirmation dialog worked. Of course all my setting were gone with the cache cleaning and reinstallation which is already a loss. But, at least I have Coda working.
Now, the property list file mentioned above, did not appear to have anything special inside. As a matter of fact, the one I initially deleted and the new one generated were identical. So, I cannot tell why it helped.
It took me sometime to make the connection: the two issues are related. In a very simple and stupid way: the dialogs get stuck as they attempt to play a sound. And since the sound system is dead, the dialog hangs up waiting. So, what I did, was disable the interface sound effects and, voila, dialogs started behaving.