Tag Info

Hot answers tagged

19

It's a bug in 10.8.1 and 10.8.2 only. The workaround for this pesky bug is to disable two items in Language & Text Preference Pane in System Preferences on affected versions of Mountain Lion: Select (click) on Text in the middle towards the top of the window deselect (uncheck) "Correct spelling automatically" deselect (uncheck) "Use symbol and text ...


17

Crash Reports are good for finding out what happened to the program and depending on the circumstances possibly fixing them (eg. Final Cut crashes trying to use more than 2.5GB of memory - close some projects). They're most important to the developer so be sure to pass them on as if the issue is a bug. A related question on SuperUser dealing with kernel ...


13

bmike has the workaround, I'll provide the "why": According to this article from TheNextWeb, a feature called Data Detectors, which scans text for meaningful formats (dates, locations...) also looks for file URLs. It does this by looking for "file://", case-insensitive. However, later in the procedure, it asserts that the string should start with "file://" ...


10

You can enable SSH from the Terminal with: sudo launchctl load -w /System/Library/LaunchDaemons/ssh.plist (note that you need to run this as an admin, and it'll ask for your admin password, which won't echo as you type.)


10

Repeated kernel panics occurring without third party drivers can only be caused by a few things: 1) A peripheral device 2) A bad OSX image or bug in OSX itself 3) A hardware problem In your case, it is unfortunately (3): System model name: MacBookPro6,2 The kernel panic indicates that your GPU is failing. This is a known issue for your machine. ...


8

Firstly, I would check to see if the issue is systemic, or related to the user account. Create a new blank user account, and then see if you can remotely log into the computer using that ID. Then, if that works, try to su to your existing ID. Also, try a start in single user mode. See what works there. After that, try safe mode. Interestingly, using ...


8

From the macrumors forums you can hold shift when you launch a program to launch it without the resume previous window functionality. Alternatively, for those who want some resume functionality and don't want to globally disable it, you can hold Shift when you launch an application to bypass resume and start that app fresh. If that doesnt work you ...


7

You can boot into single user mode by holding Command + s at startup. Single user mode starts you directly at the console, bypassing core Mac OS X startup processes. You should be able to remove or alter the offending file from there.


7

Just a quick note to say that I eventually stopped the crashing by manually copying these two files from another OS X machine and then manually starting the nlcd daemon (if you don't have another Mac, I posted my copies of those files here) Copied these files: /System/Library/LaunchDaemons/com.apple.NetworkLinkConditioner.plist /usr/libexec/nlcd Run these ...


6

Can you open the Console application (in the /Applications/Utilities/ folder) and see if anything is reported up to and during the application hangs? Are you actually getting a crash or just a hang? (A crash will display an "unexpectedly quit" dialog on its own (creating a .crash file) , whereas a hang will require you to explicitly force the application ...


6

Mac OS X Reference Library Technical Note TN2123 states: CrashReporter performs two useful actions: When a program crashes, CrashReporter will record a crash log (typically into ~/Library/Logs/CrashReporter/), and inform the user by logging a message to the system logging facility. In addition, if the program that crashed is running ...


6

Recently announced by Apple (Dec. 17, 2010), the iTunes Developer Guide [PDF] illustrates how a Mac App Store developer may receive crash log reports for their apps. This isn't true for apps downloaded outside of the Mac App Store, unless the developer has coded that functionality in manually.


6

I believe this is a bug in OS X 10.7. I also have a retina MacBook Pro. Mine is 2.6/16/512, and I noticed that there were 0 page outs but a very large swap file being created (mine was about 8 GB). Closing applications actively reduced the swap space being used. Again there were no page outs being recorded. I believe this has to do with the sleep image ...


5

Try rebooting the iPad to free up some memory. Hold the lock button until the "slide to power off" slider comes on, slide it, then turn the iPad back on.


5

Yes. You have enabled auditing somewhere along the line, being a wise person, but you have not trimmed the file, being a human, like I. Note the instant edit ;) man -k audit if you can get a shell will show you where you need to go ( look at them on the apple dev site ) i think here you want audit -e to get rid of your old audit files. From ...


5

Take it to Apple and ask them to fix it under warranty. If you have made a clean install, and can still demonstrate the problem, you almost certainly have some sort of hardware issue. If you did a reinstall, then added something that has a kext, that might be responsible, though, so in the (unlikely) event, reinstall, don't install that, and see if that ...


5

I find it easiest to use the settings app on iOS: General About Diagnostics & Usage Diagnostics & Usage Data scroll to the crash you care about and tap it select all, copy the text Now you can paste the report wherever you please. Email, Simplenote, notes, Evernote, or wherever else you like to store the text for submitting a bug with Apple. You ...


5

To repair the Open Directory authdata database: $ sudo launchctl unload /System/Library/LaunchDaemons/org.openldap.slapd.plist $ sudo db_recover -h /var/db/openldap/authdata/ Now slapd in tool mode outputs: $ sudo /usr/libexec/slapd -Tt bdb_db_open: database "dc=nl2,dc=probackup,dc=nl": unclean shutdown detected; attempting recovery. bdb_db_open: ...


5

Those log files are total benefit with no downside. Your phone is out of juice and will shut down anyway. The OS is logging the data so you can take action on it if you choose. They don't cause anything other than logging what led up to the low power condition. I watch my LowBatteryLog-YYYY-MM-DD-hhmmss.plist log files quite regularly to know when to seek ...


5

The log files that you've posted aren't providing much good information regarding the crashes. The best clue from the logs may be this line (which could be indicative of OpenGL graphics context problems): 9/10/13 10:42:57.764 AM SystemUIServer[271]: It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil. This is a ...


5

Why not just install the latest version of Xcode? Xcode 3.2 was originally released all the way back in 2009 and since it's a very technical product by nature, it's not really a surprise that it crashes on a OS that was released 5 years later. If you really, really need v. 3.2, I'd suggest looking into virtualization (Parallels Desktop or VMware Fusion are ...


5

I figured it out.. After looking more closely at the log and mulling over it for a moment I noticed in the log: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** setObjectForKey: object cannot be nil (key: serverName)' So I attempted to setup the account in Preferences>Internet Accounts again but this time, I started ...


4

I have several Machines which run MS Office 2011 perfectly fine with Mavericks. I would suspect some corrupt settings or cache is the reason for your problem. Try the following: try moving the Folder "~/Documents/Microsoft-User Data" somewhere else (f.e. the Desktop) and try starting Word try moving the folder "~/Library/Application ...


4

It could be a low memory issue. iOS is supposed to manage memory automatically, but I've found that it's not always perfect. Try quitting every single app and restart the device (hold the power button down for several seconds, then slide to power off, then power on again) to see if that fixes it.


4

Jailbreaking is the process of hacking the code signing mechanism to allow unsigned code to run on the phone. There are multiple tools used for this and they vary between both model and iOS version. Unlocking is the process of hacking the 3G chip's baseband to allow SIM cards from other networks without an official unlock from the carrier. There's also an ...


4

Crash logs are safe to post in public. There is no identifying information about you in them. All of the random looking text you see are addresses of the various methods that get symbolicated by Xcode into method names. This lets the developers see the exact line of code that caused the problem. Also know, it is harder to symbolicate crash logs that have ...


4

Two possible remedies, and I'd try in this order. 1) Safe Boot, then reboot normally (Read about Safe boot mode in the Help menu) 2) Reset PRAM. This a software reset that I just tried yesterday to fix nuisance problems in 2 Macs that did not respond to a Safe boot. Crashes like you describe often indicate there is a software screw-up somewhere in the ...


4

After looking in /Library/Contextual Menu Items/ I noticed that even after uninstalling the app which I suspected was causing the problem, a plugin was still present. Deleting it has resolved the issue. The app in question was Antidote by Druide Software.


4

As the arstechnia link to ycombinator page states, it is a "bug inside Apples CoreText font rendering framework". This post on a Russian website drew attention to it: http://habrahabr.ru/post/191654/ (translated page here: ...


4

Xcode 3 shouldn't install on Mavericks, and if it does it definitely isn't supported by Apple. To avoid the login crash try entering your login credentials, and immediately after pressing return, hold down the shift key to prevent anything from loading. IF that doesn't stop the kernel panic, then you will need to wipe, reinstall, and resort from your Time ...



Only top voted, non community-wiki answers of a minimum length are eligible