CreativePro Forum

Return to Member Forum

• Author
  Posts
• • June 14, 2010 at 1:13 pm #56038
    Philip Brandes

    Member

    Has anyone run across this issue? Control-click or right-click on a placed image causes InDesign to freeze before the contextual menu appears (spinning beach ball on a Mac).

    It first appeared in ID CS4 and continues in CS5. (CS3 has always been fine). There have been several online posts about it on various sites since CS4 release, but never a solution that worked (except not to use contextual menus on placed graphics). Also, scrolling through the Edit Menu with an image selected will cause the same freeze when passing the Edit With… command.

    The Links plug-in is definitely involved, because removing/disabling it from loading eliminates the problem. But obviously that introduces other compromises.

    It doesn't appear to be a bug per se, as the problem does not appear on a clean OS with just CS5 installed, rather it seems to be a conflict with something else…so, I'm posting this in case anyone has actually encountered and isolated the problem.

    Any info that might help avoid a complete rebuild/reinstall of my systems and all software would be much appreciated.

    Thanks in advance,

    Philip

  • June 14, 2010 at 4:14 pm #56039
    Anne-Marie Concepcion

    Member

    I would try rebuilding preferences, and also repairing permissions on your OS X (via Utilities > Disk Repair).

    It just sounds like InDesign doesn't know which app should open which image type. Since it pulls that from your computer's OS, solving it may require work on both ends.

    FWIW I have not seen this same issue on my Macs/PCs.

    AM

  • June 14, 2010 at 7:32 pm #56042
    Philip Brandes

    Member

    Thanks AM, believe me I have tried all the standard troubleshooting techniques, rebuilt InDesign prefs, repaired permissions, booted in Safe mode, created a new clean user account, zapped PRAM, etc. Nothing has worked. I tied it to the Links Plug-in by the venerable process of launching with half of the plug-ins removed, then testing by halves until I isolated it to that one plug-in. I realize this is not a typical problem, but as I said I have found a few online posts from others who have run across it so I know I'm not the only one. I was just hoping that someone who has solved it might see this and post a solution.

• Author
  Posts