Ticket Options
Question Details
TICKET ARCHIVE -> Screensaver Crash 10.4
brunocoon - Sep 23, 2005 - 1:02 pm
Hi,
When I open my Screensaver pref frame it crashes. I have tried it in two different users with the same result. OSX continues to work but after a few minutes the screen saver takes over, sleeps the computer and I can't wake it up.
Here is the first part of the Crash log.
Thanks for your help,
Bruno Coon
-----
Date/Time: 2005-09-23 09:54:38.178 -0700
OS Version: 10.4.2 (Build 8C46)
Report Version: 3
Command: System Preferences
Path: /Applications/System Preferences.app/Contents/MacOS/System Preferences
Parent: WindowServer [69]
Version: 3.1 (3.1)
Build Version: 19
Project Name: SystemPrefsApp
Source Version: 1260000
PID: 266
Thread: 0
Application Specific Information:
Desktop &
Screen Saver v.1.3 (com.apple.preference.desktopscreeneffect)|ScreenSaver|loading|Flurry| Flurry
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x4334334e
Thread 0 Crashed:
0 libobjc.A.dylib 0x909ad100 objc_msgSend + 32
1 com.apple.Flurry 0x06c63654 dyld_stub_glGetError + 113612844
2 com.apple.ScreenSaver 0x9a377b28 -[ScreenSaverModules loadModuleWithPath:frame:isPreview:] + 732
3 com.apple.ScreenSaver 0x9a378798 -[ScreenSaverModules loadModuleWithName:frame:isPreview:] + 76
4 ...pscreeneffect.screeneffects 0x05e9d2f8 dyld_stub_NSIsSymbolNameDefined + 99178332
5 ...pscreeneffect.screeneffects 0x05e9ce74 dyld_stub_NSIsSymbolNameDefined + 99177176
6 com.apple.Foundation 0x9288d998 __NSFireDelayedPerform + 304
7 com.apple.CoreFoundation 0x9075ed10 __CFRunLoopDoTimer + 184
8 com.apple.CoreFoundation 0x9074b688 __CFRunLoopRun + 1680
9 com.apple.CoreFoundation 0x9074ac3c CFRunLoopRunSpecific + 268
10 com.apple.HIToolbox 0x93129ac0 RunCurrentEventLoopInMode + 264
11 com.apple.HIToolbox 0x93129154 ReceiveNextEventCommon + 380
12 com.apple.HIToolbox 0x93128fc0 BlockUntilNextEventMatchingListInMode + 96
13 com.apple.AppKit 0x93603e44 _DPSNextEvent + 384
14 com.apple.AppKit 0x93603b08 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
15 com.apple.AppKit 0x9360006c -[NSApplication run] + 472
16 com.apple.AppKit 0x936f08bc NSApplicationMain + 452
17 com.apple.systempreferences 0x00002da8 0x1000 + 7592
18 com.apple.systempreferences 0x0000a3fc 0x1000 + 37884
When I open my Screensaver pref frame it crashes. I have tried it in two different users with the same result. OSX continues to work but after a few minutes the screen saver takes over, sleeps the computer and I can't wake it up.
Here is the first part of the Crash log.
Thanks for your help,
Bruno Coon
-----
Date/Time: 2005-09-23 09:54:38.178 -0700
OS Version: 10.4.2 (Build 8C46)
Report Version: 3
Command: System Preferences
Path: /Applications/System Preferences.app/Contents/MacOS/System Preferences
Parent: WindowServer [69]
Version: 3.1 (3.1)
Build Version: 19
Project Name: SystemPrefsApp
Source Version: 1260000
PID: 266
Thread: 0
Application Specific Information:
Desktop &
Screen Saver v.1.3 (com.apple.preference.desktopscreeneffect)|ScreenSaver|loading|Flurry| Flurry
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x4334334e
Thread 0 Crashed:
0 libobjc.A.dylib 0x909ad100 objc_msgSend + 32
1 com.apple.Flurry 0x06c63654 dyld_stub_glGetError + 113612844
2 com.apple.ScreenSaver 0x9a377b28 -[ScreenSaverModules loadModuleWithPath:frame:isPreview:] + 732
3 com.apple.ScreenSaver 0x9a378798 -[ScreenSaverModules loadModuleWithName:frame:isPreview:] + 76
4 ...pscreeneffect.screeneffects 0x05e9d2f8 dyld_stub_NSIsSymbolNameDefined + 99178332
5 ...pscreeneffect.screeneffects 0x05e9ce74 dyld_stub_NSIsSymbolNameDefined + 99177176
6 com.apple.Foundation 0x9288d998 __NSFireDelayedPerform + 304
7 com.apple.CoreFoundation 0x9075ed10 __CFRunLoopDoTimer + 184
8 com.apple.CoreFoundation 0x9074b688 __CFRunLoopRun + 1680
9 com.apple.CoreFoundation 0x9074ac3c CFRunLoopRunSpecific + 268
10 com.apple.HIToolbox 0x93129ac0 RunCurrentEventLoopInMode + 264
11 com.apple.HIToolbox 0x93129154 ReceiveNextEventCommon + 380
12 com.apple.HIToolbox 0x93128fc0 BlockUntilNextEventMatchingListInMode + 96
13 com.apple.AppKit 0x93603e44 _DPSNextEvent + 384
14 com.apple.AppKit 0x93603b08 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
15 com.apple.AppKit 0x9360006c -[NSApplication run] + 472
16 com.apple.AppKit 0x936f08bc NSApplicationMain + 452
17 com.apple.systempreferences 0x00002da8 0x1000 + 7592
18 com.apple.systempreferences 0x0000a3fc 0x1000 + 37884
philippe99 - Sep 24, 2005 - 11:30 am
Bruno, welcome to macosx.com
Do you recently add extra ram ?
Are you in 10.4.1 or 10.4.2 ?
---
Otherwise, I would try the basic maintenance tips
(1) Could you try to repair permissions
(must be admin)
Launch Applications/Utilities/DiskUtility
On the left pane, select the drive
On the right, select the First Aid (or SOS) tab
Then click on repair permissions and let run; don not worry about messages like " new permissions...."
Quit DiskUtility
Shutdown and reboot
(2) could also download Macjanitor
http://personalpages.tds.net/~brian_...acjanitor.html
and use it to run the maintenance scripts
The maintenance scripts are Unix scripts which are automatically ran on your
Mac between 02Am and 04 am..if your Mac is on at this moment.
I can advice you to run, through Macjanitor, the daily script each day, the week script each week, ..and so on
(3) Could you also download Onyx
http://www.titanium.free.fr/pgs/english.html
and use it to clean the caches.
---
Then, repairing the system through the fsck Unix command
To run fsck, you first need to start up your Mac in single-user mode. Here's how:
1. Restart your Mac.
2. Immediately press and hold the Command and "S" keys.
You'll see a bunch of text begin scrolling on your screen. In a few more seconds, you'll see the Unix command line prompt (#).
You're now in single-user mode.
Now that you're at the # prompt, here's how to run fsck:
1. Type: "fsck -y" (that's fsck-space-minus-y).
If the 1st pass says that nothing has to be repaired, try "fsck -fy"
Option "-y" forces a "yes" response to every question of the system, which is very important because answering "no" to a fsck question will stop the process !
Option "-f" forces fsck to chack a system that this command seems to have find "clean"
2. Press Return.
The fsck utility will blast some text onto your screen. If there's damage to your disk, you'll see a message that says:
***** FILE SYSTEM WAS MODIFIED *****
If you see this message--and this is extremely important-- repeat running fsck. It is normal to have to run fsck more than once -- the first run's repairs often uncover additional problems..
When fsck finally reports that no problems were found, and the # prompt reappears:
3. Type: "reboot" to restart,
or type "exit" to start up without rebooting.
4. Press Return.
Your Mac should proceed to start up normally to the login window or the Finder.
Post back your results
Regards
Philippe
Do you recently add extra ram ?
Are you in 10.4.1 or 10.4.2 ?
---
Otherwise, I would try the basic maintenance tips
(1) Could you try to repair permissions
(must be admin)
Launch Applications/Utilities/DiskUtility
On the left pane, select the drive
On the right, select the First Aid (or SOS) tab
Then click on repair permissions and let run; don not worry about messages like " new permissions...."
Quit DiskUtility
Shutdown and reboot
(2) could also download Macjanitor
http://personalpages.tds.net/~brian_...acjanitor.html
and use it to run the maintenance scripts
The maintenance scripts are Unix scripts which are automatically ran on your
Mac between 02Am and 04 am..if your Mac is on at this moment.
I can advice you to run, through Macjanitor, the daily script each day, the week script each week, ..and so on
(3) Could you also download Onyx
http://www.titanium.free.fr/pgs/english.html
and use it to clean the caches.
---
Then, repairing the system through the fsck Unix command
To run fsck, you first need to start up your Mac in single-user mode. Here's how:
1. Restart your Mac.
2. Immediately press and hold the Command and "S" keys.
You'll see a bunch of text begin scrolling on your screen. In a few more seconds, you'll see the Unix command line prompt (#).
You're now in single-user mode.
Now that you're at the # prompt, here's how to run fsck:
1. Type: "fsck -y" (that's fsck-space-minus-y).
If the 1st pass says that nothing has to be repaired, try "fsck -fy"
Option "-y" forces a "yes" response to every question of the system, which is very important because answering "no" to a fsck question will stop the process !
Option "-f" forces fsck to chack a system that this command seems to have find "clean"
2. Press Return.
The fsck utility will blast some text onto your screen. If there's damage to your disk, you'll see a message that says:
***** FILE SYSTEM WAS MODIFIED *****
If you see this message--and this is extremely important-- repeat running fsck. It is normal to have to run fsck more than once -- the first run's repairs often uncover additional problems..
When fsck finally reports that no problems were found, and the # prompt reappears:
3. Type: "reboot" to restart,
or type "exit" to start up without rebooting.
4. Press Return.
Your Mac should proceed to start up normally to the login window or the Finder.
Post back your results
Regards
Philippe
brunocoon - Sep 24, 2005 - 3:27 pm
Greetings Phillipe,
Thanks for taking the time to reply.
I tried repairing permissions but they were fine.
I tried fsck -fy several times and the report was always good.
I tried Onyx (and looked at Janitor but I actually do leave my machine on all the time so I didn't use that one.)
In any case after the above steps I tried opening screensaver and it crashed instantly.
When I run Onyx on the unix putil page, user prefs I get an Onyx alert "Error 1" When I dismiss that box it reports that the prefs are ok. What could that mean?
Bruno
Thanks for taking the time to reply.
I tried repairing permissions but they were fine.
I tried fsck -fy several times and the report was always good.
I tried Onyx (and looked at Janitor but I actually do leave my machine on all the time so I didn't use that one.)
In any case after the above steps I tried opening screensaver and it crashed instantly.
When I run Onyx on the unix putil page, user prefs I get an Onyx alert "Error 1" When I dismiss that box it reports that the prefs are ok. What could that mean?
Bruno
philippe99 - Sep 25, 2005 - 5:48 am
Well, I find any information on that Onyx error 1
May you think to install the 10.4.2 combo
http://www.apple.com/support/downloa...1042combo.html
over your existing 10.4.x and see if this help ?
In ~/Library (where ~represents your Home folder), do you have a ScreenSavers folder (i.e. specific screensavers you add to the machine) ?
If yes, could you move its content to a new folder you'll create on the Desktop for instance -well, for backuping purposes in case of-
So that this ScreenSavers folder is empty: test again
In ~/Library/Preferences/ByHost, do you have a "com.apple.screensaversxxxxx.plistt" file ('xxx' is a sequence of digits) ? If yes, move it to the Desktop and test again
Philippe
May you think to install the 10.4.2 combo
http://www.apple.com/support/downloa...1042combo.html
over your existing 10.4.x and see if this help ?
In ~/Library (where ~represents your Home folder), do you have a ScreenSavers folder (i.e. specific screensavers you add to the machine) ?
If yes, could you move its content to a new folder you'll create on the Desktop for instance -well, for backuping purposes in case of-
So that this ScreenSavers folder is empty: test again
In ~/Library/Preferences/ByHost, do you have a "com.apple.screensaversxxxxx.plistt" file ('xxx' is a sequence of digits) ? If yes, move it to the Desktop and test again
Philippe
brunocoon - Sep 25, 2005 - 12:59 pm
Hi again,
I tried the combo update. Same problem.
The screensaver pane crashes instantly.
The Desktop pictures pane works fine.
I tried moving the Screensaver Folder to the desktop. No change.
I tried to find the ByHost/com.apple.screensaverxxx file but it doesn't appear to be there.
The Preview window of the screensaver pane is displaying a black screen and I think I once tried to use a file I made from a DV QuickTime taht was a jpg of one frame of black. That source is gone but could there be an alias somewhere that the Preview is trying to link to? I tried searching for all image files and all alias files but nothing stood out or had been opened recently.
I hadn't used an aftermarket screensaver but I tried dl-ing a couple to see if they would install over whatever is screwing me up here.
That also failed.
Thanks again for your continued attempts to help me,
Bruno
I tried the combo update. Same problem.
The screensaver pane crashes instantly.
The Desktop pictures pane works fine.
I tried moving the Screensaver Folder to the desktop. No change.
I tried to find the ByHost/com.apple.screensaverxxx file but it doesn't appear to be there.
The Preview window of the screensaver pane is displaying a black screen and I think I once tried to use a file I made from a DV QuickTime taht was a jpg of one frame of black. That source is gone but could there be an alias somewhere that the Preview is trying to link to? I tried searching for all image files and all alias files but nothing stood out or had been opened recently.
I hadn't used an aftermarket screensaver but I tried dl-ing a couple to see if they would install over whatever is screwing me up here.
That also failed.
Thanks again for your continued attempts to help me,
Bruno
philippe99 - Sep 25, 2005 - 1:25 pm
Bruno,
seeing
0 libobjc.A.dylib 0x909ad100 objc_msgSend + 32
1 com.apple.Flurry 0x06c63654 dyld_stub_glGetError + 113612844
2
I think the Flurry screensaver is corrupted
The System screensavers are in
/System/Library/Screensavers where the is the name of the hard drive
Try to move (surely the system will ask you for the admin password) Flurry out of this folder
Philippe
seeing
0 libobjc.A.dylib 0x909ad100 objc_msgSend + 32
1 com.apple.Flurry 0x06c63654 dyld_stub_glGetError + 113612844
2
I think the Flurry screensaver is corrupted
The System screensavers are in
Try to move (surely the system will ask you for the admin password) Flurry out of this folder
Philippe
brunocoon - Sep 25, 2005 - 1:33 pm
You did it.
Congratulations and my deepest heartfelt thanks.
CCan I do you a favor somehow?
Bruno
Congratulations and my deepest heartfelt thanks.
CCan I do you a favor somehow?
Bruno
philippe99 - Sep 25, 2005 - 1:58 pm
Happy we both find a issue to your problem Bruno.
> CCan I do you a favor somehow?
Well, I'm a volunteer on this site. I help people because a time ago, someone helped me when I was in trouble.
In my professionnal job I'm a helpdesk man (in the engineering field), so helping someone, perhaps at the opposite of the earth, is my second nature.
I'm very happy by the sole fact to receive a feedback from the client: I know that he can use his tool, I know that my idea, combined with his way of working, has succeed... so that I will be able to help another guy with the same issue.
Just speak about us around you and why not, one day, perhaps do you feel ready for helping other people and joigning us ;-)
Best regards from (a rainy) Belgium
Philippe
> CCan I do you a favor somehow?
Well, I'm a volunteer on this site. I help people because a time ago, someone helped me when I was in trouble.
In my professionnal job I'm a helpdesk man (in the engineering field), so helping someone, perhaps at the opposite of the earth, is my second nature.
I'm very happy by the sole fact to receive a feedback from the client: I know that he can use his tool, I know that my idea, combined with his way of working, has succeed... so that I will be able to help another guy with the same issue.
Just speak about us around you and why not, one day, perhaps do you feel ready for helping other people and joigning us ;-)
Best regards from (a rainy) Belgium
Philippe
brunocoon - Sep 25, 2005 - 2:11 pm
I shall and again many thanks from Los Angeles (or at least from me)
Bruno
>Best regards from (a rainy) Belgium
>Philippe
Bruno
>Best regards from (a rainy) Belgium
>Philippe
IF THIS IS YOUR QUESTION AND YOU WISH TO RESPOND, LOGIN HERE FIRST.
