Skip navigation

Desktop Flashing, Dock Lowers

764 Views 8 Replies Latest reply: Nov 13, 2012 2:30 PM by peterfromnorwood RSS
Torn-Barb Calculating status...
Currently Being Moderated
Oct 6, 2012 7:08 AM

This sounds weird but need some help from the pros out there.

 

I'm not sure what's going on but my screnn flashes and the dock disapears then comes back and all is right.  Frequency is about every 2-3 minutes.  I'm farely profienct at Unix based systems and Apple products in general most things i can fix so here is what I've done in the last 12hrs before it began:

 

I did a typical software update and it was only iTunes, OS X update.  I began some research on if I should upgrade from Lion to ML and found that if it's not for me downgrade by using my bootable image I have of Lion.  I found my image and put it on my desktop then doubleclicked it to make sure the file is still good.  I woke up this morning and the flashing began.  I've rebooted twice to 'kill' any processes which my be causing the issue.  So far no luck.

 

Few questions:

 

1.) Anyone every have this problem?

2.) If I restore from time machine from yesterdays backup will I lose a few iTunes purchases I just did this morning?

 

Any help is appreciated....

 

System Info:

 

OS X - 10.7.5

 

Logs from about an hour ago:

 

0xffffff802fc62648.  dropping the event.

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unable to get path for vp 0xffffff802fc62458 (SnowLeopard_10_6_6.mom; ret 22; type 2)

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802fc62458.  dropping the event.

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unable to get path for vp 0xffffff802fc62078 (PkgInfo; ret 22; type 2)

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802fc62078.  dropping the event.

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unable to get path for vp 0xffffff802fc60268 (iCalExternalSyncConduit.plist; ret 22; type 2)

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802fc60268.  dropping the event.

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unable to get path for vp 0xffffff802fc5f3e0 (timezone.plist; ret 22; type 2)

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802fc5f3e0.  dropping the event.

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unable to get path for vp 0xffffff802fc6bf00 (Carbon; ret 22; type 2)

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802fc6bf00.  dropping the event.

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unable to get path for vp 0xffffff802fc6a3e0 (columnResizer_1only_.png; ret 22; type 2)

2012-10-06 08:37:12 -0500 kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802fc6a3e0.  dropping the event.

2012-10-06 08:37:13 -0500 kernel[0]: add_fsevent: unable to get path for vp 0xffffff802fc6de08 (Extras2.rsrc; ret 22; type 2)

2012-10-06 08:37:13 -0500 kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802fc6de08.  dropping the event.

2012-10-06 08:37:13 -0500 kernel[0]: add_fsevent: unable to get path for vp 0xffffff802fc6d930 (HIToolbox.rsrc; ret 22; type 2)

2012-10-06 08:37:13 -0500 kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802fc6d930.  dropping the event.

2012-10-06 08:37:13 -0500 kernel[0]: add_fsevent: unable to get path for vp 0xffffff802fc6d648 (Info.plist; ret 22; type 2)

2012-10-06 08:37:13 -0500 kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802fc6d648.  dropping the event.

2012-10-06 08:37:13 -0500 kernel[0]: add_fsevent: unable to get path for vp 0xffffff802fc6d078 (popupArrows_black_1only_.png; ret 22; type 2)

  • Linc Davis Level 10 Level 10 (107,920 points)
    Currently Being Moderated
    Oct 6, 2012 10:30 AM (in response to Torn-Barb)

    Please read this whole message before doing anything.

     

    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

     

    The purpose of this test is to determine whether your problem is caused by third-party system modifications that load automatically at startup or login.

     

    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:

     

    1. Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
    2. When you see the gray Apple logo, release the shift key.
    3. If you are prompted to log in, type your password, and then hold down the shift key again as you click  Log in.

     

    *Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.

     

    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including sound and wireless networking on certain Macs.

     

    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

     

    Test while in safe mode. Same problem?

     

    After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Linc Davis Level 10 Level 10 (107,920 points)
    Currently Being Moderated
    Oct 6, 2012 6:07 PM (in response to Torn-Barb)

    The highlighted message says that you have an outdated version of an iTunes visualizer. That's not so important in itself, but since it's a built-in system component, you may have other system corruption. More to the point, the Dock is crashing. Please post the crash report.

  • peterfromnorwood Calculating status...
    Currently Being Moderated
    Nov 13, 2012 2:30 PM (in response to Torn-Barb)

    This solved my problem! It was the dock visualizer.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.