Skip to main content
Participant
November 7, 2022

P: Print Module, Page Set Up Crashes Lightroom Classic V 12.0.1

  • November 7, 2022
  • 260 replies
  • 20832 views

Good day. I ran across this issue yesterday, 6 Nov, and I'm not sure who (Adobe, Apple, Epson) is responsible for t/s and fix- it is frustrating. Simple to explain - fixing is another issure entirely.

 

I'm using a 16" 2019, Intel MacBook Pro w/32Gb Ram. I upgraded to MacOS Ventura and Lightroom Classic v12.0.1.  Going into Print Module and trying to select Page Set Up crashes Lightroom. I tried restarting the computer, resetting LR Preferences and turning off GPU Acceleration to no avail. 

Do the LR Print Module, Page Set Up and Printer Settings, pull their input from the printer manufacturer drivers? Again, I'm not sure who is responsible or even how to go about troubleshooting/fixing. Any help/advise would be appreciated. Thanks in advance.

I have two projects for customers in work - I should have known better than to upgrade this soon.

 

 

This topic has been closed for replies.

260 replies

TheDigitalDog
Inspiring
January 26, 2023

What I find hard to understand is that they must have received lots of logs of the fault that we have been sending in.  Does that not tell them that we have experiencing these problems since early November and give them something to follow up on?

 

Not necessarily. If there's some conflict with something in the user's system, tracking that down is very difficult. One of the first suggestions for Mac users was to create a new, empty user account and test. Apparently, that didn't work, so the common issue could be something the logs don't report, some 3rd party software, something the OS is using etc. Intermittent bugs or bugs that can't be reproduced internally are the most difficult to find and then fix. Adobe is aware of the issue. No one in pre-prerelease has stumbled on the bug. 

The solution for those with the bug is to wait for an update or roll back to a previous version (test and report).

Ultimately, the fix may be something few wish to attempt: a clean install of the Mac OS, then install Adobe Creative Cloud then Lightroom Classic and test. I'd bet dollars to doughnuts the bug is gone. But that's a lot of work few wish to attempt (but it would be a good test!). 

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
Inspiring
January 26, 2023

What I find hard to understand is that they must have received lots of logs of the fault that we have been sending in.  Does that not tell them that we have experiencing these problems since early November and give them something to follow up on?

TheDigitalDog
Inspiring
January 26, 2023

I DID finally hear from Adobe (thank you!), and the frustrating and very puzzling thing is that the person said he can't reproduce the issue at his end

 

That's part of the problem; many of us on the same OS etc, cannot reproduce this bug. Those are the most difficult to find and fix. 

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
Pattyoboe
Known Participant
January 26, 2023

Couple of things, since one of you wrote with suggestions AND Adobe (!) emailed:

It was suggested I move to an older version of LR. Did that to no avail. I also went to a slightly older backup, knowing I'd printed when using that (thankfully losing only a few photos), and that, too didn't work. I have NOT moved backwards with the Apple OS so I suppose I should learn how to do that. 

I DID finally hear from Adobe (thank you!), and the frustrating and very puzzling thing is that the person said he can't reproduce the issue at his end. But I'm glad he wrote, and it does sound like they are trying to fix things, but if they can't reproduce the problem I'm not sure how they can. (Maybe I should drive over with my printer and computer. Okay, joking, but honestly, I wish they could see what happens live and in person.) He did give me a few tasks to try, so perhaps I will find the time to do that today.

Taiyosan
Participating Frequently
January 25, 2023

YAAA! Adobe has reached out ... i received an email with apologies and asking questions - i hope you have received such an email and please follow thru on his questions.

TheDigitalDog
Inspiring
January 25, 2023

You could try reverting to an older build of LR or maybe boot of the last major Mac OS (Mojave).

 If you wish to roll back to an older version, use the Creative Cloud application, click on the three dots (...) and select “Other Versions”.

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
Known Participant
January 25, 2023
I too find it totally frustrating that it has taken this long without a fix in sight.  Fortunately for me I don't use custom templates, I just print out my photographs on a single sheet of paper so when I switched to an old catalog I was able to proceed as usual but I did lose the develop data on some images.
Pattyoboe
Known Participant
January 25, 2023

Yes, thedigitaldog, I send a video as well as images of the off-centered cards. I've written about this issue, and read about the issue not only here but on other sites as well. Many of us are frustrated, and while I have tried suggestions from some of you who have had solutions nothing has worked. I'm certain the issue is something to do with Apple and Adobe, but surely the two can figure this darn thing out and fix it. Grumble, grumble.

TheDigitalDog
Inspiring
January 25, 2023

Did you send engineering a video leading up to the crash?

No crash on this end, running Ventura so this isn't affecting everyone. 

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
Pattyoboe
Known Participant
January 25, 2023

I must admit this has become so outrageous I'm seething. I, and everyone else, I assume, pay a monthly fee and yet I can't print?! I had to use all older work for a current show. I can't print my new cards using my templates that have been using for years. Is this acceptable for a company that takes monthly payments from us? Is it time to move on to something more trustworthy? I keep hoping that someone from Adobe will at least say "Yes, we know this is frustrating and we promise we are working on it," but so far they haven't done that. Admitting a problem is a sign of concern, and perhaps even respect, to those of us who are waiting waiting waiting. 

Sorry for the rant. But I'm furious.