Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > macOS > Important Crash Solution (Acrobat et al)

Important Crash Solution (Acrobat et al)
Thread Tools
rplotkin
Junior Member
Join Date: Nov 1999
Status: Offline
Reply With Quote
Oct 18, 2002, 05:58 PM
 
I post this solution to a recurrent application crashing problem that may be useful in many instances of troubleshooting. My particular experience was with Acrobat and Acrobat Reader, though this problem has apparently come up with Python installations as well. This is known as an "EXC_BAD_ACCESS" and "KERN_PROTECTION_FAILURE" error.

This problem is caused by a corruption of the a hidden preference file, called ".GlobalPreferences.plist", located in ~/Library/Preferences/.

To correct the error:
1) Log in as an Administrator.
2) Create a new user account, called NewUser.
[The name isn't important, because you're going to delete this account when we're done].
2b) If the affected user account is not an administrator account, go ahead and make it one. You can revoke this privilege later, but it will make things easier for now.
3) Log out, and log back in as NewUser.
[This will initialize the account and create undamaged preferences.]
4) Log back out, and log in again as the user affected by the crashed (who, according to step 2b, is an Administrator).
5) Launch the "Terminal" application, located in /Applications/Utilities/
6) Type the following command (for all of the following, copy and paste):
cd ~/Library/Preferences/
7) Type this command:
rm .GlobalPreferences.plist
8) Type this command:
sudo cp /Users/NewUser/Library/Preferences/.GlobalPreferences.plist .
[it will ask for an administrator password to allow you to log in as root for this action]
9) Type this command -- DON'T COPY-PASTE THIS ONE! YOU NEED TO PUT YOUR OWN USERNAME:
sudo chown USERNAME .GlobalPreferences.plist
10) Log out.
10b) If you enabled Admin access on an account that shouldn't have it, log back in as an Administrator and disable that Admin access.
11) Delete the NewUser account.
12) Log out, and log in to the affected acount.

Problem solved. Note that you must, for some reason, delete [rm] the corrupted Global file before putting an uncorrupted one [cp] in its place.

Best,
Richard
     
ctbritt
Forum Regular
Join Date: Aug 2002
Location: Beirut, Lebanon
Status: Offline
Reply With Quote
Oct 18, 2002, 07:01 PM
 
Couldn't you just rm the global preferences and log out and then log back in, letting the OS create a new file? Or does that not work...

best,
christopher
Christopher Allbritton
MacOS X 10.4.9, 2GB RAM, 15-in. 2.33 GHz MBP 2 CD
www.back-to-iraq.com
     
rplotkin  (op)
Junior Member
Join Date: Nov 1999
Status: Offline
Reply With Quote
Oct 19, 2002, 01:37 AM
 
Good question. In fact, no, it doesn't work. I think the OS auto-creates this file instantaneously, based on some temp file. So if you rm it, it just creates an identical file in its place, including the damaging instructions. You must replace it with a clean file, via the terminal, to succeed.

--Richard
     
CharlesS
Posting Junkie
Join Date: Dec 2000
Status: Offline
Reply With Quote
Oct 19, 2002, 04:49 AM
 
Originally posted by rplotkin:
Good question. In fact, no, it doesn't work. I think the OS auto-creates this file instantaneously, based on some temp file. So if you rm it, it just creates an identical file in its place, including the damaging instructions. You must replace it with a clean file, via the terminal, to succeed.

--Richard
Probably something just changed in the GlobalPreferences user default domain which caused it to write the domain in RAM to the file in your Preferences folder.

What happens if you rm the file when logged in as another user? I think that should cause it to just generate a new file.

Charles

Ticking sound coming from a .pkg package? Don't let the .bom go off! Inspect it first with Pacifist. Macworld - five mice!
     
rplotkin  (op)
Junior Member
Join Date: Nov 1999
Status: Offline
Reply With Quote
Oct 19, 2002, 11:23 AM
 
Hi Charles,

I didn't think to try that, but it certainly sounds like a good idea, and would be much simpler to do. And if it doesn't work, _then_ one can go through the replacement process.
     
ozeon
Fresh-Faced Recruit
Join Date: Dec 2002
Status: Offline
Reply With Quote
Dec 28, 2002, 10:43 AM
 
Richard, I was wondering if you found out if this works, regarding the corrupted GlobalPreferences.plist

1. What happens if you rm the file when logged in as another user? I think that should cause it to just generate a new file.


2. Or can the file be simply deleted in OS9?

Thanks,
Norm
     
Appleman
Mac Elite
Join Date: Feb 2001
Location: France
Status: Offline
Reply With Quote
Dec 28, 2002, 12:45 PM
 
Looks like my problem with iPhoto in this thread has the same. I'll try out your solution and will be back with the results.
     
Appleman
Mac Elite
Join Date: Feb 2001
Location: France
Status: Offline
Reply With Quote
Dec 28, 2002, 01:21 PM
 
I did exactly what you wrote. still have the same **** with iPhoto, see the Console log:

**********

Date/Time: 2002-12-26 21:07:16 +0100
OS Version: 10.2.3 (Build 6G30)
Host: Joris-van-t-Lands-Computer.local.

Command: iPhoto
PID: 541

Exception: EXC_BREAKPOINT (0x0006)
Code[0]: 0x00000001Code[1]: 0x90844988

Thread 0:
#0 0x90073c48 in mach_msg_trap
#1 0x90005f90 in mach_msg
#2 0x90148b10 in __CFRunLoopRun
#3 0x90180fe4 in CFRunLoopRunSpecific
#4 0x969a36a0 in RunCurrentEventLoopInMode
#5 0x969b34c8 in ReceiveNextEventCommon
#6 0x969da584 in BlockUntilNextEventMatchingListInMode
#7 0x9308d8ac in _DPSNextEvent
#8 0x9309fb04 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
#9 0x930b15e4 in -[NSApplication run]
#10 0x9315f6b8 in NSApplicationMain
#11 0x000048d4 in 0x48d4
#12 0x00004704 in 0x4704

Thread 1:
#0 0x9003eaa8 in semaphore_wait_signal_trap
#1 0x9003e8c4 in _pthread_cond_wait
#2 0x90824180 in -[NSConditionLock lockWhenCondition:]
#3 0x93081388 in -[NSUIHeartBeat _heartBeatThread:]
#4 0x9081cd38 in forkThreadForFunction
#5 0x90020d48 in _pthread_body

Thread 2 Crashed:
#0 0x90844988 in _NSRaiseError
#1 0x90844810 in +[NSException raise:format:]
#2 0x907e50b8 in -[NSCFDictionary setObject:forKey:]
#3 0x0004e3a8 in 0x4e3a8
#4 0x0004f380 in 0x4f380
#5 0x0004c7b8 in 0x4c7b8
#6 0x00019a80 in 0x19a80
#7 0x0001ad3c in 0x1ad3c
#8 0x0001bdcc in 0x1bdcc
#9 0x9081cd38 in forkThreadForFunction
#10 0x90020d48 in _pthread_body

Thread 3:
#0 0x90014d28 in syscall_thread_switch
#1 0x907f4304 in +[NSThread sleepUntilDate:]
#2 0x0000ee30 in 0xee30
#3 0x9081cd38 in forkThreadForFunction
#4 0x90020d48 in _pthread_body

Thread 4:
#0 0x90014d28 in syscall_thread_switch
#1 0x907f4304 in +[NSThread sleepUntilDate:]
#2 0x0000f760 in 0xf760
#3 0x9081cd38 in forkThreadForFunction
#4 0x90020d48 in _pthread_body

PPC Thread State:
srr0: 0x90844988 srr1: 0x0202f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x90844964 ctr: 0x907e4270 mq: 0x00000000
r0: 0x00000000 r1: 0xf002faa0 r2: 0x24000249 r3: 0xa07ed3b8
r4: 0x9068d51c r5: 0x20000000 r6: 0xf002f780 r7: 0x00000000
r8: 0x00128010 r9: 0xa07e0294 r10: 0x00000001 r11: 0x00000000
r12: 0x24000249 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x018e8a30 r19: 0x01f92920
r20: 0x01bbe270 r21: 0x00000016 r22: 0x02f81070 r23: 0x01bc1cc0
r24: 0x05e7cb40 r25: 0x0000001e r26: 0x041bd190 r27: 0x00000000
r28: 0x906d3918 r29: 0x041bd130 r30: 0x000cab74 r31: 0x908448a8

**********

Date/Time: 2002-12-26 21:12:36 +0100
OS Version: 10.2.3 (Build 6G30)
Host: Joris-van-t-Lands-Computer.local.

Command: iPhoto
PID: 545

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000020

Thread 0 Crashed:
#0 0x9068ba50 in objc_msgSend
#1 0x931c3c94 in runModalCleanup
#2 0x0007bc50 in 0x7bc50
#3 0x930f90e4 in -[NSApplication sendAction:to:from:]
#4 0x93119868 in -[NSControl sendAction:to:]
#5 0x9315dfac in -[NSCell _sendActionFrom:]
#6 0x930f2ad4 in -[NSCell trackMouse:inRect:ofView:untilMouseUp:]
#7 0x9315dbcc in -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:]
#8 0x9312d504 in -[NSControl mouseDown:]
#9 0x930c0888 in -[NSWindow sendEvent:]
#10 0x930a8788 in -[NSApplication sendEvent:]
#11 0x00070174 in 0x70174
#12 0x930b1608 in -[NSApplication run]
#13 0x9315f6b8 in NSApplicationMain
#14 0x000048d4 in 0x48d4
#15 0x00004704 in 0x4704

Thread 1:
#0 0x9003eaa8 in semaphore_wait_signal_trap
#1 0x9003e8c4 in _pthread_cond_wait
#2 0x90824180 in -[NSConditionLock lockWhenCondition:]
#3 0x93081388 in -[NSUIHeartBeat _heartBeatThread:]
#4 0x9081cd38 in forkThreadForFunction
#5 0x90020d48 in _pthread_body

PPC Thread State:
srr0: 0x9068ba50 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x20000000 lr: 0x931c3c94 ctr: 0x9068ba3c mq: 0x00000000
r0: 0x931c3c94 r1: 0xbfffebb0 r2: 0x24000280 r3: 0x03d5880b
r4: 0x933ffb48 r5: 0x01eb8c30 r6: 0x41a00000 r7: 0x00000002
r8: 0x00000002 r9: 0x00000001 r10: 0x00000001 r11: 0xa3072cf8
r12: 0x00000000 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0xa30726a8 r17: 0xa30a26a8 r18: 0xa30a26a8 r19: 0xa30a26a8
r20: 0x00000000 r21: 0xa30a26a8 r22: 0x00000000 r23: 0x01f41a10
r24: 0xa30a26a8 r25: 0x00000000 r26: 0x044ac7d0 r27: 0x044ac7d0
r28: 0x00000000 r29: 0xa3070084 r30: 0x04706fe0 r31: 0x931c3c64

**********

Date/Time: 2002-12-28 19:19:40 +0100
OS Version: 10.2.3 (Build 6G30)
Host: Joris-van-t-Lands-Computer.local.

Command: iPhoto
PID: 839

Exception: EXC_BREAKPOINT (0x0006)
Code[0]: 0x00000001Code[1]: 0x90844988

Thread 0:
#0 0x90073c48 in mach_msg_trap
#1 0x90005f90 in mach_msg
#2 0x90148b10 in __CFRunLoopRun
#3 0x90180fe4 in CFRunLoopRunSpecific
#4 0x969a36a0 in RunCurrentEventLoopInMode
#5 0x969b34c8 in ReceiveNextEventCommon
#6 0x969da584 in BlockUntilNextEventMatchingListInMode
#7 0x9308d8ac in _DPSNextEvent
#8 0x9309fb04 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
#9 0x930b15e4 in -[NSApplication run]
#10 0x9315f6b8 in NSApplicationMain
#11 0x000048d4 in 0x48d4
#12 0x00004704 in 0x4704

Thread 1:
#0 0x9003eaa8 in semaphore_wait_signal_trap
#1 0x9003e8c4 in _pthread_cond_wait
#2 0x90824180 in -[NSConditionLock lockWhenCondition:]
#3 0x93081388 in -[NSUIHeartBeat _heartBeatThread:]
#4 0x9081cd38 in forkThreadForFunction
#5 0x90020d48 in _pthread_body

Thread 2 Crashed:
#0 0x90844988 in _NSRaiseError
#1 0x90844810 in +[NSException raise:format:]
#2 0x907e50b8 in -[NSCFDictionary setObject:forKey:]
#3 0x0004e3a8 in 0x4e3a8
#4 0x0004f380 in 0x4f380
#5 0x0004c7b8 in 0x4c7b8
#6 0x00019a80 in 0x19a80
#7 0x0001ad3c in 0x1ad3c
#8 0x0001bdcc in 0x1bdcc
#9 0x9081cd38 in forkThreadForFunction
#10 0x90020d48 in _pthread_body

Thread 3:
#0 0x90014d28 in syscall_thread_switch
#1 0x907f4304 in +[NSThread sleepUntilDate:]
#2 0x0000ee30 in 0xee30
#3 0x9081cd38 in forkThreadForFunction
#4 0x90020d48 in _pthread_body

Thread 4:
#0 0x90014d28 in syscall_thread_switch
#1 0x907f4304 in +[NSThread sleepUntilDate:]
#2 0x0000f760 in 0xf760
#3 0x9081cd38 in forkThreadForFunction
#4 0x90020d48 in _pthread_body

PPC Thread State:
srr0: 0x90844988 srr1: 0x0202f030 vrsave: 0x00000000
xer: 0x20000000 lr: 0x90844964 ctr: 0x907e4270 mq: 0x00000000
r0: 0x00000000 r1: 0xf002faa0 r2: 0x24000249 r3: 0xa07ed3b8
r4: 0x9068d51c r5: 0x20000000 r6: 0xf002f780 r7: 0x20000000
r8: 0x00128010 r9: 0xa07e0294 r10: 0x00000001 r11: 0x00000000
r12: 0x24000249 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x018e1140 r19: 0x03f08840
r20: 0x03f088c0 r21: 0x00000017 r22: 0x057041f0 r23: 0x01c81490
r24: 0x0594e910 r25: 0x0000001e r26: 0x00152960 r27: 0x00000000
r28: 0x906d3918 r29: 0x01a7e810 r30: 0x000cab74 r31: 0x908448a8
     
rplotkin  (op)
Junior Member
Join Date: Nov 1999
Status: Offline
Reply With Quote
Dec 28, 2002, 02:15 PM
 
Hi Appleman,

Have you tried creating a new user and testing iPhoto with that user? Does the problem persist? If it does not (or does), let us know. try dumping all your preferences and replacing them with the system's default prefs, located in /Library/Preferences It's kind of drastic, but it could work. Be wary of losing registration info if you do this; some OS X programs (for some REALLY dumb reason) store their serials in a user's prefs.
     
Appleman
Mac Elite
Join Date: Feb 2001
Location: France
Status: Offline
Reply With Quote
Dec 28, 2002, 03:52 PM
 
When creating a new user as administator it does the same.
When creating a user without admin, it doesn't.



I would say that if I install OS X again (as I did) all prefs should be as new...

it worked for a while, but then it started to do the same buggy stuff
     
rplotkin  (op)
Junior Member
Join Date: Nov 1999
Status: Offline
Reply With Quote
Dec 28, 2002, 06:00 PM
 
Hi again Appleman,

Well, not that you need to be told this, but that is unbelievably bizarre. Two thoughts:
1) Re-installing OS X will NOT overwrite your preferences. So don't bother. The only way to do that would be to follow a procedure similar to the one documented above: Create an Admin user, log in as that user, sudo into root, cd into the affected user's ~/library/preferences folder, run "rm -R ." (erase all files in current directory), then copy all files from /Library/Preferences/ into that user's directory. IF one of those files in the default location has been corrupted, then re-installing OS X would fix them, and then rewriting the user's prefs would work.

2) Have you zapped the P-RAM? If not, reboot the computer and hold down <Command>-<Option>-P-R until you hear the startup sound...and let it start up about four times before you let go.

Sorry I can't be more help yet,
This is a weird problem, especially ocurring only in new Admin users, and not new regular users.

One last question: If you create a regular user, launch that user, start up iPhoto, log out, log in and enable that regular user as an Admin, then log back in to that regular --> Admin account, does iPhoto cease working then? Or is it only in an originally Admin account that it won't work?

--Richard
     
Appleman
Mac Elite
Join Date: Feb 2001
Location: France
Status: Offline
Reply With Quote
Dec 29, 2002, 04:47 PM
 
Originally posted by rplotkin:
Hi again Appleman,

Well, not that you need to be told this, but that is unbelievably bizarre. Two thoughts:
1) Re-installing OS X will NOT overwrite your preferences. So don't bother. The only way to do that would be to follow a procedure similar to the one documented above: Create an Admin user, log in as that user, sudo into root, cd into the affected user's ~/library/preferences folder, run "rm -R ." (erase all files in current directory), then copy all files from /Library/Preferences/ into that user's directory. IF one of those files in the default location has been corrupted, then re-installing OS X would fix them, and then rewriting the user's prefs would work.

2) Have you zapped the P-RAM? If not, reboot the computer and hold down <Command>-<Option>-P-R until you hear the startup sound...and let it start up about four times before you let go.

Sorry I can't be more help yet,
This is a weird problem, especially ocurring only in new Admin users, and not new regular users.

One last question: If you create a regular user, launch that user, start up iPhoto, log out, log in and enable that regular user as an Admin, then log back in to that regular --> Admin account, does iPhoto cease working then? Or is it only in an originally Admin account that it won't work?

--Richard

1. When first erasing the harddisk all prefs are gone of course, forgot to tell that. I did, and after a while the very same problem came back.

2. I hadn't zapped the PRAM, will do that after this message :-)
(silly, in OS 9 that would have been one of the first things to do actually...)
     
Appleman
Mac Elite
Join Date: Feb 2001
Location: France
Status: Offline
Reply With Quote
Dec 29, 2002, 05:02 PM
 
Originally posted by Appleman:
1. When first erasing the harddisk all prefs are gone of course, forgot to tell that. I did, and after a while the very same problem came back.

2. I hadn't zapped the PRAM, will do that after this message :-)
(silly, in OS 9 that would have been one of the first things to do actually...)
Doesn't matter: last imported photo's do not stay when quitting iPhoto. They do get in the iPhoto Folder though (in the Pictures Folder).

I'll send a feedback to Apple with the logs, maybe Uncle Steve can come up with a update next MacWorld :-)
     
ozeon
Fresh-Faced Recruit
Join Date: Dec 2002
Status: Offline
Reply With Quote
Dec 30, 2002, 04:10 AM
 
1. Would using Dragster to delete the GlobalPreferences.plist do the same thing as the Logon as other User technique?
Or would it just create another corrupted pref?

2. If I delete the GlobalPreferences.plist, exactly what info will be lost and have to be resurrected. It sounds like a fairly last resort and I was wondering what happens when I do this?

Thanks,
Norm
     
rplotkin  (op)
Junior Member
Join Date: Nov 1999
Status: Offline
Reply With Quote
Dec 30, 2002, 04:58 AM
 
Hi Ozeon,

In your response to your Dragster question: I don't know. I would recommend giving it a try, if you are uncomfortable with the command line. If it doesn't work, then you're stuck with the more difficult instruction set. If it does work, please post that it did on the forum.

As for what you lose when deleting the file: It's very much like deleting "Finder Prefs" in OS 9. You lose your time zone, and probably also your energy saver prefs. Maybe. Other than that, the file is there to preserve OS-level operations, and this is why it regenerates. So, in short, you should make a run through your prefs, but you won't lose anything important.

--Richard
     
   
Thread Tools
 
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Top
Privacy Policy
All times are GMT -4. The time now is 04:16 PM.
All contents of these forums © 1995-2015 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.8 © 2000-2015, Jelsoft Enterprises Ltd.,