Bug: Mac OS X 10.7.3 and QuarkXPress
There is a problem with recent versions of QuarkXPress and Mac OS X 10.7.3. Quark recommends NOT updating to 10.7.3 until they can work out a solution with Apple.
The problem is that after upgrading to Mac OS X 10.7.3, some icons in QuarkXPress palettes disappear. One workaround that has helped some users is to change Quark’s preferences so that the XTensions Manager always appears when QuarkXPress launches. Here’s where to do that:
After re-launching QuarkXPress, most or all of the icons should reappear.
To prevent the reoccurence of this issue, launch Disk Utility (in Applications/Utilities), select your hard disk, and click Repair Disk Permissions.
But the best approach is to NOT upgrade to 10.7.3 until Quark issues a fix.
To follow the ongoing discussion, see Quark’s forum thread at http://forums.quark.com/t/27664.aspx
Jay Nelson is the editorial director of PlanetQuark.com, and the editor and publisher of Design Tools Monthly. He’s also the author of the QuarkXPress 8 and QuarkXPress 7 training titles at Lynda.com, as well as the training videos Quark includes in the box with QuarkXPress 7 . In addition, Jay writes regularly for Macworld and Photoshop User magazines and speaks at industry events.
Hi. I’ve reinstalled Lion on my iMac 27 last week and, of course, I’ve the same problem with Quark XPress 9.2. But after that I’ve installed the last Flash plug-in update and now everything work fine. Not sure if this can be a solution, but I hope that can help someone :)
Lot of compliments for your work :)
There are many more things that don’t work.
Some meny items are invisible and it’s impoosible to create EPS-files.
come on… hurry up :)
Well, at least we’ve learned a lesson, “don’t be the guiney pig having your software up-to-date” :(
Play safe, let someone else lead …..
Doesn’t help if you’re buying a new mac though – it comes preinstalled with 10.7.3? Now what?
Danny: Yeah, that’s always the challenge. In that case you’ll have to live with the XTensions Manager workaround until Quark and Apple fix the problem. That really sucks.
Upgraded to Quark 9.2 to better run with Lion. What a mistake. Things were much more stable with Quark 8 running on Lion. 9.2 has been nothing but a headache. What was I thinking!?
Ugh… Need a headache? Fire up Quark.
This problem is fixed, please download and install QuarkXPress 9.2.1, released two weeks ago:
http://www.quark.com/support/downloads/Details.aspx?fid=225
Bonjour,
je signale un bug concernant la police zapf dingbats de l’os X 10.7.3 qui fait planter xpress au démarrage.
Comment y remédier ? remplacer la polices par la même d’un précédent système avant Lion.
I updated to 9.2.1 even though I use MacOS 10.6.8, on the general theory that it’s always good to update. Also I was having trouble with Sonar Bookend Fnote Xtension and I hoped the new Quark would run smoother with that, but quite the contrary. Quark 9.2.1 seems less friendly to Fnote, but worse than that is that after less than an hour of working on a document, the page you’re working on stops showing any responses on the screen. You can go to another page and come back and see that you have actually done something with your key commands, but that’s no good — the only solution is to save, quit quark, and re-open the software. Anybody else finding this? Somewhere I saw “Please note that these UpDate is only for Mac OS X Lion 10.7.3 Users”. Do I have to get Lion for this update to work?
@Matthias: That’s great that 9.2.1 was released to fix this issue, but what about a fix for 8.5.1 running on Lion? We have 30 users on Quark 8 and have started upgrading to hardware that is pre-installed with 10.7.3. Given that Quark 8 was still ship[ping after the release of 10.7, it seems reasonable that a compatibility fix should have been offered. Upgrading to Quark 9 for that many users is not a “fix” as it’s not in the budget this year. But this glitch with the pallets is untenable… your actions (or lack thereof) are actually forcing me to cave in and switch to InDesign (which we also already own). I am once again disappointed in your lack of support for your existing user base. Sadly, it looks like for the first time since Quark 3.0 – could it really be 21 years? – I will no longer be able to support Quark personally or professionally.