LR crashes when managing printer with ICC profile

Hi,
I'm printing on an Olympus P-11 thermic printer, using a custom ICC profile (Mac OS X). This works perfectly with all versions of Photoshop, including CS3. LightRoom just crashes when trying to use this profile (or any other profile)...
extract from crashlog :
Version: Adobe Lightroom 1.0 (310575)
PID: 622
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 com.apple.CoreFoundation 0x907d9ab0 CFDictionaryGetValueIfPresent + 60
1 PrintModule 0x16e21bec dyld_stub_regexec + 383882156
I've tried this on two different computers (Apple G4 and G5), one runing an english version of LR, the other running a french localized version. Same result, and Photoshop prints flawlessly on both...
The problem is definitely in LR.

Nicolas,
I have exactly the same problem on a quad G5, Os X 10.4.9. Lr crashes when trying to use an ICC profile to print to a networked HP B9180. Printing using 'Managed by Printer' doesn't cause a crash (but is obviously not a workaround, due to the less favourable colour output). Deleting preferences and re-creating the library doesn't help.
My crash log looks the same as the snippet you posted. I have filed a bug report.
However after I filed the report, I noticed that I also get the following message in the Console which may be of some diagnostic value (is there anyway I can add this info to my original bug report?):
Adobe Lightroom[558] InkChecker could not launch , launch path not accessible
Jupiter crashdump[563]: Adobe Lightroom crashed
Crash logs available for those who want them,
Jason

Similar Messages

Possible solution for problems printing with ICC profiles - esp. R2400

(N.B. This is long because I've decided to go in to details about the background of the problem etc.. Also note that whilst my experience is with the Epson R2400, anyone with problems printing using ICC profiles in Aperture may find this post helpful, as will be explained further down the post.)
Ok, here's the situation. I've been an Aperture user for over a year, and an R2400 owner for half a year. In that time I have done a huge amount of experimenting, but I've never managed to get Aperture to work perfectly with Epson's 'premium' R2400 ICC profiles - the ones you can download from their site which are better than the ones provided 'in the box'. This hasn't been too big a deal because, in fact, the R2400 does a rather good job just set to 'System Managed' in Aperture and 'Epson Vivid' with a gamma of 1.8 in the printer driver. Nevertheless, it really annoyed me that something that should work wasn't, which is why I've spent a lot of time trying to figure out what's going on. Having said that, I have come across a method which will give you pretty good prints out of your Epson R2400 using the premium profiles in Aperture - it's not perfect, but it's the best you're going to get if you want to use those profiles in Aperture. I understand the words 'it's not perfect' aren't what photography experts would probably want to hear, however, I have seen a few anguished posts from R2400 owners in here before, so I think some people may find it useful.
The whole reason why Aperture is hopeless at using the R2400's premium profiles is because - unusually - their default rendering intent is set to 'relative colorimetric' rather than 'perceptual'. You might say 'but that's good - it means you get more accurate colours!', and if you do, you're right... however, there's a snag. To get an image to reproduce well using Epson's premium profiles and relative colorimetric rendering, you really need to use black point compensation. This is where the trouble lies: Aperture's black point compensation is diabolical to the point of being unusable when used with relative colorimetric rendering - I feel I need to be awarded compensation every time I've ever tempted to use the setting. So because BPC in Aperture is unusable, that effectively makes the premium profiles unusable too, because Aperture always uses the default rendering intent specified in the profile.
The solution? Use perceptual rendering instead. Ok, so you can't change the rendering intent in Aperture, which makes that sound a tad difficult. However, as I said in the above paragraph, Aperture always obeys the default rendering intent specified in the profile... so you can see where we're going with this: we need to change the ICC profiles' default rendering intent from 'relative colorimetric' to 'perceptual'. I did some digging around and found one or two expensive pieces of software that could do that... but then I found that, lo and behold, the Mac OS has a command-line utility which can do the job for us, for precisely £0.00. It's called SIPS or 'Scriptable Image Processing System', and you can find out some information about it here: http://developer.apple.com/technotes/tn/tn2035.html#TNTAG58 For those who don't like reading technical jargon however, here's what you need to do to convert a profile's rendering intent. First go to terminal, then type in the following command:
sips -s renderingIntent perceptual
Do not press 'enter' yet. Instead, add a space after 'perceptual', find the ICC profile you want to modify, and click and drag it into the terminal window. You should then find that your command looks something like this:
sips -s renderingIntent perceptual /Users/yourname/folder/RandomProfile.ICC
At which point you can then press 'enter', and the command will execute, giving you an ICC profile which will now make Aperture use perceptual rendering.
There is just one further thing to be aware of after doing this: for some crazy reason, you then need to turn on BPC in Aperture for the prints to come out as good as possible. Black point compensation shouldn't make any difference when using perceptual rendering as the idea of perceptual is that it takes account of things like that anyway, however, in Aperture BPC does make a difference, so remember to turn it on to get a half decent print. In general, I find that prints made using this setup come out pretty well; they almost perfectly match prints made using the profiles with a perceptual intent in Photoshop Elements, except for the fact that Aperture blocks up the shadows a bit more than Photoshop. However, if you can live with that, you might find this is quite a workable solution.
Now, I said near the beginning of this post that all the above can apply to other printers too. Most printer profiles have 'perceptual' set as their default rendering intent, in which case everything I've just said won't be of much help. However, If you are reading this because you're having problems with ICC profiles in Aperture, but you don't use an Epson R2400, find your problematic ICC profile, double-click on it, and take a look at the window that opens: specifically, at the 'Rendering Intent' the window mentions. If it doesn't say 'Perceptual' then it may well be worth trying the steps I've outlined in this post to set it to perceptual, to see if doing so produces an improvement when using the profile in Aperture.
Finally, just one note of caution: if you decide to try out the steps I've detailed above on a paid-for custom-made profile, please back your profile up before messing with it. I haven't experienced any problems when using SIPS to change a profile's rendering intent, but I obviously can't guarantee that it won't do something weird and corrupt your expensive custom-made profile.
If you have any questions, feel free to ask, although (contrary to any impression I may give) I am not a colour-management expert; I'm just someone who doesn't give up when they have a problem that should be solvable.
Thomas
Mac Pro 2.0GHz with 30" ACD; 15" MacBook Pro 2.0GHz Mac OS X (10.4.10)

Thomas
Wow - thanks for such a comprehensive post.
I have Aperture and a 2400 so this information is exceptionally useful to me.
Again - thanks for caring and sharing
Brian

Printing with ICC profiles using CS4

I recently upgraded my MAC Mini to Mavericks. My Photoshop CS4 no longer prints using ICC profiles. It prints using "printer controls' just fine.

Many printer drivers (especially Epson) are having problems with printing on MacOS 10.9. Contact the printer maker to see if they have updated drivers available.

Is printing with ICC profile usable in CS5 and Mac Intel ?

Hi all,
I have an Epson Stylus Color 2100 (2200 in USA) which works perfectly in CS3 with a Power Mac G5. I have an iMac (Mac OS 10.6.4) and can't print with my Epson : everything get out greenish when I try to let Photoshop manage color. If I the printer manage color it's ok but since I work with a ColorMunki.... I would prefer to work with my profiles ! Has anyone any ideas ? Thanks for your help.

Just for your info : there is no solution to my problem (greenish prints) it is a CS5 running SnowLeopard and Epson driver problem.
I have not seen this issue with the new Epson drivers for the 9600, except when I did not completely remove old drivers.
For details (and a workaround -not a solution-) you can see Adobe Tech. Note: No color management option missing when printing in Photoshop CS5 http://kb2.abobe.com/cps/834/cpsid_83497.html and for more details you can read in the Luminous Landscape Forums the topics about that ( http://www.luminous-landscape.com/tutorials/solving.shtml
and http://www.luminous-landscape.com/forum/index.php?topic=43352.0
By far I am not the only one with this problem. I have to wait for the promised Adobe printer Module (which will be available in Adobe Tech Labs someday).
I have tried to install CS3 on SnowLeopard but with no printing difference hence I will have to print with my G5 and CS3....
I found that with SL that it was best to use sRGB as the assigned profile in the workaround, but this did not produce as good a profile as printing a no CM target with InDesign to create the profile.
By far I am not the only one with this problem. I have to wait for the promised Adobe printer Module (which will be available in Adobe Tech Labs someday).
Removing "No Color Management" from CS5 was just a really dumb move by Adobe just because some Epson drivers were not written correctly. O' and by the way Adobe then releases the new version of Elements with "No Color Management" as an option. So is Adobe going to update CS5 and include the "No Color Management" option? Must be some reason after all this time they have not released the much promised application to print unmanaged targets.
I have tried to install CS3 on SnowLeopard but with no printing difference hence I will have to print with my G5 and CS3....
CS3 was one strange beast when it came to printing. Seems it had elements of both Apple printing paths and depending on what OS version you are using you will get different results. I have no trust what so ever printing from CS3. Now CS4 on the other hand prints just fine, and even prints the "No Color Management" option just fine with correct drivers, and that includes the 8.19 driver for the 9600.

Printing with ICC profiles: Aperture/Leopard/Canon 9500

My Canon 9000 prints perfectly with Aperture 1.5 and 2.0 under Tiger.
A friend with a Canon 9500 eports that the cannot turn off color correction in the printer driver under Leopard. It seems that the option is greyed out.
There is a bit of chatter about this in various PS/LR and other forums.
Is anyone printing successfully from AP to a Canon 9500 under Leopard? If so, what driver and settings are you using?
DiploStrat

I just picked up the 9000 today and I had the same problem too. I discovered that the CUPS driver doesn't allow turning off the profile in the driver. I installed the other driver that is available from the Canon website and it does allow it to be set to 'none'. It is the 4.8.5 version. However, the results I am getting do not look as good as it does from iPhoto with the same settings. I am still experimenting with it.

Placing a PDF with ICC profile embedded

If I place a PDF with a ICC profile embedded, InDesign doesn't take in consideration it.
In the case that the Indd colour workspace is different from the ICC embedded in the PDF, when I export to PDF the color conversion is wrong.
For example the PDF embedded ICC profile is US webcoated (Swop), the Indd workspace is Iso Coated L39 v2 and I want export to PDF with conversion to PSO lwc improved,
the conversion that I get is wrong.With an image with the ICC pofile embedded the conversion is ok.
does anyone know how it works?

With regards to placing PDF/X files in either InDesign or Illustrator ...
Neither InDesign nor Illustrator currently do anything whatsoever with the Output Intent ICC profile in a PDF/X file. It is totally ignored. In PDF/X-1a files, there is no other color mangement and as such, all objects are either DeviceCMYK or DeviceGray or spot colors. The objects are imported as CMYK or spot color values assuming the document's default CMYK color space. Thus, if you place a PDF/X-1a file with a profile for Gracol and your InDesign document's default color space is US Web Coated SWOP, those CMYK colors in the PDF/X-1a will be brought in as-is but interpreted as is they were US Web Coated SWOP.
The picture becomes a bit more complex for PDF/X-4. All untagged CMYK objects in a PDF/X-4 file are assumed to have the color space of the embedded Output Intent ICC profile. CMYK content in PDF/X-4 that uses a CMYK color space must be explicitly tagged as such and have an embedded profile for such color spaces. Ironically, all CMYK content that matches the color space of the Output Intent ICC profile must be specified as DeviceCMYK per the PDF/X-4 specification (there is a long story about why that is the case). When PDF/X-4 is placed in InDesign or Illustrator, similar to the case of PDF/X-1a, the Output Intent ICC profile is indeed ignored and DeviceCMYK colors assume the document's default CMYK color space. All explictly tagged with ICC profile CMYK and RGB objects in PDF/X-4 maintain such tagging when placed within an InDesign or Illustrator document and are either preserved on PDF export/save or converted based on the PDF export/save options specified.
Is this a problem? Yes, I believe so. I am in the process of looking at what can be done to improve the PDF/X placement capability in the future so that this problem is ameliorated.
- Dov

Since installing Lion Adobe InDesign CS3 crashes when I print.

I upgraded to Lion yesterday and, now that I am at work, I find that InDesign CS3 (5.0.4) crashes when I print. It doesn't hang...it just pops. My printer drivers (for our Xerox WC7775, with Fiery) no longer work for my other applications (Word, BBEdit). To get CS3 to work I installed Java Runtime through the automatic installer.
Upgrading to CS5.5 is not possible, as our whole office is on CS3.
Is there anything I can do?

Well, I strongly feel it is an Apple issue. Granted I should have done more research before I upgraded, but I (naively) thought that Lionwould be another instance of Apple improving their product, and enhancing its capabilities. In this I was wrong. But then why produce an OS that's incompatible with a large block of your user base?
(1) OS-makers set the rules, and it is incumbent on them tobehave in a gentlewomanly/manly fashion. It seems inconceivable that it's in Apple's best interests to prevent Adobe products from working. Yet that seems to be the case here. It's like Bloom returning home in Joyce's Ulysses: it's dark and all the furniture has been moved.
     And fellow-software makers should help each other out: when there's a flood in anoffice building (as there is here) everyone drops what they're doing to pitchin.
    Maybe this was all a product of a *******-match between Adobe and Apple(recall the PDF support issues on the iPad), but from a users' perspective this is irrelevant. It's the argument that was made in the Financial Times recently about the fall of Netflix: Customers don't give a fig what your internal business priorities are, they want the products that they bought from you to work and be priced well.
(2) The very kludgy work-arounds to this issue, involving deleting or hiding PPDs in the system library (specifically inOS/Library/Printers/PPDs/contents/Resources/), suggest that what is causing the InDesign CS3.x to crash is minor in nature. I.e. a patch could easily bewritten.
(3) Adobe CS3.x applications are the first generation of "Universal" apps. Okay, maybe their implementation was not ideal (as this shows) but they were written to the rules at Apple laid out for them, rules that are still in place now. As with my first point (1) it's unfair to change the rules on Adobe after the fact.
(4) Who could expect that the step from 10.6.x 10.7.1 (the.1 presumably meaning that some initial kinks had been worked out) would be so traumatic? We are not talking here about a step from Classic or PPC. (I remember these, but because they were structural changes everyone, at some level, was prepared for the change.) This is not about getting Rosetta to work on 10.7.
(5) We are not talking about a minor set of applications here either. Considering the long-standing use of Macs by the design community, in print, production, and photo, the support of Adobe apps should have been aconsideration for Apple. But when you look at the list of issues with this upgrade (http://kb2.adobe.com/cps/905/cpsid_90508.html) it's hair-raisingly long. And note these are CS5.5 apps: the very newest software you can get from Adobe. If part of your argument is that it's incumbent on people to keep their software up-to-date, then here's a set of OS issues that are affecting users of software that was released just this spring.
(6) Even if Adobe CS5.5 was fully supported (see (5)), it's unreasonable to expect everyone to upgrade all of their software packages each time the OS is upgraded (as opposed to completely revised: again, as in (4)10.6.x was not Classic). All of my personal software is up-to date, but I cannot say the same of my clients and my employer: they hold to older computers and software packs as long as they can because the software was so expensive.CS5.5 Design Premium is $1900. For any organization this is a big chunk of cash to doll out regularly. My employer is a non-profit: should they replace their software because I have upgraded my laptop? Or should I stop upgrading my software because they can't afford to get CS5.5 (even if it was properly supported)?
      And, what if we buy a new Mac? Presumably this will come with Lion. It's clear with this that this is no longer a $4000 proposition, but a $10,000 proposition, since all the other copies of CS3.x would have to be upgraded.

Adobe Bridge CC crashes when opening file with Photoshop CC or Camera RAW!

Adobe Bridge CC crashes when opening file with Photoshop CC or Camera RAW!
- Tried to Reset the preference with CTRL + Click.
- It's just new clean install didn't do anything with it yet.
- Windows 8.
Any help?

Just that one project, or any project? Can you create new projects?

After upgrading from FM 9 to 11, FM crashes when the Print Book command is used. Suggestions?

After upgrading from FrameMaker 9 to 11, the program crashes when the Print Book command is selected to print files that were converted from FM 9 to FM11. (Resulting .pdf files are problematic, w/ broken links and non-functioning bookmarks.) Has anyone encountered this issue, and can you suggest a workaround? Thank you!

Known bug - already fixed - get the latest FM11 patch

I have a photosmart plus b210 e print and when I print with a black back ground I get lines

I have a photosmart plus b210 e print and when I print with a black back ground I get lines. What can I do to eliminate the
lines in the photo
Thank You

Hey appollus,
Do you get these lines only when printing with ePrint? If not, it sounds like a printhead issue. Here are the steps to fix the issue.
1. Go to the setup menu on the printers front screen.
2. Go to tools.
3. Go to clean printhead
You may need to do this a few times to completely remove the lines in the print.
Although I am an HP employee, I am speaking for myself and not for HP.
If I have resolved your issue, feel free to provide Kudos and make sure you mark this thread as solution provided.

Elements 13 crashes when selecting Print

Elements13 crashes when selecting Print from the File menu.
Rebuilding the Preferences file will bring the Print menus back, but only temporarily.
No error message, Windows advises the program must be shut down.
Win 7, 16GB RAM, Elements 6 on the same computer works fine.

Hi ,
You are going through File menu > Print or File menu > Order Prints .
Meanwhile go to Edit menu > Preferences >> Adobe partner services .
Click "Refresh Button"
Click "Reset Account"
and "Clear On-line Serves data" also.

Acrobat crashes when editing PDF with Pitstop professional

A lot of times our Adobe Acrobat XI crashes when editing PDFs with Pitstop Pro 11.
Mainly when trying to edit/replace fonts.
I also have the crashreport. How can i show this here in the forum?
Am i even in the right place or do i need to contact support for Pitstop Pro?
Thanks,
Robert

Email Enfocus support @ '[email protected]'
they will be happy to help you, if you have any issues please let me know

My java launcher crashes when display SplashScreen with JDK7 on MacOSX

I'm writing a java launcher using JNI on MacOSX, to display a SplashScreen and AWT window. I have almost finished the program, that it runs with JDK6 successfully, but it will crash with JDK7 if SplashScreen shown.
I have posted my code and error message here:
http://stackoverflow.com/questions/21021366/my-java-launcher-crashes-when-display-splashscreen-with-jdk7-on-macosx
Anyone can help me how to show SplashScreen correctly with JDK7 on MacOSX? Anyone can point it out where is wrong in my program?
You can download the program here:
http://www.playcoding.com/sites/playcoding/files/launchers.zip (the launcherV3)
The crash log is here: http://www.playcoding.com/sites/playcoding/files/hs_err_pid241.log

The server JIT compiler is crashing.
This could be an instance of bug 6332641, which will be fixed in 1.5.0_08. It has no known workaround, other than to exclude the method being compiled.
You may want to file a bug.

Photoshop CS5 Print Printing problem: print count and print to ICC profile

Since Adobe still haven't acknowledge the printing issue with CS5, I start this thread to report my own problems.
Problem 1:
print copy count is not working. The first print is always one print regardless how many copies you set in the dialog window. The next print will actually print the copies set in the previous print job.
This is a well documented problem, and until today no fix. I am not too worried about this problem because I can always print one copy each time to get job done, until the day Adobe acknowledge and fix the problem.
Problem 2:
when I let the Photoshop manage color and print to a custome ICC profile (generated by Spyer3Print), Photoshop RANDOMLY decides to print a light colored magenta cast picture. It's like Photoshop has used the wrong ICC. Now every time I print a 13x19, I have to pray. Because this thing is so random, I can't even reproduce the problem consistantly.
here's the information about my system:
Windows 7 Ultimate 64Bit (not a fresh system) with 8GB RAM. Printer drivers installed: Canon Pro9000II, Canon MP600, Epson 1400.
I experience problem 2 after I installed CS5 with Epson 1400 printer, but not too frequent. Later on I installed drivers for Epson R1800, Epson R2400, and I mainly print with R2400. All the printer drivers, software updates are the lastest available.
I was a software developer. I wrote windows application before. I am pretty sure the problem is with CS5 based on my knowledge. If I wrote an Windows application that crashs Windows or another party's appliction, I certainly would not blame Microsoft or another party for not writing a bulletproof system. I would try to find a workaround in my own application. That's just my take. Adobe may have different mind set. They are still pointing finger to MS and Epson.

I don't condone the problems, but a workaround I've recently read about for the copy count problem is to do the following, in order:
1. Set the copy count you want.
2. Click the Print Settings... button to enter the printer driver setup dialog.
3. [OK] out.
4. Print
This is reported to get the proper copy count into the print driver and make it "stick". I just tried it and it seems to work.
Keep in mind you may want to go through this again after printing to get the copy count to default back to 1 for the next print.
-Noel

Color management, printing with InDesign CS3

RGB output devices (this includes essentially all inkjet printers from every manufacturer, when driven by the manufacturer print driver). Inkjet printers driven by a PostScript RIP are considered CMYK output devices, and thus this post does not apply to them.
When printing to RGB output devices from InDesign using the same ICC profiles and settings as in Photoshop, you still get crummy results, in terms of color, that differ from both IDCS2 and other Adobe applications including Photoshop CS3.
InDesign CS2 previously did all rasterizing and color space conversion in InDesign prior to submitting the print job to the OS. In CS3 this was changed to submit PostScript + colorspace information, which is then supposed to be normalized by the OS. Except that it doesn't work. Mac OS X drops the color space information.
The work around is to check "Print as Bitmap" in the advanced section of the IDCS3 print dialog. This causes IDCS3 to do the conversion and generate a bitmap prior to submitting to the OS, rather than depending on the OS to do color conversion or rasterizing, which is the default behavior with IDCS2. Thus you can use the same ICC profiles and print driver settings as with all other Adobe applications, if you choose this option.
Chris Murphy
co-author Real World Color Management 2e

Chris,
First, I am surprised that there has been no response to your post since there were more than a few complaints about the problem in this forum when IDCS3 first came out. So thank you for the solution to this vexing problem.
But I find some of the language in your post a bit problematic:
>InDesign CS2 previously did all rasterizing and color space conversion in InDesign prior to submitting the print job to the OS.
and
>... rather than depending on the OS to do color conversion or rasterizing, which is the default behavior with IDCS2.
The second quote seems incorrect on two counts:
1. It contradicts the first quoted statement.
2. In my mac IDCS2 (version 4.0.5 build 688) in the options area of the color management pane of the print dialog, the only available choice for the Color Handling pop up is "Let InDesign Determine Colors".
So the default behavior with IDCS2 seems to be "Let InDesign Determine Colors".
I am not at all taking issue with the main point of your post, which I welcome wholeheartedly. I just find the second quoted phrase from you post confusing. Can you please clarify.
Returning to your main point, are there any downsides of using the Print as Bitmap method?
Thanks,
Al

LR crashes when managing printer with ICC profile

Similar Messages

Maybe you are looking for