Comments on: The Dreaded Lightroom “Change Modules” Error http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/ Photography in Small Doses Fri, 21 Nov 2008 07:08:33 +0000 http://wordpress.org/?v=2.1 By: charley http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1010 charley Thu, 01 Nov 2007 02:20:00 +0000 http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1010 Hey Aaron - I'm having the same issue in LR ("an error occurred when changing modules"). It appears to have started after I upgraded to OS X 10.5 last weekend. I get the error when I click on the "Print" module in LR. All other modules seem to work okay. I've re-installed the print driver (Pixma Pro 9000)...re-installed LR... tried the rename-the-Lightroom-folder trick you mentioned...STILL no luck! I was hoping you might have some other ideas. Thanks! Charley Hey Aaron –

I’m having the same issue in LR (“an error occurred when changing modules”). It appears to have started after I upgraded to OS X 10.5 last weekend. I get the error when I click on the “Print” module in LR. All other modules seem to work okay.

I’ve re-installed the print driver (Pixma Pro 9000)…re-installed LR… tried the rename-the-Lightroom-folder trick you mentioned…STILL no luck! I was hoping you might have some other ideas.

Thanks!
Charley

]]> By: charley http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1011 charley Thu, 01 Nov 2007 02:28:41 +0000 http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1011 ...update to last post... I revised my search and found this: http://www.lightroomforums.net/showthread.php?t=330 It appears LR 1.2 is not fully compatible with OS X 10.5!!! From the blog: Per Tom's blog, "The current version of Lightroom 1.2 is not fully compatible with Leopard, Mac OS X 10.5. The good news is that we’ll be releasing an update in mid-November that will address key compatibility issues." One of the known issues is that the Print module may not load. For the full blog: http://blogs.adobe.com/lightroomjour...d_leopard.html. In a weird way, I'm relieved by this answer. At least I know to stop chasing the issue. Plus, I can always print from CS3. …update to last post…

I revised my search and found this: http://www.lightroomforums.net/showthread.php?t=330

It appears LR 1.2 is not fully compatible with OS X 10.5!!!

From the blog:
Per Tom’s blog, “The current version of Lightroom 1.2 is not fully compatible with Leopard, Mac OS X 10.5. The good news is that we’ll be releasing an update in mid-November that will address key compatibility issues.” One of the known issues is that the Print module may not load. For the full blog: http://blogs.adobe.com/lightroomjour…d_leopard.html.

In a weird way, I’m relieved by this answer. At least I know to stop chasing the issue. Plus, I can always print from CS3.

]]> By: Administrator http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1017 Administrator Sat, 03 Nov 2007 02:56:39 +0000 http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1017 I'm not very happy with Adobe at the moment, thanks to both this Lightroom 1.2 news from Charley as well as my "poor experience with Photoshop CS3":http://www.singleservingphoto.com/2007/10/17/photoshop-cs3-overrated/. It looks rather certain that I'll stick with Tiger for at least the rest of this month (even though I have a Leopard DVD on its way to me as I write this). C'mon Adobe, get with the program! I’m not very happy with Adobe at the moment, thanks to both this Lightroom 1.2 news from Charley as well as my poor experience with Photoshop CS3. It looks rather certain that I’ll stick with Tiger for at least the rest of this month (even though I have a Leopard DVD on its way to me as I write this).

C’mon Adobe, get with the program!

]]> By: Kev Thomas http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1079 Kev Thomas Mon, 03 Dec 2007 20:56:33 +0000 http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1079 Hate to say it, but I'm running LR 1.3 and on 10.4.11 of OSX. I printed loads of pictures yesterday, but today it's not letting me into the Print module at all. There's plenty of drive space, and nothing...but nothing, has been updated. This is really, really frustrating! Hate to say it, but I’m running LR 1.3 and on 10.4.11 of OSX. I printed loads of pictures yesterday, but today it’s not letting me into the Print module at all. There’s plenty of drive space, and nothing…but nothing, has been updated. This is really, really frustrating!

]]> By: Aaron http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1080 Aaron Mon, 03 Dec 2007 22:03:26 +0000 http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1080 Sorry to hear about your troubles, Kev. I did bite the bullet and upgrade to 10.5 (Leopard, actually 10.5.1) and I'm running Lightroom 1.3 and my "Print" module does seem to be working. I admit, I don't use the print module much, but I tried it once and saw the convenience it brings, especially for contact sheets and such. I'm slightly disappointed at how slowly Adobe seems to react to things like these. I have a much more serious problem with Leopard and Photoshop CS 3, which I also wrote about. That still has not been resolved, so I'm using CS 2 instead. Lightroom is a great product, but so is Aperture. I have a lot of time invested in Lightroom and I would like to keep it, but if push came to shove, I have options. Photoshop is at the place in its lifespan where it has become seriously entrenched and is depended upon by millions. If I couldn't use Photoshop, I'm really not sure where I would turn. I hope that Adobe can get their act together and fix the problems it has in Leopard because hardware and OS development isn't going to stop any time soon! Thanks for sharing your troubles, Kev. If you do get it figured out, please leave another comment so everyone can benefit! Sorry to hear about your troubles, Kev. I did bite the bullet and upgrade to 10.5 (Leopard, actually 10.5.1) and I’m running Lightroom 1.3 and my “Print” module does seem to be working. I admit, I don’t use the print module much, but I tried it once and saw the convenience it brings, especially for contact sheets and such.

I’m slightly disappointed at how slowly Adobe seems to react to things like these. I have a much more serious problem with Leopard and Photoshop CS 3, which I also wrote about. That still has not been resolved, so I’m using CS 2 instead.

Lightroom is a great product, but so is Aperture. I have a lot of time invested in Lightroom and I would like to keep it, but if push came to shove, I have options.

Photoshop is at the place in its lifespan where it has become seriously entrenched and is depended upon by millions. If I couldn’t use Photoshop, I’m really not sure where I would turn. I hope that Adobe can get their act together and fix the problems it has in Leopard because hardware and OS development isn’t going to stop any time soon!

Thanks for sharing your troubles, Kev. If you do get it figured out, please leave another comment so everyone can benefit!

]]> By: monique http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1164 monique Sat, 15 Mar 2008 00:35:04 +0000 http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1164 thanks for sharing. It solved my adobe lightroom problem. :) thanks for sharing.
It solved my adobe lightroom problem. :)

]]> By: Mike http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1190 Mike Mon, 26 May 2008 12:45:41 +0000 http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1190 Well, I thought I'd write in this area since Adobe is so slow and limited in their forum and knowledgebase searches. I trialed their version 1.3 and, to my utter disappointment, still have no export abilities for background music. I assume they are limited by Acrobat's inability to play music. Well, I let the trial lapse and then went back to the folders that it had imported (I was missing images that I knew I should have had). I looked at these particular folders Lightroom had set up and found that the X3F files had 0 kb's! That was 127 images that were not imported. When you are importing 100's and 1,000's of images, you might just not notice that the files have "0" listed in the registered image! Now that the app has lapsed, I can't go in to see if there is, at least, a thumbnail ghost or another place where the file might have been sequestered. This is not as painful as my iPhoto experience of losing thumbnails and thinking I had lost the originals and, in my panic, accidentally deleting an original file of thousands. But, it would have been disconcerting if I had shelled out the $300 and found later that these files had been registered as X3F files with no content! Any suggestions? Like, kiss them off or hasta la toaster, baby!?! Well, I thought I’d write in this area since Adobe is so slow and limited in their forum and knowledgebase searches. I trialed their version 1.3 and, to my utter disappointment, still have no export abilities for background music. I assume they are limited by Acrobat’s inability to play music. Well, I let the trial lapse and then went back to the folders that it had imported (I was missing images that I knew I should have had). I looked at these particular folders Lightroom had set up and found that the X3F files had 0 kb’s! That was 127 images that were not imported. When you are importing 100’s and 1,000’s of images, you might just not notice that the files have “0” listed in the registered image! Now that the app has lapsed, I can’t go in to see if there is, at least, a thumbnail ghost or another place where the file might have been sequestered. This is not as painful as my iPhoto experience of losing thumbnails and thinking I had lost the originals and, in my panic, accidentally deleting an original file of thousands. But, it would have been disconcerting if I had shelled out the $300 and found later that these files had been registered as X3F files with no content! Any suggestions? Like, kiss them off or hasta la toaster, baby

]]>