Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

LR crashes while trying to select icc profile

Community Beginner ,
Jul 11, 2023 Jul 11, 2023

Hi.

Fresh LR install on a Mac Studio running Ventura 13.4.1

When I open Print Settings in order to select an Hahnemuhle icc paper profile instead of the generic Epson one, LR crashes. 

Clearing the LR preference file didn't help.

Any ideas? Thanks

TOPICS
macOS
355
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Beginner , Jul 12, 2023 Jul 12, 2023

Hello Conrad. 
The problems look similar, though my problem was specifically with the Colorsync tab.
Anyway, I deleted the Epson SC-P800 printer driver, reinstalled it and know everyrthing works again… 

Translate
Community Expert ,
Jul 11, 2023 Jul 11, 2023

Have you checked whether any other ICC profiles cause LrC to crash?

 

Where did you obtain the profile? If Hahnemuhle can you share the profile or link to same in order that we can check whether the profile is corrupt?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 12, 2023 Jul 12, 2023

Hi Ian. 
It happens with all the profiles. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 11, 2023 Jul 11, 2023

What type of Mac is it?

 

Is this happening in the ColorSync part of the Print dialog box, not when selecting the profile in the Print Job panel in Lightroom Classic? If so, then this crash happens in the part of the Print dialog box that (I think) is not directly controlled by Lightroom Classic, but by macOS print code interacting with ColorSync, indicating that the problem is more likely to be in macOS.

 

My old computer is an Intel Mac and it is running macOS 13.4.1. If I do the same steps in Lightroom Classic 12.4 and select a profile I downloaded from Hahnemuhle, it works fine, no crash.

 

But there is another post in this community where a similar crash is reported, so I wonder if there is a specific system configuration where the crash happens, like if it happens only on Apple Silicon Macs. I know I said in that other thread that Apple fixed a print crashing bug in macOS 13.3, but that was related to clicking the Page Setup button, not selecting a profile in the ColorSync section. So if there is a crash related to that second problem, it looks like it would be different than the crash Apple fixed in macOS 13.3.

 

Because this profile action seems to crash on some Macs and not others, even when both Macs are running the same version of macOS and Lightroom Classic, the important thing now is to isolate what specific conditions make the crash happen. That will help Adobe narrow down where the problem is, and it’s why it will be good to know the specific Mac model where you are seeing the crash.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 12, 2023 Jul 12, 2023

Hello Conrad. 
The problems look similar, though my problem was specifically with the Colorsync tab.
Anyway, I deleted the Epson SC-P800 printer driver, reinstalled it and know everyrthing works again… 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 12, 2023 Jul 12, 2023

it and know everyrthing works again… 

 

If above includes the 'Hahnemuhle' ICC profile, then please mark your answer regarding reinstalling the driver as the 'Correct Answer'. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 15, 2023 Jul 15, 2023
LATEST

I've marked this post as correct as you've indicated the issue was resolved by removing, then reinstalling the drivers. 

 

Note that answers marked as 'Correct' help others with similar issues.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines