Red Background Squares When printing from Acrobat 8.1.2 (Leopard)

We are 5 to use Acrobat Pro 8.1.2 in the office on Mac OS10.5. When we print to HP Laserjet from Acrobat, we get red square backgrounds on items in the page. When printed from Preview, or older Acrobat, this does not happen. HP does not have a clue.
Thanks for any suggestions.
Jonas

You can change the printer profile inside Print / Advanced / Output /
Colour Profile /
Jon

Similar Messages

Faded colors when printing from Acrobat - different than previous

Hi
I have read some threads about color fading when printing a PDF created in ID and printed from Acrobat. My problem is the same and I am also having the same problem with PDF's exported from Keynote (client created posters). It sounds like I should work with the PDF optimizer for the solution. Has anyone experienced the fading colors from anything other than ID or Quark made PDF's? Did the optimizer fix the problem? I find it frustrating that I can print directly from ID and not have a problem - why can't they all get along! ;0)
Using Acrobat 9, Keynote 09 and an Epson 9880 printer.
Thanks

RE: "You don't indicate what Xerox printers you have"
In my first post I named it, is that the information you need?
Docucolor 3535 using Splash 3535
That's interesting, so I have to find a way to turn off the printer's Color Management function? I mailed them, hope they can tell me how to do it easily. They usually just tell me to not use any profiles and so on, but that's the general rule in this area, I'm really tired of hearing it. Everybody seems to think profiles and LAB mode are nuclear science and I should stay away from it.
Anyway, the test image I'm using is a simple photograph (size A3, 300dpi), so no transparencies at all. I'm placing this image into an equally large ID file and print it from ID, then export it to PDF-X/3 and print it from Acrobat. Hope that helps.

How to get paper color profiles when printing from Acrobat

Hello,
I've been in trouble trying to print with specific paper profiles from Acrobat.
I'm running on mac os 10.8.5, and the latest version of the suite (Acrobat XI).
My printer is an Epson 3880.
I can print ok using my paper profiles when I'm printing from Photoshop; the paper profils show up in the printer box,
and I can choose from my different paper profiles, some of which I've installed recently, non-Epson papers.
But those paper profiles don't show up in the menu when I print from Acrobat…
Any hints why I can't reach those?
Thanks in advance for any help,
Keth.

Are you talking about the color profiles? If so then:
1. Go to File>Print
2. Click the Advanced button
3. Select Color Management from the window pane
4. Select the Color Profile from the Color Profile pop-up menu

Highlighter colors look muddy when printed from Acrobat 8, X, and Reader XI to Xerox WC7775, 7665

Highlighter colors look muddy when printed to Xerox WC7775, 7665(applies to Acrobat 8 Std, Acrobat X Std, Reader XI). I tried the latest PS and PCL6 drivers from xerox.com. How can I troubleshoot / fix this so highlighter colors look bright when printed?
When printing highlighted text from other applications (like Word) from the same computers to the same printers, the highlighter color is bright. Users print PDFs for distribution to clients so they would like the printed documents to look good.
Thanks

I have tried the WCS sRGB, scRGB and ICC U.S. Web Coated (SWOP) v2 color profiles. sRGB and scRGB are very slightly brighter than the default and SWOP but still much more muddy than the bright yellow from a Word document. I just started digging in to this today so any helpful hints would be greatly appreciated.

Terrible red color cast when printing from aperture

I have printed the same image from Iphoto as well as a windows machine and got very nice prints on my Epson R2880. However, every time i print from Aperture it comes out with a terrible red cast. I have tried the system managed colorsync profile as well as the generic one. (FWIW, B&W prints from Aperture on the R2880 come out very nice)
Any other ideas?

You may find it helpful.
Thanks, but if you look in the archives of the Apple ColorSync Users List, you'll find thousands of posts from his Mac dating back to the beginning of the List.
The principle is that you configure your device colour spaces to the largest gamut of which they are capable, calibrate them to a stable condition, characterise that condition in a measured test chart, and build ICC device profiles for those characterisations in your ICC profiling package of choice.
You then capture and correct colour with correct colour previews, resulting in normalised exposures in an ideal CIE colour space. With you normalised exposures, you convert into output condition 1, output condition 2, output condition n which is what repurposing is about.
But you do no apply a gamma change on top of the colour managed rendering. That is incorrect by definition. You apply your gamma change as part of the colour correction in order to get your normalised exposure.
If you imagine this in a prepress process, then you can forget the concept of determinate rendering which is the bedrock of the ICC architecture. If you as photographer do a gamma correction on top of your presentation print or proof print, then you can claim that you have a presentation print, but you cannot contractually claim that you have a proof print as your proof print is a colour correction on top of the colour management system. If Apple Aperture allows the user access to colour correction on top of colour management, then that is a bug in the application. Sorry ...
/hh

Washed out text when printing from Acrobat Help?

When I print PDFs from Adobe Acrobat all the text is washed out. It is supposed to be black but I get gray text.
I have the print settings at rich text black.
The print settings on Acrobat are 600dpi.
It is not a printer issue as I get the same problem with 2 different printer that are different makes and models.
It is a high resolution PDF with no image compression.
The file prints fine from Indesign.
I am running Acrobat Professional 8.2.3
I am running CS 3 master suite
any help is appreciated.
thanks
Trevor

IF, (and that is a big if) the pdf is create some some type of text (word open office, pages, etc) then open PDF in acrobat and click on Touch up text tool
(a Samll button with a capital "T" on it -without quote marks).
Click on select all. then File menu look for Properties. click on properties
when window opens click on appearance tab.
choose color by clicking on colored block. choose black.
IF your document then your out of luck there are no fonts just a drawing of what appears to be fonts. You might use OCR on Document but then not all Characters might ocr so you would only be partially successful.

Exported pdf from indesign drops punctuation when printed from adobe reader

The pdf prints fine when printed from acrobat pro, but depending on the export pdf settings from indesign, it will drop most numbers and punctuation when printed from adobe reader.

Is Adobe Reader installed on the same computer Adobe Acrobat is?

When I load my print projects to Acrobat and print from Acrobat, my blacks turn green. WHY!!??!

Sometimes I have to color match at work, or just adjust images in Photoshop CS4. I save as a Adobe PDF, and load it into Acrobat Pro.
I do not flatten or convert to PDF 1a, just print from Acrobat. When I print, my blacks in the print are green. WHY??

Thanks Sig. The information is here: Anything useful stand out?
Battery Information:
Model Information:
Serial Number:    9G1130CJVD3MA
Manufacturer:    DP
Device Name:    bq20z451
Pack Lot Code:    0000
PCB Lot Code:    0000
Firmware Version:    0201
Hardware Revision:    0002
Cell Revision:    0158
Charge Information:
Charge Remaining (mAh):    5663
Fully Charged:    Yes
Charging:    No
Full Charge Capacity (mAh):    5663
Health Information:
Cycle Count:    59
Condition:    Normal
Battery Installed:    Yes
Amperage (mA):    261
Voltage (mV):    12574
System Power Settings:
AC Power:
System Sleep Timer (Minutes):    10
Disk Sleep Timer (Minutes):    10
Display Sleep Timer (Minutes):    10
Wake on AC Change:    No
Wake on Clamshell Open:    Yes
Wake on LAN:    Yes
Current Power Source:    Yes
Display Sleep Uses Dim:    Yes
Battery Power:
System Sleep Timer (Minutes):    10
Disk Sleep Timer (Minutes):    10
Display Sleep Timer (Minutes):    2
Wake on AC Change:    No
Wake on Clamshell Open:    Yes
Display Sleep Uses Dim:    Yes
Reduce Brightness:    Yes
Hardware Configuration:
UPS Installed:    No
AC Charger Information:
Connected:    Yes
ID:    0x0100
Wattage (W):    60
Revision:    0x0000
Family:    0x00ba
Serial Number:    0x00262704
Charging:    No

Different Colors when printing from Photoshop and InDesign CS3

Different Colors when printing from Photoshop and InDesign CS3
I have the following problem:
When printing from Photoshop or InDesign to a PostScript printer, Adobe recommends to let Photoshop handle the colors (I use the German version, so I don't know the exact term used, it changes slightly in all CS3 apps anyway).
The manufacturer however told me to let the PostScript printer handle the colors.
When I chose this option in Ps's print dialog and then choose ISO Coated as the printer pfofile, the results are fine.
But when I place the exact same image in an InDesign file and print from InDesign or export to PDF and print via Acrobat, again using "Printer handles colors", the results are the exact same as if I had used Ps and chosen to let Ps handle the colors (way too saturated and a bit too red).
·Photoshop CS3
·InDesign CS3
·Test image is a TIFF in CMYK Fogra 27 Coated (which is also the working color space in Ps and ID.
·Printer: Xerox Docucolor 3535
·Printer profile: ISO Coated
How can I make sure the printer handles the colors in other CS3 apps than Ps? I tried it with ID's print dialog (translated from the German version: Color Management > Options > Color Handling: PostScript-printer decides colors).
Thanks a lot!

RE: "You don't indicate what Xerox printers you have"
In my first post I named it, is that the information you need?
Docucolor 3535 using Splash 3535
That's interesting, so I have to find a way to turn off the printer's Color Management function? I mailed them, hope they can tell me how to do it easily. They usually just tell me to not use any profiles and so on, but that's the general rule in this area, I'm really tired of hearing it. Everybody seems to think profiles and LAB mode are nuclear science and I should stay away from it.
Anyway, the test image I'm using is a simple photograph (size A3, 300dpi), so no transparencies at all. I'm placing this image into an equally large ID file and print it from ID, then export it to PDF-X/3 and print it from Acrobat. Hope that helps.

Same as Source Printing from Acrobat 9

Hello Everyone,
I'm in the process of testing CS4 for deployment to a large print production environment and I'm seeing some interesting behavior in so far as it's handling of color management is concerned, specifically with Same as Source printing from Acrobat.
I currently have CS2 deployed, and we're using InDesign for page composition. We primarily accept Adobe RGB (1998) and US Web Coated (SWOP) artwork. PDFs are created from InDesign via File > Export, and we have it configured for "No Color Conversion" and "Include all Profiles." As such, our PDFs contain both RGB and CMYK artwork, all of which is tagged with an ICC profile.
In Acrobat 7, we submit these files "Same as Source" to our RIPs (Fiery and Wasatch) in order to preserve the embedded profiles. All of our color management is handled at the RIP. This works quite nicely. We have tested the submissions and the RGB and CMYK builds (color numbers) come through dead on.
With Acrobat 9 Same as Source submissions, we are seeing that the builds are changing, and that we are getting a conversion to CMYK.
-Original PDF file
Raster RGB - 191,45,47
Here are the numbers that are submitted by Acrobat, captured by our RIP:
-Acrobat 7 Same As Source
Raster RGB - 191,45,47
-Acrobat 7 Printer/Postscript Color Management
Raster CMYK- 0,244,245,0
-Acrobat 9 Same As Source
Raster CMYK - 0,242,251,0
-Acrobat 9 Printer/Postscript Color Management
Raster CMYK - 0,242,251,0
-Acrobat 9 Acrobat Color Management
Raster CMYK - 17,248,245,1
So the question is: What changes have been made in Acrobat 9 to cause for it to handle Same as Source print submissions differently? Why is it that our builds are changing when Same as Source has always been how we get "pass through" color from Acrobat?
Has anyone else run into this? From the perspective of a RIP-driven, color managed workflow, this is a serious issue, no?
(This is also posted to the Color Management forum, as it is both a color management concern generally, and an issue specificly related to Acrobat.)
Matt

We’ve done some further investigations into the differences in Same as Source printing from Acrobat 7 and Acrobat 9. For our tests we created a simple InDesign file with two red vector rectangles, one defined as Adobe RGB (1998) and one as U.S. Web Coated (SWOP). This file was then exported to PDF with “No Color Conversion” and “Include All Profiles.” The resulting PDF contained both rectangles tagged as specified, as verified with PitStop.
We then opened this PDF in both Acrobat 7 and 9 and printed to PS files (at the time, the queue for our HP5500PS was selected). Our cursory findings are:
1. The file sizes differs, which suggests that there is a difference right off the bat.
2. The printed artwork differs visually, which is troublesome.
3. In both instances, when opened in Notepad2, the page objects appear to be tagged properly with Adobe RGB and SWOP specified as the objects color space. This, on the other hand, is good.
a.       Acrobat 7
i.      RGB – Line 3342
ii.      CMYK – Line 3400
b.       Acrobat 9
i.      RGB – Line 8406
ii.      CMYK – Line 8468
4. And here's the biggie: When the PS file created from Acrobat 9 is opened in Illustrator, it says "The document does not have an embedded RGB profile" and it allows for the specification of an RGB profile ONLY. When the PS file created from Acrobat 7 is opened in Illustrator, it says "This document contains objects using both CMYK and RGB color modes. Illustrator allows only one color mode per document. Which color mode would you like to use?" Of course, this PS file SHOULD contain mixed color modes (because it came from a mixed color mode PDF), but only the PS files from Acrobat 7 do. The PS files from Acrobat 9 do NOT. This suggests to us that the PS files (and therefor print data submitted to PS queues as Same As Source) created by Acrobat 9 are not honoring the embedded ICC profiles of tagged artwork.
Does anyone out there have any thoughts or experience? If what we are finding is true, this is a major problem for Adobe's Acrobat 9 print engine.
Matt

Jagged edges on text when printing from InDesign

When I print text from InDesign, it prints with rough edges. This happens with text created in InDesign or imported from Photoshop. I can export the same image to a PDF though and it prints perfectly from Acrobat.

Well, I'd say that you should just do your printing from Acrobat.
ID is not really all that good at printing direct to a printer, and it won't print properly at all to some common ones (mostly HP and Ricoh, but not all of either). Are you printing for proofs or final output? I strongly advise printing proofs from the same PDF files that you will be sending out, anyway, and PDFs tend to process faster in the printer than native InDesing files, so you often can shorten the time it takes to get output by exporting to PDF, even including the time it takes to export (plus, export is a background task so you can continue to work in ID, but printing direct ties up the application).

Banding occurs when printing from Illustratror/InDesign on HP Designjet Z5200 PostScript Printer

Recently we got the below printer for large-format prints such as posters, banners and the like.
http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/18972-18972-3328061-12600-3328080-4122732.ht ml
However so far when printing directly from InDesign and Illustrator there have been problems with "banding" (alternating stripes of darker and brighter colors on the paper when printing).
It seems that this could have something to do with either the type of paper and/or the OS (we use both XP and Win7) on which CS5 runs but I am still unsure if these are the real causes.
After having talked to a certified HP-technician (not only a support employee!) the technician pointed towards the CS5 package as the culprit.
At the very moment we are using a workaround that the before mentioned technician advised us to use which is basically the following.
Illustrator --> Saving the Ilustrator file, then opening it in Photoshop and saving as a tiff raster image in the relevant resolution, then importing the tiff raster image into HP's HP own "Instant Printing Pro" printing application.
InDesign --> Saving the InDesign file as a pdf, then opening the pdf in Photoshop and saving as a tiff raster image in the relevant resolution, then importing the tiff raster image into HP's HP own "Instant Printing Pro" printing application.
These two solutions both work without banding on the final print.
However, sometimes - as mentioned before - it seems that the paper might absorb the ink better if it's of a better/thicker quality when banding doesn't seem to occur (at the moment we mostly use plain paper settings in the local printer settings display when loading a roll of paper which also is a cheaper type of paper) and while banding seems to occur mostly when printing from XP machines it doesn't always seem to occur when doing so from Win7 machines.
What's the score on the above?
Any help and input is welcome and appreciated!

Well, I have no official
connection to Adobe, but any manufacturer who sells a product targeted
at the graphic arts industry, and then says that the reason it doesn't
work is because there's a problem with the software produced by the
graphics industry leader needs a reality check. Printer manuafacturers
have had access to Adobe for years, so there's really no excuse for an
incompatibility problem.
Your company is a vendor? Get
escalated. HP should be all over getting this to work correctly,
including providing a RIP for you if that's what it's going to take to
implement proper printing. How do the expect you to demonstrate or
recommend this printer if it stripes the background?
Peter -->
You are right about basically anything that you said and I agree that this should be HP's headache. But it's not so simple at the moment.
First of all I'd hate to stand back like a dummy if it would turn out to be a minor driver setting issue or another insignificant problem that creates the banding. On the other hand it would of course also be the local HP-support failing since they didn't manage to tell us about it in the first place and that's really their job and responsibility but under any circumstance, I'd like to give the ideas and suggestions from the other participants further up this thread a chance and see if the pdf-printing or other ideas work. In other words..., if I'd complain to HP it had to be bulletproof.
Secondly we are supposed to sell these and similar products to our clients and if I should start a dicussion I'd have to argue not only with HP who would most likely claim that the workaround they told us works (in a way) and that this was a result - at least to them - as well. I might also have to start discussing with the CEO of our company, the purchasing department and the marketing director (the latter actually said some time ago when we had the first problems that if the printer didn't work according to the HP-consultant's promises they could have it back, so there is at least some hope there). At the moment I am too busy at work and too low paid to be getting into this. And I seriously doubt that HP would give us a RIP to be testing this off even though we'd argue that the clients won't be able to work this out if we don't do. They'd probably just say that it's mainly for plotting charts and architects or stuff or find a whole range of other excuses. It's not certain and there could be positive surprises but I'd say that that's not likely.
There is one other thing Peter that I am still wondering about...
If you take a look again at the fourth and last picture-link I posted you can see the exact same print as in link no. 3 but whereas the third link shows banding the last - the fourth image link - shows no banding at all. Now I am not a 100% sure anymore if these were both printed directly from Illustrator but to my best knowledge they were since I printed all of these banners the same day and I don't recall saving to tiff or using other programs. I might be wrong but if that's the case then the thick HP-paper doesn't band whereas the thin does. That's the reason why I stated previously that the banding might occur with thinner paper (or wrong paper load settings) and doesn't occur with thicker paper at all. As mentioned I don't recall this action a 100% but am pretty sure. Also therefore I would like to run another test when I get more time and won't be so busy at work as I am right now.
Do you think there could be a difference there...?
macinbytes wrote:
I'm guessing they have the same crappy Colorburst software that shipped with the HP we got and it's never going to get good with InDesign or Illustrator transparency. We have the thermal printer that is 6x more expensive and the software is still bad. At version 9.3 it still fails on InDesign transparency.
We just make tiffs or normalized PDFs for files containing InDesign transparency. Illustrator transparency generally works better than InDesign, but isn't infallible. Anything that uses the gradient feather tool in InDesign I don't even bother with a test print to see if it gets it because I know it will fail 100% of the time.
If they are a vendor they are in a Catch 22 if they do it right and go for a solution that normalizes the files properly before sending to the garbage software that ships with it. When you are talking about an entry level thermal inkjet the software package isn't going to be robust. Something like a GMG or other solution to handle all the show devices files works, but at best you are disingenuous about how files are being handled with your clients and face pushback when they can't run all the cool tricks to them when they get it out in the field.
Happens with Colorburst, happens with Colorgate, happens to a lesser degree even with the lower end Creo RIP. Fiery seems to get it good somehow, but doesn't power a ton of inkjets.
HP support is phonetag hell anyway for inkjets. They buy out tons of companies that produce anything printing like ColorSpan and provide bare minimum support on the products they slap an HP tag on. They want to sell inks and papers. They don't make the software and license it in bulk like the crap they load on their computers. They also usually ship with old software that needs at least a couple point releases before it is current, but even the current software on their thermal printers sucks at InDesign transparency. HP may need a reality check on their software, but I doubt they get it. They've got a sufficient stranglehold and supporting what is essentially a bottom of the barrel portion of their printing business is in the high maintenance low yield square for them.
macinbytes -->
Wow, now THAT is scary reading...!
If what you wrote is true then things really start looking bleak. But I can recognize some of the problems that you are mentioning although I am not into all of the details that you are writing about in your thread. But it sure looks like they just mass produce and try to keep support to a bare minimum whereas they are scoring big bucks on the media, inks and other accessories and then hope that complaints will die and people will just give up in the end.
It does make sense also seen in light of the fact that our local HP-consultant who "introduced" us to the printer praised it to the sky with a lot of "sales mambo jambo", trying it out in HP's own "E-share & Print" (which I was told by the HP-technician was the wrong HP-print program, instead he made me download and install the "Instant Printing Pro") whereas he NEVER even tried it off in any of the Adobe programs or asked some of our employees to do so.
If you are getting more info in regards to the development in these cases or solutions software-like speaking I'd love to hear from you.
Thanks for your time and for posting.

CUPS Error message when printing from some applications

Hi. I've got an issue when printing from some apps, but not others. Up to a few months ago everything was fine, then it started when Word would not print direct to my printer (Epson Stylus Pro 3880), not a big deal as I don't use it a lot and could print it through Safari if needed. Then more worryingly as a designer I found that PDFs stopped printing direct too, again I can print through Safari and Preview. Last night I installed a firmware update and now InDesign (CS4) is refusing to print!! Not great as printing via Safari/Preview doesn't give me the same level of control over my prints. Just checked both Illustrator and Photoshop and they both print okay. I get the same error code each time "error: /usr/libexec/cups/filter/pstoraster failed" Does anyone know what could be causing this?
Thanks in anticipation. D

cytan,
As Matt pointed, an application printing to CUPS controls only the format of the input. It has no direct control over the chain of filters inside the printing pipeline. Acrobat isn't coded to use pstoraster, it is simpling submitting postscript to the print queue. In an un-molested Apple supplied CUPS setup, that works fine.
What is going on is that the CUPS system configuration got mangled by some third party bits. In the Unix tradition, the configuration is fairly transparent, in the form of plain text files. In particular, in /usr/share/cups/mime you will find out exactly how the filter pipeline is configured via a table of what filter to use to convert data between two mime types. So we can inspect how the filters are setup and how a broken pstoraster is getting into the chain.
I don't have a handy "before mangling" state, but I can clearly see the Apple specified filters to be invoked when the input data is application/postscript (in apple.convs). I can also see a conflicting filter definition referencing the broken pstopdf (in mime.convs) but with a higher precedence, overriding the apple specified filter. This is why, in reference to your points #1 and #2, simply removing pstoraster fails, because the filter configuration is what needs fixing.
On my system, I found the pstoraster filter to be a shell script referencing a MacPorts install of ghostscript. I've since removed MacPorts, but that evidentally left the CUPS configuration in this broken state. Without knowing exactly how the CUPS system was put into the broken state, fixing it can be a bit tricky. Another posting suggested replacing the broken pstoraster with the Apple supplied equivalent of pstocupsraster. That might work, but it would be better to simply remove the conflicting filter specification, which on my system is this bit in /usr/share/cups/mime/mime.convs:
# pstoraster is part of GPL Ghostscript...
application/vnd.cups-postscript application/vnd.cups-raster 100 pstoraster
Removing that will restore the Apple specified filter chain for postscript input. With the filter specification gone, you are free to remove the pstoraster filter itself.
On wating for Adobe to fix this...
Acrobat provides enough things to scream about without pinning non-Acrobat problems on it as well. Not only is this problem not the fault of Acrobat, but suggesting that Acrobat should reach into a CUPS system broken by some unknown third party and fix it is only going to complicate the situation by having two third party products trying to un-do each other's configuration of a system resource. Do you really trust Adobe to fiddle with system components it doesn't own? No, I didn't think so. Adobe installers and updaters have enough trouble with the stuff they do own.
So, why does this problem only seem to affect Acrobat (your point #3)? I suspect it is simply that Acrobat is in the minority of submitting Postscript to the print queue. Any print job produced via CoreGraphics APIs is going to enter the system via a different path (namely, PDF), but the Postscript method is completely legitimate and any application that submits Postscript will be affected in the same way as Acrobat.
I hope this sheds some useful light on what is really going on with this problem.
-john

Can't Print from Acrobat 9 Pro on windows 7 64bit....

I have a windows 7 64-bit computer that can't print to any printer from Acrobat 9 Pro. When you try to print I get the following error:
"print driver host for 32 bit application has stopped working"
Any thoughts, it's driving me crazy....

I'm having the identical problem and the only way I can get it to work is by not trying to change the title suggested by Acrobat for the PDF.
If I try printing from Firefox and pasting in a new PDF title, it crashes Firefox.

When printing from v10.1.3 or v9 from OSX Lion get Adobe Reader quit unexpectedly

When printing from v10.1.3 or v9 from OSX Lion get Adobe Reader quit unexpectedly
Click on the print button
get the Print screen
Click Print then get the error
Am able to print fine from other applications
Have tried uninstalling and restalling Adobe 10.1.3, downgrading to v9. reinstalling the printer driver.
Process:         AdobeReader [2372]
Path:            /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
Identifier:      com.adobe.Reader
Version:         9.4.0 (9.4.0)
Code Type:       X86 (Native)
Parent Process: launchd [220]
Date/Time:       2012-07-22 18:19:40.579 +1000
OS Version:      Mac OS X 10.7.4 (11E53)
Report Version: 9
Interval Since Last Report:          265926 sec
Crashes Since Last Report:           23
Per-App Interval Since Last Report: 30 sec
Per-App Crashes Since Last Report:   2
Anonymous UUID:                      6710821A-4F63-46E6-AD7A-75FB91C7B394
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000014
VM Regions Near 0x14:
--> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
    __TEXT                 0000000000001000-0000000000003000 [    8K] r-x/rwx SM=COW /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
Application Specific Information:
objc[2372]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   AdobeAGM                                0x7e5f1824 PrintInstance::BuildEndPrintEvent() const + 84
1   AdobeAGM                                0x7e5fa503 PrintInstance::NextPrintEvent() + 8157
2   AdobeAGM                                0x7e5291f3 PrintSession::GetNextPrintEvent() + 151
3   AdobeAGM                                0x7e529c60 _AGMPrintSessionGetNextPrintEventProc_GetNextPrintEvent(AGMPrintSession*) + 40
4   com.adobe.Acrobat.framework             0x8077def8 0x7fe0a000 + 9912056
5   com.adobe.Acrobat.framework             0x801d0749 AcroSecurityBailOutImpl + 2003525
6   com.adobe.Acrobat.framework             0x801d08eb AcroSecurityBailOutImpl + 2003943
7   com.adobe.Acrobat.framework             0x8004ffe0 AcroSecurityBailOutImpl + 428764
8   com.adobe.Acrobat.framework             0x800511fd AcroSecurityBailOutImpl + 433401
9   com.adobe.Acrobat.framework             0x7ffbaa3b CopiesPagesPDE_Prologue + 9523
10 com.adobe.Acrobat.framework             0x7ffbadce CopiesPagesPDE_Prologue + 10438
11 com.adobe.Acrobat.framework             0x7ffbb298 CopiesPagesPDE_Prologue + 11664
12 com.adobe.Acrobat.framework             0x7ffcc2ca CopiesPagesPDE_Open + 50672
13 com.adobe.Acrobat.framework             0x7ffcc495 CopiesPagesPDE_Open + 51131
14 com.adobe.Acrobat.framework             0x800066c5 AcroSecurityBailOutImpl + 127425
15 com.adobe.Acrobat.framework             0x80006852 AcroSecurityBailOutImpl + 127822
16 com.adobe.Acrobat.framework             0x80006a9b AcroSecurityBailOutImpl + 128407
17 com.adobe.Acrobat.framework             0x8018fe6e AcroSecurityBailOutImpl + 1739114
18 com.adobe.Acrobat.framework             0x801ffb92 AcroSecurityBailOutImpl + 2197134
19 com.adobe.Acrobat.framework             0x801ff925 AcroSecurityBailOutImpl + 2196513
20 com.adobe.Acrobat.framework             0x802e19ac AcroSecurityBailOutImpl + 3122344
21 com.adobe.Acrobat.framework             0x8001fa66 AcroSecurityBailOutImpl + 230754
22 com.adobe.Acrobat.framework             0x80020e3a AcroSecurityBailOutImpl + 235830
23 com.adobe.Acrobat.framework             0x80165925 AcroSecurityBailOutImpl + 1565729
24 com.adobe.Acrobat.framework             0x8016346a AcroSecurityBailOutImpl + 1556326
25 com.apple.AppKit                        0x93d05fc5 -[NSWindow sendEvent:] + 7533
26 com.apple.AppKit                        0x93c9f163 -[NSApplication sendEvent:] + 4788
27 com.apple.AppKit                        0x93c30d11 -[NSApplication run] + 1007
28 com.adobe.Acrobat.framework             0x7fe0d28d RunAcrobat + 2557
29 com.adobe.Acrobat.framework             0x7fe0c9ce RunAcrobat + 318
30 com.adobe.Reader                        0x00002e8b start + 2371
31 com.adobe.Reader                        0x0000264a start + 258
32 com.adobe.Reader                        0x00002571 start + 41
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib                  0x9b0ac90a kevent + 10
1   libdispatch.dylib                       0x98338e10 _dispatch_mgr_invoke + 969
2   libdispatch.dylib                       0x9833785f _dispatch_mgr_thread + 53
Thread 2:
0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
Thread 3:
0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
Thread 4:
0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
Thread 5:: WebCore: LocalStorage
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.JavaScriptCore                0x9c9a7e81 WTF::ThreadCondition::timedWait(WTF::Mutex&, double) + 81
4   com.apple.WebCore                       0x91b97501 WTF::MessageQueue<WebCore::LocalStorageTask>::waitForMessage() + 135
5   com.apple.WebCore                       0x91b97454 WebCore::LocalStorageThread::threadEntryPoint() + 74
6   com.apple.WebCore                       0x91b973b1 WebCore::LocalStorageThread::threadEntryPointCallback(void*) + 17
7   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
8   libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 6:: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib                  0x9b0a9c22 mach_msg_trap + 10
1   libsystem_kernel.dylib                  0x9b0a91f6 mach_msg + 70
2   com.apple.CoreFoundation                0x95c619da __CFRunLoopServiceMachPort + 170
3   com.apple.CoreFoundation                0x95c6ab04 __CFRunLoopRun + 1428
4   com.apple.CoreFoundation                0x95c6a1dc CFRunLoopRunSpecific + 332
5   com.apple.CoreFoundation                0x95c6a088 CFRunLoopRunInMode + 120
6   com.apple.Foundation                    0x9c5d80c4 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
7   com.apple.Foundation                    0x9c5cbe25 -[NSThread main] + 45
8   com.apple.Foundation                    0x9c5cbdd5 __NSThread__main__ + 1582
9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 7:
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
6   AdobeACE                                0x020310bd 0x2000000 + 200893
7   AdobeACE                                0x02030ab5 0x2000000 + 199349
8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 8:
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
6   AdobeACE                                0x020310bd 0x2000000 + 200893
7   AdobeACE                                0x02030ab5 0x2000000 + 199349
8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 9:
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
6   AdobeACE                                0x020310bd 0x2000000 + 200893
7   AdobeACE                                0x02030ab5 0x2000000 + 199349
8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 10:
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
6   AdobeACE                                0x020310bd 0x2000000 + 200893
7   AdobeACE                                0x02030ab5 0x2000000 + 199349
8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 11:
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
6   AdobeACE                                0x020310bd 0x2000000 + 200893
7   AdobeACE                                0x02030ab5 0x2000000 + 199349
8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 12:
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
6   AdobeACE                                0x020310bd 0x2000000 + 200893
7   AdobeACE                                0x02030ab5 0x2000000 + 199349
8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 13:
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
6   AdobeACE                                0x020310bd 0x2000000 + 200893
7   AdobeACE                                0x02030ab5 0x2000000 + 199349
8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 14:
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be78 _pthread_cond_wait + 914
2   libsystem_c.dylib                       0x97b4382a pthread_cond_wait + 48
3   AdobeAGM                                0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
4   AdobeAGM                                0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
5   AdobeAGM                                0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
6   AdobeAGM                                0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
7   AdobeAGM                                0x7e4b09e1 thread_proxy + 45
8   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
9   libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 15:
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be78 _pthread_cond_wait + 914
2   libsystem_c.dylib                       0x97b4382a pthread_cond_wait + 48
3   AdobeAGM                                0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
4   AdobeAGM                                0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
5   AdobeAGM                                0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
6   AdobeAGM                                0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
7   AdobeAGM                                0x7e4b09e1 thread_proxy + 45
8   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
9   libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 16:
0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x97b9be78 _pthread_cond_wait + 914
2   libsystem_c.dylib                       0x97b4382a pthread_cond_wait + 48
3   AdobeAGM                                0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
4   AdobeAGM                                0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
5   AdobeAGM                                0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
6   AdobeAGM                                0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
7   AdobeAGM                                0x7e4b09e1 thread_proxy + 45
8   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
9   libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 17:
0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
Thread 18:
0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
Thread 19:
0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
Thread 20:
0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
Thread 21:
0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
Thread 22:: com.apple.appkit-heartbeat
0   libsystem_kernel.dylib                  0x9b0abbb2 __semwait_signal + 10
1   libsystem_c.dylib                       0x97b4c7b9 nanosleep$UNIX2003 + 187
2   libsystem_c.dylib                       0x97b4c558 usleep$UNIX2003 + 60
3   com.apple.AppKit                        0x93e79816 -[NSUIHeartBeat _heartBeatThread:] + 2399
4   com.apple.Foundation                    0x9c5cbe25 -[NSThread main] + 45
5   com.apple.Foundation                    0x9c5cbdd5 __NSThread__main__ + 1582
6   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
7   libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 23:
0   libsystem_kernel.dylib                  0x9b0ac90a kevent + 10
1   com.adobe.Acrobat.framework             0x804ff1fe AcroSecurityBailOutImpl + 5340410
2   com.adobe.Acrobat.framework             0x8041adf7 AcroSecurityBailOutImpl + 4405491
3   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
4   libsystem_c.dylib                       0x97b9b6de thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x7e5f17de ecx: 0x7e3f96ac edx: 0x00000001
edi: 0x7eac1420 esi: 0x01ab4228 ebp: 0xbfffdea8 esp: 0xbfffde60
   ss: 0x00000023 efl: 0x00010286 eip: 0x7e5f1824   cs: 0x0000001b
   ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
cr2: 0x00000014
Logical CPU: 0
Binary Images:
    0x1000 -     0x2fff +com.adobe.Reader (9.4.0 - 9.4.0) <8CEEE461-DF9E-46F5-816E-71DE8564A551> /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
   0x60000 -    0x61fff +com.adobe.eulaframework (??? - 1.0) <8AFCE794-4DCF-41B8-9D0F-30311D7BEB92> /Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/EULA.framework/Versions/A/EULA
0x2000000 - 0x210dfe7 +AdobeACE (??? - ???) /Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/AdobeACE.framework/Versions/A/AdobeACE

Right. After almost a day I finally sorted the problem.
Adobe Reader worked under the spare Admin account so I deleted that in case it was confusing the installer. I then rerpaired persmissions. I then re-installed Reader. Same problem "Internal Error"!!
So, I re-created another Admin account and opened Reader. No problem. After clicking accept licence it opened up with a question to make default or not. After this I hunted through every folder and found that Under 'User/Librarary/Application Support/Adobe' there was an Acrobat folder. When I checked the account I normally use there wasn't, and never was?? So I copied pasted a copy of the Acrobat folder into the same location on the non working account and all is fine.
Problem for me is, why did this happen? I wasted almost a day on this. Is it a problem with the installer, the Macbook or Permissions. I checked permissions and they are identical to those on the spare Admin account. So why did the installer not create the Acrobat folder on the main account from where it was installed? Reason it concerns me is with regard to updates. Will they also screw up?
I'll try to explore further as times goes on but for now I have to say I've had enough of Acrobat and Lion for one day. "It just works". Really???

Red Background Squares When printing from Acrobat 8.1.2 (Leopard)

Similar Messages

Maybe you are looking for