![]() ![]() Open System Preferences, navigate to the Language & Text menu, then over to the Text tab. The good news is twofold: You probably don’t use or come across file URLs very much, and if you do - or are now paranoid about them - there is a fix. It won’t corrupt your HDD or SSD, nor will it cause things inside your Mac to heat up until they melt, causing a chain reaction that explodes your battery and sets your desk on fire. The bug will crash the running app, but the worst of the effects will be losing any unsaved data and having to restart (though Mountain Lion does have a resume feature). The bad news is that the bug is fairly prevalent, and affects just about any app that uses a data detector, which is most major OS X apps. When the verification process checks to see if the access command is legitimate - rather than improperly identified - it cannot distinguish between the uppercase “F” and lowercase “f,” crashing the app when the uppercase letter is used. The problem isn’t that any given affected app can’t handle attempting to access the local file, but that the detector has an issue with verifying that the command is actually a proper one. Like the command knows to navigate to a web page, the file:/// command attempts to access a file from within the computer that issued the command. These data detectors notice URLs, making standard links clickable upon detection. For example, you might receive an email with a date and location, and can then automatically add it to your calendar. This is due to data detectors, a facet of recent Mountain Lion updates that allows OS X to detect certain types of data, and react accordingly. With a simple text command, File:/// (without the quotation marks and with a capital F), that can be entered into just about any app that uses OS X’s standard text-input methods (web forms, TextEdit, etc.), the app will crash. Remember back in the early days of the internet when you could spin your friend’s floppy drive through a remote AIM command? Well, now you can do something similar (but more annoying) to yourself if you’re running Mountain Lion. Case in point: An eight-character URL detection flaw that easily crashes Mountain Lion apps. However, as Macs became more prominent, things began to just work a little less. Terms of use.įor the longest time, one of Apple’s most prominent slogans for OS X was “It just works,” which was actually true to some degree, once upon a time. If this is the normal behavior, I will turn off Deep Sleep since the Mac takes less time to sleep with it off.This site may earn affiliate commissions from the links on this page. Is this normal or should it happen like in Snow Leopard? Now when the battery dies, the computer restarts: I need to put my password and the programs open again but some of them lose the previous state (like VLC, Chrome has the "restore" option, etc.) it is exactly like a restart with the option "Reopen windows when logging back in" selected. ![]() What is happening to me is that, when I put my Mac to sleep and the battery dies, it does not restore the state like a normal sleep that it did when I was on Snow Leopard. ![]() I'm having an issue on my Mac since I installed Lion and now Mountain Lion (I thought that the Lion problem could be because I've put an SSD in my Mac and did not make a fresh install but a carbon copy to the new disk, but it still happens with Mountain Lion with a format/fresh install).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |