Not sure if this is the correct address to send this to. Not even sure which logs you want so here is a copy of all message from console. All I did was start Lightroom 4, attempted to select book module, got the error "An error occurred when attempting to change modules", then tried to select library and got the same error.
Feel free to coach me on how to extract the most useful logs.
MacBook Pro running 10.7.2
The logging I've been using to confirm cases of the same bug is emitted to the console when running Lightroom from Terminal.app (in /Applications/Utilities) with the -tracebacks option like this:
/Applications/Adobe\ Photoshop\ Lightroom\ 4.app/Contents/MacOS/Adobe\ Photoshop\ Lightroom\ 4 -tracebacks
That said, so far I haven't figured out what causes the errors that are being thrown. There's some detail I haven't figured out that perturbs the module switching sequence and makes it blow up.
I had the same Problem.
In my case I had to repair the permission of the following folder.
/Users/[your name]/Library/Application Support/Adobe/Lightroom
The owner of that folder was incorrect. In my case the owner was a different user, maybee it's a installer Problem.
Hi Dan, Victoria,
I was wondering if I might get a workaround for the same book module problem? I created a new user account and it runs fine in there. I tried copying the Lightroom file over to my main account but still doesn't work and I am not sure how to repair the permission as p.roehl has done.
I would really like to use the book module in my main user account.
Thanks so much,
I am having the same problem. I have tried everything here and everything else I can think of but i a;ways get the same error when I attempt to load the book module.
If I create a clean account it works fine, but attempting to copy the support folder back doesn't work. Changing the permissions doesn't work. I've even deleted the Lightroom folder in the application support folder, re installed the application and it still doesn't work.
I do have the Nik software suite installed, so I'm not sure if that's the issue, but removing the entries from the external editors folder doesn't work either.
Your help would be greatly appreciated as I would really like to try out the book module
I think to copy the folder will not help since the "owner" of the Folder would be incorrect.
What I did is the following, requires a little Unix Shell knowledge...
Started a Terminal Session:
cd Library/Application\ Support/Adobe/
drwxrwxrwx 3 peter 502 102 27 Jan 12:02 Fonts
drwxr-xr-x 33 peter 502 1122 27 Jan 13:08 Lightroom
drwxrwxrwx 4 peter 502 136 15 Feb 2006 Linguistics
drwxrwxrwx 3 peter 502 102 20 Mai 2008 LogTransport
Check for Lightroom.
In my case the Owner (3rd colum) was not me (peter)
To change this type:
sudo chown -R peter:502 Lightroom
Replace peter with the correct user, look at the other Folders.
You will be asked for a password since it requires root privileges and it will change the owner of that folder to yourself and will also work thru sub-folder.
to check type again and look for Lightroom:
Now the owner of Lightroom should be you...
I hope that helps.
All the subfolders in my Lightroom folder inside the Appleication Support folder are owned by me and have read write privelages for everyone. I even tried removing the flder and letting Lightroom create a new one but to no avail. I've tried trashing the preference and I've tried creating a new catalogue. All to no avail. And yet it works in a clean user?
Here's what comes up in the console when you try to change modules:
28/01/2012 21:34:15.150 Adobe Photoshop Lightroom 4: CFURLCreateWithBytes was passed these invalid URLBytes: '/Applications/Adobe Photoshop Lightroom 4.app/Contents/Frameworks' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateFromFileSystemRepresentation should be used instead.
28/01/2012 21:34:15.204 Adobe Photoshop Lightroom 4: CFURLCreateWithBytes was passed these invalid URLBytes: '/Applications/Adobe Photoshop Lightroom 4.app/Contents/Frameworks' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateFromFileSystemRepresentation should be used instead.
28/01/2012 21:34:15.273 Adobe Photoshop Lightroom 4: CFURLCreateWithBytes was passed these invalid URLBytes: '/Applications/Adobe Photoshop Lightroom 4.app/Contents/Frameworks' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateFromFileSystemRepresentation should be used instead.
28/01/2012 21:34:18.946 Adobe Photoshop Lightroom 4: Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: "/Library/ScriptingAdditions/SIMBL.osax"
28/01/2012 21:34:43.622 Adobe Photoshop Lightroom 4: Failed to restore first responder (message was inputContext) NOT KEY
28/01/2012 21:34:45.542 Adobe Photoshop Lightroom 4: Failed to restore first responder (message was inputContext)
28/01/2012 21:34:46.479 Adobe Photoshop Lightroom 4: Failed to restore first responder (message was inputContext)
28/01/2012 21:34:47.520 librariand: client connection is invalid: Connection invalid
Not sure if that hellps in the troubleshooting process but anyway!
Thanks for this...I made an attempt and my name was correct on the lightroom file line...does anything else look odd on this line? Thanks again
drwxr-xr-x 22 kimberly_charles staff 748 Jan 22 14:38 Lightroom
Ok, I figured it out
the problem (for me anyway) was a corrupt font. Or at least a font that Lightroom doesn't like.
If you go to your users library folder and look in the fnts folder. Quit Lightroom and Drag everything out to a temporary folder and try LR4. If that works, then you will have to go through a process of elimination by dragging back a couple of fonts at a time and re-launching lightroom
Hope this helps!
Hi Thomas, I spoke too soon. I tried putting some fonts back into my user font folder and now then the module changing error as soon as I launch Lr rather than only when trying to access the book module. Then I put all the fonts back where they were before and continue to get the error on launch. I don't know where that leaves me but maybe it will help Dan Tull troubleshooting this. I hope.
Wow. That's it! Thank you Thomas!
For purposes of debugging, the font is called aescrawl.ttf. What's interesting is that when you look at the font info, the full font name is Aenigma Scrawl, but in some parts of the font info, its being registered as ∆nigma Scrawl. It generates a name table useability caution when I validate it in fontbook. It's a freeware font, easily downloadable if anyone wants to check out what the specific problem is.
Julie, Did you try taking the fonts all out again?
Thomas...Thanks so much!
That worked for me too. I have a folder right below fonts called fonts disabled and I dragged the whole lot into that. I restarted lightroom and it opened up the book module!
I have so many fonts in there that figuring out the corrupt one will be the next challenge.
I have a lot too. Do it in halves. eg. Take all the fonts from a-L and try them, if they dont work, take them out again and try a-e, etc. It took me about twenty minutes to narrow down a couple hundred to one font.
Thanks! ...It didn't take long to find the font causing my book module problem...cafenorden.ttf
It looks ok but when I click it to see it, the e has turned into a question mark so maybe the odd character too. The font below it, Mom.ttf also has an odd character and although it wasn't crashing the book module, it is not showing up in the lightroom 4 beta font list when I dragged it into the fonts folder.
Maybe a picture is worth a thousand words...here is a screen shot...
...as per Thomas's suggestion I dragged all the fonts from Fonts into Fonts Disabled, then as artemesia suggested, I tried a few at a time to narrow down the bad font. Hope this works for you Julie and anyone else having problems with the Book Module.
I'm glad that you found a solution for your problem.
Any idea why Lightroom 4 would be unhappy with a font that didn't pose any problems for previous versions?
I think that the book module is using a different Font Library.
I'm glad this worked out for everyone! It's great to be finally able to use the book module as it seems to be pretty cool. I figured it had to be something in the user library as it works fine in a new user and yet, in my own user it wasn't working, even with a clean install and a new Lightroom folder in the application support folder. I was going through items in the Library folder when I remember seeing this problem on a friends computer with some other software years ago. Some fonts are missing characters and and I thin that is possibly what's causing it. I'm not sure. I know in my case it was a free font that was the cause of the problem, and it was missing characters. God knows, but hopefully this will help the developers isolate the issue for future versions.
By the way, the book module is awesome. Good work Adobe!!!
Holy cow. I feel so much less bad that I couldn't figure out what was causing this load failure.
As for the inquiry as to why Lightroom 4 is more sensitive to fonts, the Book module uses additional Adobe text components (the same one used in some other products; this is why you have a bunch of typographical control like kerning and leading and such via the text panel in Book) that we haven't used in previous versions. I'm going to ask the devs internally what we might be able to do to bulletproof against dodgy fonts (minimally making the message better and hopefully letting the module load successfully even in the face of whatever error is occurring here). I'll also ask whether I should collect them and file bugs against the component so it will either (a) read them with no problems or (b) ignore them if it can't use them.
Great work getting to the bottom of this one, sorry I couldn't be of more help figuring it out! Hopefully, I can put this revelation to good use and save customers the pain you patient folks went through.
Thanks! -- DT
P.S. If at least one person would send me one of their poison Fonts, I'd be very interested to try to reproduce this condition internally so I can be more sure when evaluating potential fixes.
I've just emailed you my poison font.
Thanks so the additional information on why Lightroom 4 can't play nice with a font that previous versions liked. And thanks very much for all your effort in trying to figure out the cause of this.
This has already been fixed.
I also verified that all the fonts mentioned here* not only don't kill the Book module, but are also usable in it.
*I tested aescrawl.ttf, cafenorden.ttf, and My Mom s Font.ttf - if I missed one (or more), please let me know, and I'll confirm that one for you, too.
I don't understand that message, Max. Are you saying that this module changing error was not reproducible on the developer end with these fonts in the user font library? Or are you saying that the issue has been fixed for the final release so that those fonts will be useable?
The latter. There was a fix for how fonts were processed in the code that was fixed. We just didn't make the connection to realize that was the bug that was biting those on this thread. I'm going to roll back to the beta build and make sure I can repro the bug with the fonts I've been sent.
I'm also going to try to use that repro to see if there's something we should tweak to make failures in that vicinity easier to diagnose.
The final version of Lightroom 4 should be able to use those fonts.
Yep, these fonts definitely make the beta fail to open and the log is conspicuously short on useful diagnostic output but does resemble the logs that various folks sent me, so I think we got our bug and it's dead.
Clearly there are no Free fonts. I have so many so called FREE FONTs it might take some time to figure out what fonts are missing characters . Is there some easy way to figure out what fonts are missing characters ?
What was the problem with aescrawl.ttf and cafenorden.ttf? They don't seem to have anything other than 0-9 and a-z in their names.
I have many fonts that contain dashes and underscores in their names as well as one with an exclamation point and apostrope. None of these seemed to trigger the module changing error.