Skip to main content
shuboxII
Participant
March 12, 2012
Answered

An internal error has occurred: assertion failed!

  • March 12, 2012
  • 3 replies
  • 29040 views

Error occures on file export. I have reinstalled LR4, Repaired disk pernissions, trashed P files, checked ignore ownership on destination volume. Nothing seems to help. Export works fine from LR3.

If anyone has any ideas please share.

System:

Mac OS X 10.7.3

2x2.8  GHz Quad-Core

16GB Ram

LR4

Thanks- Jackie

    This topic has been closed for replies.
    Correct answer eggzentrick

    Thank you for your prompt response Victoria.    That popup was set to "Do Nothing" but I found the problem:

    I kept checking similar questions after I posted and found someone who'd had the same trouble but only on one user account.  This reminded me that Lr had done odd things with permissions on Presets folders in the past which had prevented me from saving new presets.

    The backstory:  When I created the main user account on this machine - by restoring from a TimeMachine backup - it somehow gave me a short name with a space in it.  No idea how, but it hasn't caused me any problems in 4 years - except with Lightroom!  Lr sets the ownership on all its folders to the first word of my short user name, which is not me as far as the system is concerned so I don't get RW access.

    The solution in this case was to make myself the owner of, and give myself RW access to, the folder ~/Library/Application Support/Adobe/Lightroom/ and everything in it.

    I guess Lr does not expect a short name with a space in it, which should be a reasonable assumption given that I don't think you can create them in the OS X gui, and fails to deal with it when it finds one by only parsing the first word.

    3 replies

    July 25, 2012

    I too had this every time I started lightroom:

    "An internal error has occurred: assertion failed!"

    As soon as I diabled the only plugin I had installed, it stopped happening.

    I couldn't  find the folder on my MAC :"~/Library/Application Support/Adobe/Lightroom/ "

    There is no adobe folder? *ugh* I found the Application Support folder......

    Participant
    June 19, 2012

    I've just upgraded from 3.6 straight to 4.1 and I can't export any images at this point - I am getting this error.  Running OS X 10.6.8 on a Mac Pro.

    I have searched here and haven't found anything.  Are there any solutions or workarounds evident?

    Victoria Bampton LR Queen
    Community Expert
    Community Expert
    June 19, 2012

    Double check that the After Export pop-up at the bottom of the dialog isn't blank.

    Victoria - The Lightroom Queen
    eggzentrickCorrect answer
    Participant
    June 19, 2012

    Thank you for your prompt response Victoria.    That popup was set to "Do Nothing" but I found the problem:

    I kept checking similar questions after I posted and found someone who'd had the same trouble but only on one user account.  This reminded me that Lr had done odd things with permissions on Presets folders in the past which had prevented me from saving new presets.

    The backstory:  When I created the main user account on this machine - by restoring from a TimeMachine backup - it somehow gave me a short name with a space in it.  No idea how, but it hasn't caused me any problems in 4 years - except with Lightroom!  Lr sets the ownership on all its folders to the first word of my short user name, which is not me as far as the system is concerned so I don't get RW access.

    The solution in this case was to make myself the owner of, and give myself RW access to, the folder ~/Library/Application Support/Adobe/Lightroom/ and everything in it.

    I guess Lr does not expect a short name with a space in it, which should be a reasonable assumption given that I don't think you can create them in the OS X gui, and fails to deal with it when it finds one by only parsing the first word.

    Participant
    March 19, 2012

    I have the same error not jut the defaullt Adobe exports but all third party software aswell

    Known Participant
    March 29, 2012

    I also get this error when exporting images using LR4  & the 500px plugin.

    Using macbook pro & snow leopard.

    Geoff the kiwi
    Community Expert
    Community Expert
    March 29, 2012

    Try the Lr4.1RC available from Adobe Labs throught the Announcment at the top of the forum.