Color management when printing from Reader 9
When printing from Adobe Reader 9 (Windows XP), the Advanced Print Setup gives the option "let printer determine colors". I presume that if this is selected the colors in the document will be sent unchanged to the printer. So, how does Reader 9 affect the document colors when printing if this option is NOT selected? Also, was this the same in Reader 8?
Thanks
Steve Fowell
It is using sRGB and that is the only color profile available.
In addition, when I try to print 4 slides per page and 1 slide per page, the colors are completely different than when I try to print 2 slides per page.
I have tried changing settings in print options and put them back to default and nothing I do changes the issue. Again, it only occurs when printing from Reader. Everything else prints colors perfectly fine.
Similar Messages
-
Colors not printing correctly - Only When Printing from Reader 9
I have recently been having problems printing color PDF's using Reader 9. Yellows are printing as blue, blues as pink, pink as grey, etc. I have no problems printing any other types of photos, documents, or powerpoint presentations so I am assuming it is some setting in Reader. My printer is an HP Color LaserJet CM1015. Any help diagnosing this problem would be greatly appreciated!
Thanks in advance,
DaveIt is using sRGB and that is the only color profile available.
In addition, when I try to print 4 slides per page and 1 slide per page, the colors are completely different than when I try to print 2 slides per page.
I have tried changing settings in print options and put them back to default and nothing I do changes the issue. Again, it only occurs when printing from Reader. Everything else prints colors perfectly fine. -
[FIX] Darker prints and color shifts when printing from Lightroom 2
Hi,
The problem :
When printing RAW or TIFF files from LR2, you get a printer output that
is much darker than it should be and that presents various color shifts.
I'm using an Epson Stylus Pro 3800 with the latest Windows driver
(6.50 - which is rather old by the way). The workaround described below
works for me under Windows XP SP3. It should also probably work with
other systems/printers/drivers. Use at your own (minor) risk.
The "official" procedure for printing from LR is as follows:
1. Do not let the printer manage colors and select "Other..." from the
profile dropdown list and select the ICC/ICM paper/printer profile that
you want to use.
2. Click on Print... in LR which opens the Print Settings dialog.
3. Select the options you need and the paper you're using.
4. **Disable the color management from the driver's side** (in Epson's
drivers, "Mode | Custom | No Color Adjustments").
5. Print
Unfortunately, **this doesn't work** for many of us and this produces a
print that is dark and has color shifts as mentioned above. Note that
the same image prints correctly from QImage or Photoshop CS3 (that is,
the printer output corresponds to what you see on your calibrated
display).
Apparently, although color management has been (allegedly) disabled in
the driver, there's something wrong between LR and the driver which
makes that *both* LR and the driver are still trying to manage colors.
In other words, the "No Color Adjustements" option of the driver doesn't
seem to work with LR.
The workaround (found after hours of hair pulling and paper and
expensive ink wasting):
In step #4,
1. Instead of selecting "No Color Adjustments", set Mode to "Custom |
ICM
2. Click Advanced...
3. Check "Show all profiles".
4. Select Driver ICM (Advanced)"
5. Set **both** the "Input profile" and the "Printer profile" fields to
the very same profile that you specified in LR.
That is, if you specified Pro38 PGPP (Premium Glossy Photo Paper) in LR,
then also select Pro38 PGPP in both "Input Profile" and "Printer
Profile". This has actually the same effect has disabling color
management in the driver (what "No Color Adjustements" should normally
take care of).
That's it. When printing, you'll get exactly the same color results as
when printing from QImage or Photoshop. No more dark prints. No more
color shifts.
One might think that the bug is in the Epson driver but in that case,
QImage would have the very same problem. So I tend to think that the bug
is on the Lightroom side.
Note: Although Photoshop CS3 produces a correct printer output, it
demonstrates the same problem as LR when using the "Match Print Color"
option for soft proofing. But in that case, only the preview colors are
wrong. The printer output is ok. Which also tends to demonstrate that
Adobe has the problem, not Epson. Or maybe both... :-) .
Don't ask me why some users have the problem and other don't.
Hope this helps.
Patrick Philippot
MainSoft Consulting Services
www.mainsoft.frA sincere thank you for your reply, Michael. Sorry about the "it just doesn't make sense" shortcut. I have been trying to solve this issue since LR 1.1, spending dozens of hours on different trials and digesting everything written on this forum and the B9180 forum about color management and double profiling. My shortcut was a summation of my experience (and my frustration) but doesn't really advance the conversation. Here are some data that should be more useful in diagnosing the problem.
I am running Windows XP SP2. I calibrate my monitor monthly with the Spyder. The reason I suspect this may be an issue of double profiling is because the results (moderately strong magenta overlay plus an increase in contrast) match what more knowledgeable people than I on this forum describe when double profiling occurs. Perhaps I shouldn't presume it is double profiling, and follow Patrick Philippot's lead in naming the problem "color shifts." Patrick does refer in post #2 of this thread, however, to obvious double profiling.
I certainly do have a successful and consistent print method. With PS CS3, and either my Epson 1280 or my HP B9180, the output is almost always dead on. Here is how I do it. In PS from the print dialog box, under color handling I always choose "Photoshop manages colors." Then under printer profile I select the profile designated by the manufacturer for a particular paper/printer combination. Then in the printer driver I disable printer control of color. With the Epson I check the box "Off (No Color Adjustment)." With the B9180 I choose the option "Application Managed Colors." While I sometimes may tweak the final output, these procedures have served me well with PS for several years.
Contrasted with my positive PS experience, my experience with LR printing has been inconsistent. I regret having to be so imprecise but truly sometimes LR produces accurate results that match the calibrated monitor, but most of the time it does not. I use standard procedures with LR that parallel the PS ones described above. In LR's printing panel, under color management, I specify the correct profile, just as I did for PS. Then in the printer driver I use the same procedures I use with PS. Most of the time the prints have the magenta overlay and too much contrast.
BTW, the inconsistent LR printing only takes place with my HP B9180. I have never had any problem with off-color LR prints with my Epson 1280. Again, I emphasize that I have standard procedures that always work with PS (no matter which printer) and LR (but only with the Epson).
Unfortunately the LR printing problems are intermittent. Some of the time (perhaps 20%) LR produces fine prints in the B9180, indistinguishable from PS prints. When LR is printing well, it will continue to print fine until "something happens" and the output shows the color shift. This means I do not get a random sequence of good-bad-good-bad prints, but rather good-good-x factor-bad-bad-bad. Ths problem is that I do not know what this "x factor" is. Once, when LR was giving me accurate output, I simply changed the default printer (Control Panel-Printers and Faxes) from the B9180 to my Samsung 1430 laser; immediately afterwards the LR output colors shifted. Did LR react to this change in default printers? Another time I had good LR printing success with version 1.2 but ran into the problems described above when I upgraded to version 1.3.
Sorry for the long post. I am hoping that someone will see something that I am missing and provide a hint. I think, though, that Patrick is correct when he states, "I tend to think that the problem is with LR. After all, similar issues (obvious double profiling) are observed only in LR but with various printers." -
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 -
Color cast when printing from Lightroom with Epson 3880 printer
Just got an epson 3880 printer. Printing on epson paper is fine. But printing on Ilford or Moab or other papers from lightroom and photoshop have a terrible magenta color cast.
WHen I print the same image from Preview, with the same print driver settings, it looks fine. So somehow the adobe apps (or my settings) are messing up the color sync.
I used to have an espon 2400 which worked just fine.
I have Mac OSX-10.9.1. Monitor is calibrated. (Prints to epson paper with their profiles look great...it's just other profiles that are really bad).
I need help!Are you using moab icc profiles or are you using one of the epson profiles?
I always use the moab profiles which you can download from their Web site. This way you are matching the specific epson printer with the specific moab paper.
At that point you change the printer manages color to Lightroom manages color and select the specific profile. Very easy to do - they even have instructions on the Moab site for installing the profiles if you haven't done that.
Once installed you can also use them through the system print dialogs in PS but it is really much much easier to use in LR - Since coming on board with LR last summer, I have switched to doing ALL printing from LR. Since you mentioned that you are having the same problem with LR and PS, I'm betting you are using epson profiles and this will solve your problem.
Hope so
Tom -
Color off when printing from iPhoto if photo was scanned in.
When I scan a photo to a file or into an application and try to print from iPhoto, the colors are off. Usually darker than they appear in the photo. If I do a direct print from the scanner to the printer the colors look normal (OK). Any idea if there is some type of adjustment for this?
What color profile do the pics have? Is the printer set to the same profile?
Regards
TD -
Color management when printing
I have an IMac OS10.9 and lightroom 5 and a canon printer MG6150. I want the printer to manage color. In Lightroom I comand "printer manages colors" and I am told to make sure this is turned on in the printer How? In The layout shown in lightroom I have two options: "color synk"with different ICC-profile options or "canon colormatching"Which should I use? Is there a comprehensive text on how to manage colors in this situation?
You need to access the printer driver to ascertain that the color management is turned on and the driver interface set to the proper paper type and size. You can do this with the Page Setup button in the bottom left of the Print module. Maybe somebody with knowledge of the printer can give you more detailed instructions.
-
Trun off Color management when printing
I've recently purchased some Fotospeed printing paper and want to get a custom profile for this. The instructions sent to me by the company only covers Elements 1 - 9. These tell me to select Print then, under Color Management set Color Handling to No Color Management. However, this option on longer is available in Elements 11. I've also checked your website for Elements 10 and it would appear that this option was still available in that version. How can I get around this in Elements 11?
Sorry, Barbara.
I could not imagine why one would want to turn off any color management and rely only on a paper profile ?
Here are the instructions to get a custom profile :
http://www.fotospeed.com/pdf/Download/Profiling%20Pack/Epson-CanonandHPElements1-9.pdf
My guess is that if PSE11 is set to 'printer manages color' and you have followed the instructions relative to your specific printer, the result will be equivalent to 'no color management in PSE'.
Really, it's up to Fotospeed to update their custom profiling process instructions. -
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 -
Color cast when printing from Aperture
I'm having troubles with printing since the last upgrade of Aperture.I'm using the Canon ipF5100.
When I print using Aperture the is a nasty greenish color. Now I've to switch to Photoshop CS3 to make a print.
Before the update I could make fine prints.
I have callibrated the screen and the paper I use.
I switch to no correction.
Who can advise me?
Kees BakkerKees,
This sounds like it's the bug with Camera Raw 2.2, rather than Aperture itself. I and many others on this forum had similar issues and reverting to Camera Raw 2.1 fixed things. See this thread and the link to the solution thread:
http://discussions.apple.com/thread.jspa?threadID=1729542&tstart=270
Good Luck!
Regards,
Calx -
Color problems when printing from PDF created in Pages
I have created a newsletter in Pages, and have used the Export > PDF so that the file can be sent to a professional printer. One of the graphics (created by an outside graphic designer and put into my Pages document as a jpg file) prints in all sorts of bizarre colors - nothing like how it displays on the screen. Is there some sort of color formatting that I can do to make it print in the correct color?
The Pages pdf will have many more problems than this case of mismatched color profiles.
Unless you really know what you are doing avoid using Pages for commercial output. For a start all your bitmaps will have been rendered to a too low 72dpi resolution.
Peter -
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.
ThanksRE: "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. -
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. -
All of a sudden when printing from my desktop Mac in IPhoto the printout comes out black. My colors are fine on my HP color laser printer. I have printed many times and now all of a sudden it is not printing. A test copy from my printer comes out fine. I really think for some reason something has changed just in the last few days. Just communication with IPhoto and the computer.
As long as your cartriges are full, put a photo on you desktop, highlight it , click COMMAND P and the print preferences window should drop down, and select your printer and photo paper.
-
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/AdobeACERight. 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???
Maybe you are looking for
-
Can no Longer See Windows Shares
My network has always connected no problem. Suddenly today I can no longer see the computers on my LAN. These are all windows shares. All I see are two alias' Llbrary and Servers. Mail and internet operates normally both by ethernet and wireless. I'v
-
Convert Planned orders in single shot with a Single PR
Hi, Is it possible to convert the multiple planned orders into a single Purchase Requsition with in a single transaction. Existing SAP :- MD 16 >Select Planned Order>Convert to PR of a single Planned Order I am looking for the s
-
Layout - not recognize the element when i call the function write_form
Hi experts, I got a layout(se71) that not recognize the element that i add in the MAIN window when i call the layout from a program. what could it be? i add the element in se71. any help will be appreciated. Michal.
-
Dear sap, cost elements that have been used for postings to our projects but the cost elements are not included in the allocation structures. As a consequense are the settlements ot the projects malfunctioning. Cost element Allocation structure
-
500 Internal Server Error and formsweb.cfg ???
Hi I have the following message when I call my form application : 500 Internal Server Error Erreur de servlet de lapplication Forms. Valeur absente ou non valide pour le paramètre baseHTML. Vérifiez dans la configuration du servlet que cette valeur f